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.

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.

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?

None. There is no model that can output anything even remotely usable on that tiny amount of RAM and certainly not using the few CPU cycles your vps has to offer.

The US default, that I never left Europe. What an achievement for the USA!

Oh come on, are you really that boneheaded not to understand that you’re not the norm?

I literally had not a single power surge in my entire life. The only power outages I had were for a few minutes maybe three times in the last 15 years.

The larping refers to you. Either you are truly an outlier who actually runs a small DC, or you just like the feeling you can get pretending to do so.

Your attitude is roughly the “only gold plated cables made from solid silver” equivalent in audiophiles. Technically maybe correct, practically a self-important waste of money.

But not for us.

That’s what I meant by larping. The vast vast majority of us here would probably not even notice if their systems went down for an hour. Yes, battery backup has its purpose. In a datacenter.

I mean, what’s on the line here in the worst case? 15min without jellyfin and home assistant? Does that warrant taking risks with old batteries or investing in new ones?

That equation might change if you’re in a place with truly unreliable electricity, but I guess those places have solutions in place already.

That’s typically a feature for servers or business desktops. Maybe your laptop has it, just look into the BIOS.

As I wrote in my other comment: try to be realistic about your needs. Chances are, pressing the power button every few months (if at all) is perfectly fine for your use case (and most others here).

And how much need is there for a UPS in this scenario - realistically.

Some of the people here take their admin-LARPing a tad too seriously. Most households have reliable enough electricity, and even if there’s an outage once every quarter, would a dead battery even help?

I advocate for being realistic with one’s own needs. Don’t build a five-nines datacenter for a glorified weather station or VCR.

In case you didn’t already do that: remove the battery. It’s probably dead anyway, you don’t need it and it poses a potential (albeit low) risk.

But they made half a million.

And there are literally hundreds of similar companies raking in billions in investments that magically vanish while the founders live a luxury live and move on.

The real question is: why do VCs shit so much money into obvious frauds? Are they this stupid or do they just hope to pass it on to the greater fool?

Had to work with a fixed string format years ago. Absolute hell.

Something like 200 variables, all encoded in fixed length strings concatenated together. The output was the same.

…and some genius before me used + instead of stringbuilders or anything dignified, so it ran about as good as lt. Dan.

And there are some truly magic tools.

XSDs are far from perfect, but waaay more powerful than json schema.

XSLT has its problems, but completely transforming a document to a completely different structure with just a bit of text is awesome. I had to rewrite a relatively simple XSLT in Java and it was something like 10 times more lines.

And DBAs. I’m currently working on a project where I said from the very start, I can set up this DB in k8s and I can get it to work decently, but I have neither the knowledge nor the time to get it right. Please give me someone who knows how this works.

No, don’t worry, it’ll be fine, we don’t need that, this kuverneles thing I keep hearing about handles that!!!

Six months of hard contact with the enemy on production later:

Well, we’re currently looking for someone who actually knows how DBs work, because we have one of those issues that would cost a proper DBA 5min and me 5 months.