←back to thread

25 points llll_lllllll_l | 3 comments | | HN request time: 0.413s | 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. aristofun ◴[] No.42207103[source]
This is literally what seniority/experience means.

This is why more experienced developers get paid more — because the deliver more consistent, higher quality, less issues work.

You work more, on more projects etc. and you eventually grow. Doesn't matter at all which tricks, approaches do you use.

The best investment in you quicker growth - is to find bigger, more complex and important project to tackle, and better team.

replies(2): >>42207507 #>>42208248 #
2. nasmorn ◴[] No.42207507[source]
Today I tested a feature in production that integrates with another system where I fetch how much to delay our data feed for some customers. I kinda remembered we were talking about the delay being an extra 5s but the numbers I got from their prod service amounted to an extra 30s. I flagged it up and it turned out all the other people on the team for the other service simply never checked that they actually input the correct data. Luckily they now have time until tomorrow to fix it.
3. llll_lllllll_l ◴[] No.42208248[source]
This makes sense. It's just like, sometimes is really hard to see how to keep improving on the quality besides failing and learning with it.