Because you don’t know what you’ll need that wrapper beforehand, that’s my entire point.

Unless you’re only doing trivial changes, the chances are very high that you won’t be able to design the class structure. Or, you end up essentially writing the code to be able to write the tests, which kind of defeats the purpose.

If you have to ask “can’t you just” the answer is almost always no.

And who actually writes tests like that?

I mean, do you think tests do the calculations again? You simply have well defined input and known, static output. That’s it.

Tests first is only good in theory.

Unit tests typically test rather fine grained, but coming up with the structure of the grain is 80% of the work. Often enough you end up with code that’s structured differently than initially thought, because it turns out that this one class needs to be wrapped, and this annotation doesn’t play nice with the other one when used on the same class, etc etc.

Especially then I’d test the shit out of everything? I’m getting paid for writing correct software.

For local development, it should be super quick. However, I’m currently building a small project where a device (or rather the library using it) can’t really be used with a debugger. So 500 print()s it is.

Yes, but it’s not Unix. That’s literally part of GNU/Linux’ name.

Mac OS is more Unix than Linux.

And a lot of people would call that incapable.

This is a form of learned, or rather forced to internalize, helplessness. People don’t even want to understand things, even though they absolutely could and ought.

I think you don’t distinguish enough between professionals and capables.

All your points are either “sysadmin” or “complete buffoon” and nothing in between. That’s not how reality works.

You absolutely are expected to be able to check your oil and just a few years ago, you were expected to be able to change your tires. That doesn’t make you a car mechanic, but a capable user.

I’m absolutely not a car guy, but I know how to change a tire. Why? Because it’s necessary knowledge. I also know how to file my taxes, even though I’m not an accountant or tax consultant. Again, because it’s necessary.

The sentiment should rather be, that the system maintains itself. And that’s actually something I would get behind.

Tinkering around is cool, but I’m in my 30s and when my girlfriend’s build pipeline finishes, I’ll be a father, I can’t spend 4h every week fixing stuff, I need a reliable platform to work on. Currently that is indeed a mix of Debian and Nix for me.

At least the normal update process should work completely transparently for the user.

Not a sysadmin, but a capable user.

People shouldn’t just accept technology as magic. They should understand at least the basic principles of the technology around them. Corporations want us to be dumb and incapable. Look at cars, you seriously can’t expect a normal person to fix anything on them. But that’s not because of inherent complexity, but because corporations want us to just buy new parts when they think it’s time.

Sapere aude was true in the 19th century and it’s true today as well.

I find it extremely frustrating how weirdly wrong-density much documentation is. It’s extremely detailed in all the wrong places and often lacks examples for common use cases.

I learned a while ago that news articles are supposed to have increasing levels of detail from top to bottom. Each paragraph adds a bit more context, but the general picture should be contained in the first one. Hardly any documentation follows that pattern.

I use Karch, btw.

Usually ~/devel/

On my work laptop I have separate subdirs for each project and basically try to mirror the Gitlab group/project structure because some fucktards like to split every project into 20 repos.

Ansible is actually pretty nice, if you get the hang of it. Not perfect, but better than triple tunnel ssh.

You could simply automate step by step, each time you change something, you add that to the playbook and over time you should end up with a good setup.

Flakey dev setups are productivity killers.

The real question is why you’re torturing yourself by manually fixing that stuff? Don’t you terraform your Ansibles?

Exactly. But mods here are too butthurt to accept that and rather delete my comments, so they can live in their delusions - which was my point

As I wrote: sanctions. That’s what compliance means.

Removed by mod

Removed by mod