• 0 Posts
  • 263 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • For a project I liked I saw that the translation of the UI was only about 1% complete for my native language. I decided to dedicate the weekend to get it above 95%. This was apparently the part that seemed too hard for most to make a dent in, but across several new versions my language is still 100%. I think my groundwork made it easier for some sporadic contributors to get a small bit of dopamine when updating the few new strings in a release to see it hit 100% again.




  • 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.



  • 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.