Comment by coroxout | Hacker News Reader

Comment by coroxout | Hacker News Reader

Parent Full thread

"We're constantly thinking about all of the stuff that's gone wrong with our applications previously, what new things could go wrong with them now"

I really feel this. I'm supposed to be half coding and half support but the support has expanded to fill all my time and I don't write anything more than 30-line kludges that only I will see any more.

That's partly just the nature of support always taking up all the time, but also I feel really paralysed when it comes to coding, because I just think of all the stupid corner cases I've been bitten by and how bad it felt to lose data or cause downtime or just look stupid.

And yes, the answer might be "write more test cases, code review" but that little voice in the back of my head goes "you thought you'd caught all the edge cases last time, and it still did a dumb thing you'd never thought of". I find it really demotivating, and start to put things off until I feel cleverer (which I never do), and then my lack of productivity depresses me, perhaps to the point you'd call "burnout" even.

Well, glad I'm not alone. Any tips on thinking my way around it welcome.

You can try your best but bugs seem to me to be a necessary tradeof for “getting stuff out there”. Some are generally acceptable given that the applications we write these days generally aren’t for life threatening devices etc.

What I’d do in your situation is bring these issues up with the team and think of what if anything you can do to help reduce the amount of support tickets coming through.

I’d look at reoccurring support tasks and prioritise the proper fixing of these based on the frequency these tasks come up.

I’d raise specific bugs that have come about recently and ask if you as a team could have prevented these in any way. What lessons do these have for the future?

Maybe you can get a “story sign off” from the product owner once tasks are done you demonstrate that the feature works as expected.

Another thought is to write up more formal acceptance criteria with various scenarios in story cards “As a, I would like, so that”, “Given When Then” kinda stuff. Might need to google on that one.

Anyway, I think if you take the actions you can take and maybe reframe the way you think of bugs, you can rest a bit easier. Just remember it’s a team effort, and hopefully your team members can help pitch in to help solve these with you.

Reply on news.ycombinator.com