←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: 0.486s | 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. zghst ◴[21 Nov 24 17:38 UTC] No.42206644[source]▶
Keep ahead of the industry, keep up with blogs and industry influencers for trends, new APIs, patterns, etc; write tests, look at others’ code, practice good coding patterns, always ask a lead/senior to do some pairing when you’re struggling (that’s what I did to help a lot of other developers in my career), ask for feedback/temperature check during 1-on-1s.

Lots of options, some of them require swallowing your pride and putting effort in.

replies(1): >>42208226 #
2. llll_lllllll_l ◴[21 Nov 24 20:22 UTC] No.42208226[source]▶
About asking feedback, what would be good points to ask exactly? I didnt have good experiences with feedbacks in my career, usually they were too vague.