←back to thread

Ask HN: How can I consistently deliver high-quality work with minimal issues?

25 points llll_lllllll_l | 1 comments | 21 Nov 24 14:53 UTC | HN request time: 0.201s | source

TL;DR: What are your checklists, tips, and tricks to ensure you're delivering a high-quality piece of work (whether it's a Pull Request or something equivalent in your field)?

As a full-stack developer, I've often found myself in situations where a sprint goes wrong, and a lot of bugs are flagged by QA. It's a tough spot to be in because I genuinely put in my best effort when coding, but sometimes things just don't go as planned. It could be due to a new feature, an old legacy system, or simply a rough week—it happens from time to time (not so often, I remember like 4 moments in my 5 years of experience). What advice do you have for maintaining consistent deliveries with minimal bugs (or equivalent failures in your area)?

1. nicbou ◴[22 Nov 24 00:15 UTC] No.42210040[source]▶
Remove the small errors to stay focused on the big ones. Use typed languages, linters, unit tests and the like.

Don’t trust your future self to remember anything. Not that the logic needs updating in multiple places (single source of truth!), not the steps of a process (scripts!), and not what you need to do (lists and flight checks!)

When something goes wrong, treat it as a learning experience and set up a countermeasure. Mistakes shouldn’t happen twice.