100% that.

Especially that working software over comprehensive documentation part, which can be automated so easily if done right.

There’s so much value in TDD and providing a way to do integration and automated UI tests early on in a project, yet none of the companies I’ve worked at made use of it.

Also automated documentation tools like Swagger are almost criminally underutilised.

Unfortunately I can’t help you with Nobara, but I’m surprised you’re having troubles with EndeavourOS.

EOS has been working out of the box for me for almost everything.

Not really. Exceptions are a controlled way of indicating something went wrong in an application.

The only point where you wouldn’t know about the possibility of one is when you don’t know enough about the language features you’re using or when you use a badly documented library or framework.

Yeah, I had a similar case with some authentication middleware I used that was part of a library.

It would always throw an exception when a user wasn’t authenticated instead of just giving me some flag I could check.

Wouldn’t have done it that way, but it was okay for an API controller.

Another upside of Jetbrains over Adobe is that you can get edu-licenses that allow you to use every software of theirs.

The best deal our university could get from Adobe was 25% off on Photoshop if at least 200 students bought it.

Depends on who you think the people are.

CTOs, technical team leads and such can make those decisions. And devs can also suggest migrating to simpler solutions.

If a tech giant like Amazon can do it like they did with Prime Video, I don’t think it’s impossible other companies can do so too.

I’d have recommended it as well.

Popular stuff is usually available in most languages.

You can have the best tool in the world and still find people just hitting their own face with it.

Meme is funny, but that exception used as flow control hurts.

Thanks for the response. Seems like I can’t assume other CS degrees are comparable.

We definitely have a strong focus on security in my degree, but I still believe that awareness of what you’re running on your machine and potential dangers of those programs fall into the category of common sense. Mishandling secrets, having bad authentication or not knowing how to setup SSL is definitely experience stuff though.

Neither young or naive. Just assuming others share my experience.

Makes sense, I feel bad for the guys that were happy for a chance and got screwed over. (By the hackers, not you, haha)

That’s a bad take. Unless you get your knowledge purely from shady tutorials or have a fast track bootcamp education, it’s unlikely you never touch on security basics.

I’m a software design undergrad and had to take IT Sec classes. Other profs also touched on how to safely handle dependencies and such.

While IT Security is its own specialisation, blindly trusting source code others provide you with is something a good programmer shouldn’t do.

If you need a metaphor: Just because a woodworker specialises in tables, doesn’t mean they can’t build a chair.

Edit: Seems like my take is the bad one 😂

It’s sad that this works. You’d think especially software professionals would be the most vigilant about running unknown code.

While I certainly agree with you that discrimination based on sex is unacceptable im most contexts, I believe that gender exclusive spaces, unless they hinder people directly, sometimes are a good thing.

My dad is a mental health professional and founded a weekly ‘only-men’ self help group. He found that some things they talked about there wouldn’t have worked with women involved. That group existed for about 5 years or so and helped quite a few struggling men.

So yeah, unless there’s any maliciousness involved, I’d argue that gender exclusiity is not bad in every context.

I did check the bios settings but couldn’t really find anything that would directly affect a pcie card.

Most power management stuff that could cause issues is turned off. Fast boot itself was also off.

Classic!

Thanks! It’s really funny. Especially since KDE updated to version 6 and caused a lot of issues for other users - so it had to be the a software issue of course!

I’m still not entirely convinced, that it wasn’t a software issue that caused the device to misbehave.

It’s my cat, I am the user 😄