Ved mit gamle arbejde indenfor energihandel synes jeg ellers de kronisk fyrede udviklere. Det var også noget af det der fik mig til at sige op: Mere arbejde til færre folk. Men det er nok ikke billedet i hele sektoren.

I'll try that next time it dies, see if it helps

The server currently runs on 32gig but I was planning on upgrading to 64 or 128gig DDR5. Could go as low as 16 if need be, but the the price is still hurting more than having to reboot 2-4 times a month.

Difference is that vibe coding doesn't create 20% more CPU usage or 30% more RAM usage because it doesn't understand the underlying mechanics (or, it could but that is not the important part). LLMs will happily provide you with solutions that consists of plain text password storage, leaking personal information through open APIs, and business crushing vulnerabilities. A sharp developer should be able to catch that, but if you're reviewing 5000+ line PRs daily that's been spat out by LLMs it'll be impossible to catch all failures. And for someone who doesn't know all those nonfunctional requirements that a business absolutely must have it'll become a nightmare for the receiver of the code.

So to be clear: For functional requirements LLMs are a bit better but still needs hand holding. For nonfunctional requirements they're dog shit as that's the part that more often than not has to explicitly be mentioned. And being able to identify nonfunctional requirements and when they're not met is the difference between a junior dev and a 10+ year lead.

Slow app? Just add resources. Vulnerable app? Actual compliance and business risk.

And I've given up on Facebook ages ago. You should too.

Only thing I wish for Christmas is to be able to replace the RAM and mobo in one of my servers. It is failing with a kernel panic about once a week and it is an old DDR3 platform I planned to upgrade back in January. I have isolated the issue to a hardware fault but left without a solution...

Velkommen til @VisualizationExpo@feddit.dk

Hvordan fandt du frem til Feddit.dk?

Der har vi vist også fået en del igennem, jeg håber du kommer godt til rette blandt os andre expats fra Reddit! Hvis du har nogle spørgsmål så er du mere end velkommen til at række ud.

Velkommen til @MindMovie@feddit.dk

Hvordan fandt du frem til Feddit.dk?

Hvorfor fanden skal vi have en statue af Putin stående?

What OOP refers to is not "writing code" but "designing the code." Everyone can write a book. Even I can. It will be a fucking shitty book, because I don't know how to create suspense, give depth to characters, or any of that stuff. But it's still a book. Writing code is easy. Writing good code is hard. If you want a program to fetch the current outside temp from an API you could throw together random lines of code that vaguely does what you want that you found on stackoverflow and iterate until it works. Will it catch edge cases? No. Will it output in a pretty format? No. Will it be maintainable? No. Will it be the next Facebook? Hard no. But you did write code.

Writing code is easy. Writing good code is hard. And that is why we have door stoppers called "Clean Code" to help us on our way. You might notice that the "how to code" books aren't much thicker than a a pamphlet. But if it ever as much as touches on the topic of good code it will make for a door stopper worthy of a nuclear bunker's entrance.

And the realist in me says that no one outside Britain knows what Elizabeth Tower is. And probably half of Britain.