this post was submitted on 13 Mar 2026
-23 points (17.1% liked)
Programming
26036 readers
103 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All the code I review looks good at first glance and makes shit up as it goes once you read into it more. We use two different HTTP libraries - one sync, one async - in our asynchronous codebase. There's a directory full of unreadable, obsolete markdown files that are essentially used as state. Most of my coworkers don't know what their own code does. The project barely works. There's tons of dead code, including dead broken code. There are barely any tests. Some tests assert true with extra steps. Documentation is full of obsolete implementation details and pointers to files that no longer exist. The README has a list of all the files in the repo at the top of it for some reason.
People are being laid off because of poor management and a shitty economy. No software devs are losing their jobs because AI replaced them. CEOs are just lying about that because it's convenient. If software devs truly were more effective with these tools, you'd hire more.
That's up to you to decide. Try using them if you want. But don't force yourself to become obsessed with them. If you find yourself more productive, then that's that. If not, then you don't. It's just a tool, albeit a fallible one.