this post was submitted on 14 May 2026
190 points (96.6% liked)
Technology
84646 readers
4308 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Since you brought up the notion that we might be doing different styles of development, I was giving you context as to the kinds of development that I do. Sounds like we might not be doing such different scales of development after all, but I couldn't have known that until you gave that information just now.
This isn't supposed to be some kind of duel or argument, I don't see the point of that. I'm just explaining my usage of coding agents and specifically unit tests in that context. Since that's what you were questioning.
I see it seemed more like a weird flex.
Anyways, I couldnt possibly deploy with any confidence a large project or honestly a small project I expected someone to rely on without layers of test. Unintended consequences of even a small change are just a reality. And with the expectation to move quick with large legacy systems, if you don't have tests that's a dangerous high wire act.
Well, I've seen large projects without extensive unit tests before. The main time I remember a big project with them before coding agents they were largely a checkbox that developers implemented with a grumble when first deploying a new system and then that were slowly disabled one by one as later changes broke them.
These were stand-alone projects, though, with a large QA department and without an expectation of future versions directly descended from them once deployed. If it worked then it worked, that was all that was needed at the end of the day.
never had a large qa team. And my experience has when we have qa resources, people move to the new feature so it's up to the developers to not break the critical features everyone forgets about until they break. And I've yet to meet a developer that has time to also be a full time qa resource
I meant my first sentence to be an apology for jumping to conclusions but it clearly isn't. It's late. Sorry for the snarky response.