-14
What could go wrong with coding and AI usage, right?
(jeferson.me)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jul 2026
-14 points (23.1% liked)
Programming
27744 readers
477 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Sounds about right. Fits in with the 80:20 rule. Does the first 80 quicker than the 20% of time it usually takes but does the next 20% which takes 80% of the time even slower.
Effectively, it optimises the quicker bit so you suffer long term and overall waste more time while screwing the planet. It's only fine for prototyping and even then, would that be the best base to build off? Is it modular and maintainable? Does it have low coupling and high cohesion? Or is it just trash?
Heavily coupled code with a lot of duplication of code. These are the main points of the refactor.
There is some lack of "smart" use of the JS, like the positional arguments instead of objects (for quick fix/change), no separation of concerns, there is something lightly there, but lacks the gross thing.