this post was submitted on 23 Sep 2026
466 points (97.6% liked)
Technology
88209 readers
3480 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Companies have always pressured software teams to ship products as fast as possible.
What's new is the part where all of the worst coders can shit out code a lot faster and pretend like they're doing a good job. It used to take them a while to write garbage that they didn't understand or review themselves, but now they can do it so quickly that it makes the actual good coders look like they're taking a long time.
This is why you absolutely have to have documented coding and review standards. The idea that you'd ship any code that has never been reviewed by a human is horrifying.
The idea that you'd work 12 hour days is so stupid to start with. I've seen people consistently work that long and... surprise, they don't actually work that long. They work about the same as anybody else and goof off the rest of the time. I doubt you can even just press enter for that long. People just don't work that way.
AI in engineering is an accelerator. If you are producing slop software, which most teams are, then it's just going to accelerate the rate at which you can produce shitty software and bad code.
If teams are producing high-quality software, then it accelerates those teams' ability to deliver that quality.
Yes, and most engineers effect on the product can be graded on [-1, 1] scale. And I find that the -1s accelerates faster.
I had one of those. My seniors are getting dumber though, and we have twice as many prod bugs as a year ago. I had an outage because someone didn't properly trim an input for fucks sake recently.
This is exactly it. I’ve worked with 2 different teams in this new era. One has all strong engineers and good review and testing standards. The other has 20% bad engineers that should have been fired years ago and’s weaker testing culture. The result is the strong team is delivering higher quantity software faster than ever, and the other team is going fast with much worse results. The quality is very bad, and the good engineers still there are quitting.
The good engineers spend their whole days just trying to keep the ship afloat and minimizing the harm from the bad engineers. They hate it and are burning out fast.