For those missing context, Rossman uses a software that helps view the layout of Mac hardware… and it breaks literally constantly.

I think he’s just saying that working in a shit environment is sometimes more harmful than underpaying them. Pay is important but it won’t always keep someone if the job is awful.

deleted by creator

I started using EndeavourOS which is pretty close to Arch with a better installer. Uses their repos unlike Manjaro.

https://github.com/just-containers/s6-overlay#the-docker-way

I’d argue systemd has bad, borderline incorrect design. I didn’t like SysV because it caused inconsistencies and hard to understand processes. systemd fixed the inconsistencies but the rest is sort of hacked together bullshit that developers play wackamole with. That hackery is the reason it can’t be used in Docker for example. It has a complicated parser for a language that’s basically a DSL that doesn’t really solve the problem of complexity for the user. It requires a whole slew of random non-sense to work and it feels like stars have to align perfectly for things to function. It encourages bad behavior like making everything socket activated for literally no reason.

Compared to SysV, I’ll take systemd. I don’t find it ideal at all though. It’s serviceable… much like how Windows services are serviceable. S6 is I think what the ideal init would look like. I’m more impressed with it’s execline and utilities suite but that’s another story.

The only thing I think systemd did right is handling cgroups.

I did exactly this. Lost a lot of money with no immediate income but it was so worth it.

They’ve been pulling leetcode questions designed to take a lot of thought and effort. They then expect people to get them in 10 minutes.

Unfortunately, I never got a degree so even when I can ace those questions, I’m really just there to fill their interview quota for the most part.

I’ve seen it get a lot of hate revently. In my experience, it’s mostly been from people upset they had to refactor their 400 line function or write unit tests.

Been with a lot of codebases that had no unit tests at all and everyone was afraid to change anything because the QA process could take weeks to months.

The result is you have a codebase that ages like milk.