←back to thread

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

25 points llll_lllllll_l | 2 comments | 21 Nov 24 14:53 UTC | HN request time: 1.141s | 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. brudgers ◴[21 Nov 24 20:23 UTC] No.42208233[source]▶
1. If the work is actually hard, your software will have bugs along the way.

2. Big projects do not look finished until the end.

3. If you want to dominate the dojo, only fight children.

4. The creative process is messy and mostly unsuccessful. Assembly lines are neat and predictable…

…the sprint model comes out of consulting where the goal is to do the same thing that’s been done before.

5. QA’s job is to find bugs. They are part of your team. They are not your opponents.

Good luck.

replies(1): >>42208405 #
2. llll_lllllll_l ◴[21 Nov 24 20:40 UTC] No.42208405[source]▶
> 3. If you want to dominate the dojo, only fight children.

hahah, love it, thanks!