this post was submitted on 29 Apr 2025
97 points (88.2% liked)
Technology
69491 readers
4109 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
I'm a dev and I hate releasing buggy code but I'm not in charge of testing or the amount of testing we do before release.
I’m also a developer and I’m really big on optimizing database queries and having the right data indexed. When I review others’ code I’m being “nitpicky” when I point out that an index is missing. When it comes to query optimization I’m often told “well there’s plenty of memory.”
Aren't you though? I'm a dev too, and at the end of the day, I'm responsible for the correctness of my code, even though we have a QA team that also helps with testing.
You don't test your own code as well?
I write unit tests and test my own code, but we also have UAT tests that are completed by others independently. Complex systems with lots of moving parts require lots of testing.
Technical testing still leaves a lot of potential issues with business rules, UX etc...
But you can validate the business rules with the people that make them: the business or your users?
I get some companies do things pretty fucking backwards and QA as a separate function is harmful, pointless and should be abandoned.
However, I don't see how anyone from QA is going to physically stop your from testing and validating your code. As a dev, you could be more proactive in understanding what you're building, why you're building it, and how to make sure it works and it does what your stakeholders/users need it to do.
If you don't, then refer to OP's post.
Oh I get that. Just sounded like passing all testing responsibilities off to others.