this post was submitted on 22 Jul 2026
437 points (98.4% liked)
Technology
86580 readers
3718 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
Why though? Aside from blind hate, good written JIRA stories are almost oneshot now in many occasions. You can spend more mental energy on logic correctness rather than translation of requirements into code.
Not only it is faster, but you can deliver greater quality faster. Slopware is a result of trying to crank the dev speed to the max without following proper sdlc with proper dod.
The company I work at has fully embraced vibe coding, so from my experience: it did seem faster at first, but also the amount of regressions and new bugs being introduced has gone up dramatically, and so the overall workflow has stabilised to be roughly just as fast as before AI, but now almost all mental energy is going into QA and reviewing. From the customer perspective, they saw lots of new progress initially, but have now been frustrated by constantly finding things broken or buggy.
And all this is at a company which has entire teams dedicated to trying to improve AI-based workflows and tools to make them more reliable.
So no. From someone in the field, quality has dropped a lot, and speed is only increased if you close your eyes and ignore all the tech-debt being created.
Your devs do QA, not a dedicated team?
Unit tests, snapshot tests, UI tests?