I once worked on a project where the main function would run the entire code in a try-catch block. The catch block did nothing. Just returned 200 OK. Didn’t even log the error anywhere. Never seen anything so incredibly frustrating to work on.

Mostly the latter. We don’t do any optimizations on our product whatsoever. Most important thing is to say yes to all the customers and add every single feature they want. Every sprint is spent adding and adding and adding to the code as much as we can and as quickly as we can. Not a single second is allotted to any discussion about performance or efficiency. Maybe when something breaks, but otherwise we keep piling on more crap at full speed non-stop. I have repeatedly been told “the fast way is the right way” followed by laughter. I was told to “merge this now” on multiple occasions even when I knew that the code was shit, and told the team as much. I am expected to write code now and think about it later.

As you can expect, the codebase is a bloated nightmare. Slow as shit, bugs galore, ugly inconsistent UI, ENORMOUS memory use, waaaaaay too frequent DB access with a shit ton of duplicate requests that are each rather inefficient themselves. It is a rather complex piece of lab management software, but not so complex that it should be struggling to run on dedicated servers with 8 gigs of RAM. Yet it does.

I have node named pve too. Small world.

Twice, because usually it’s two sticks.

In any case, RAM failure is rare enough that quadrupling its chances is not gonna make any meaningful difference. Even if it does, RAM is the easiest thing to replace in a PC. Don’t even need to go offline while waiting for a new stick. Someone who’s got the cash to build that thing in the first place won’t be too upset by the cost of another 32gb stick either, I don’t think.

Well you see one client demanded some absolutely stupid very obscure feature that was so absolutely stupid that it could only reasonably be achieved by hacking some bullshit together on their on-premise bare-metal installation that they insisted on not giving you proper access that you needed. Then something went wrong with that hacked-together one-off bullshit, and the digital equivalent of this was the only way to figure out what the hell was happening.

Podman has a built-in automatic update feature that monitors the source repo. Could be useful for you.

Ah, if I understand this explanation right, the blob’s purpose is to do things and stuff. Is that correct?

How is that? Does risc-v have magical properties that make its designers infallible, or somehow make it possible to fix flaws in the physical design after the CPU has already been fabbed and sold?

What skill? This is not a fucking game lmao. I don’t use an immutable distro because I have better things to do with my time than to try and climb a steep learning curve using some very questionable documentation. I can acknowledge the benefits, but I also acknowledge it’s gonna take me time to get there. And I judge that the time investment is not worth it.

It doesn’t have discussions, it doesn’t offer pull request management with commented/annotated code reviews, it doesn’t have built-in ssh and key management features, no workflows, no authorization tools of any kind…

In short I find the “just use git itself lmao” to be an exceedingly weird thing to say and I find it even weirder that it gets said as often as it does and it gets upvoted so much. Git by itself is not very useful at all if there are more than one a half people working on the same code.

Excuse me if I don’t appreciate when the compiler adamantly refuses to do its job when there’s one single unused variable in the code, when it could simply ignore that variable and warn me instead.

I also don’t enjoy having to format datetime using what’s probably the most reinventing-the-wheel-y and most weirdly US-centric formatting schemes I have ever seen any programming language build into itself.

Pretending that the distro package manager is a suitable tool is not enough? Kids these days smh

C dependency management is the worst. I thoroughly dislike how it works over there.

It’s an error message matrix (the messaging application) throws when something goes wrong that makes it unable to decrypt messages.

Floating point errors are a product of how floating points work as a mathematical concept. So they’re independent of the programming language and can happen everywhere.

In this case though, I doubt it’s a critical issue. So the player “died” when they actually had 0.000000000027 hp left or whatever. Who cares? Do you need to be that precise?

Excuse my ignorance but how is this a violation?

Have they given an explanation as to why that is? I mean why make it a fatal error that prevents compilation, when you could make it a warning and have the compiler simply skip it?

To you, maybe.

That’s… a rather huge drawback. Why even pay for a shield at that point?

Manually optimizing the code I wrote in C, so that it runs noticeably slower and has all sorts of stupid bugs that weren’t there before. All in a good night’s work.