←back to thread

25 points llll_lllllll_l | 1 comments | | HN request time: 0.208s | 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)?

Show context
gregjor ◴[] No.42205382[source]
Four bad moments in five years? You should tell us your secret.

All kinds of things can go wrong when programming. Sometimes you don't have control over them. Very often you can't reliably predict them. You get better at knowing yourself and what to watch out for with experience, but even the most experienced programmers run into unexpected issues. And have bad days or weeks.

replies(1): >>42205799 #
1. llll_lllllll_l ◴[] No.42205799[source]
haha, yeah perhaps I removed some examples from my counting. I see your point, we dont know what we dont know