Discussion
RE: https://social.treehouse.systems/@ariadne/117267343778956550
I've said it before. Vibe/AI coding is a symptom of the software industry's problem with tech debt, bloat, over-complexity, and feature creep.
If you are using AI to write "boilerplate"... why are you writing boilerplate? Good tooling doesn't need boilerplate.
@lina They treat the LLM like every intern's most toxic boss demanding boilerplate.
We steal someone else's boilerplate and make tweaks to match our needs better.
We are not the same.
@lina you had me in the first half. Lol what the heck do you mean "good tooling doesn't need boilerplate?" If setters and getters are boiler plate, what is the argument that those aren't needed? (Please do not say make everything public...)
@smolbrain setters and getters can be very easily generated without LLM. Codegen and syntax sugar exist 
...and if your tooling has no option to do that, and requires manual definitions, such tooling has a really huge room for improvement
@mo
Again. im not taking on the AI point here.
But saying every language *must* have this auto generated code feature is amusing to me. And taking such a hard line position... Well I have seen how well it goes personally many many times. And for your own work that's totally fine and whatever. But if you ever have to do code for a company you often don't get that level of say and taking that kind of hard line position makes you a difficult person to work with. Which was why I wished them sincere luck.
@lina
@smolbrain @mo I never said it's your responsibility to fix management's bad choices, or that you should refuse to work on any codebase that is not perfect or has tech debt.
They're still bad choices though, and it's still a codebase with tech debt, and if you ever *do* find yourself in a position to make better choices, you should.
@smolbrain If your setter and getter are doing nothing useful then yes the field should just be public.
If you are doing it for future-proofing, then your language should offer a way of marking up the field to auto-generate a default getter and setter for you.
If your language can't do that, that's the problem right there.
@lina I'm not even saying this "in defense of AI". But that is a wild take to me. I wish you the best of luck with it. Not in a facetious way. I just personally don't think that's a great way to go about thinking about code. But what do I know vOv
@smolbrain It's okay to disagree. Best of luck with your getters and setters!
@lina What if somebody is using AI to write non-boilerplate code?
Install bonfire.cafe
Get the full app experience
@lina I agree with this 100%. 15 years in software development and I still haven't seen boilerplate code in the wild. Knowing programming paradigms, patterns and refactoring helps much more than coding agents.