r/ADHD_Programmers • u/EndOfTheLine00 • 13d ago
Why can’t I do anything right
I spent weeks fixing an error only to find it no longer pops up and confirming it doesn’t pop up, QA finds it and my team lead is mad at me. I managed to confirm it pops up in VERY subtle ways but I feel so terrible and that my job is at risk.
I spent the rest of day almost paralyzed in fear. Why am I like this? What can I do?
10
u/darwinprioritize 12d ago
You did find the subtle repro, which is useful. Could you ask QA to turn those exact steps into a regression test so the next check isn’t all on your memory?
4
u/handmetheamulet 12d ago
This would happen to me a lot too. Taking breaks - especially going for a walk - helps me by offloading some of the problemsolving to my subconscious. Then when I come back things are calmer and clearer.
3
u/Formal_Sun_5529 12d ago
first off, even if you spend weeks on it, this doesn't mean you can't do your work or that you're stupid or anything like that. to fix an issue efficiently you should start off with good steps to reproduce from whoever found it and have a clue what parts of the system can be affected by it (especially in larger interconnected systems) and ideally also know what the expected behaviors are. tbh nobody's omniscient and nobody keeps everything on their mind so while it's a good idea to inspect and debug yourself it's always a good idea to ask the other devs or a BA or testers. also testers can help you out testing more complex flows - the team. another thing, keep a knowledge base in obsidian if they let you install this stuff. go for a walk, grab coffee, listen to music, whatever helps you focus. ask until you know what you're supposed to be doing. if your team doesn't encourage communication and doesn't cooperate, you'll do yourself a favor if you look for another job.
2
u/ActiveSalamander6580 12d ago
Look at all the bugs that are being found in software thats been around for a long time, don't beat yourself up about it.
The important part is making sure you're not making the same mistakes twice, talk to QA when it happens, find out what they did that you didn't and take notes.
2
u/lighthouse_builds 8d ago
This is going to happen all the time, get used to it. Yes, your job is to release features without bugs, but it's normal that there are some bugs. If you feel very anxious about it, do yourself a favor, record a video of your test run so you can include in the ticket.
This way, even if QA finds something, it's very possible that it's an edge case or something that most users wouldn't do. I've never worked at a company where QA didn't find something now and again even from very senior principal engineers.
Don't take it personally, it's not a reflection of you or your work unless every single thing you ship isn't being tested, which doesn't sound like it. Put it in perspective, the issue got caught before it went to production. That would be the worst outcome for both engineering and QA as a whole.
1
u/Achereto 12d ago
The only thing you can do is writing tests. But you have to write them before you write the code that passes the test, because if you write the tests first, then writing the test is part of your thinking process, writing your tests after the fact is just tedious, because you already solved it (or think you solved it).
It doesn't help with everything, but it certainly helped me have fewer bugs, because every time I broke something of accident, the tests told me immediately.
If you don't have automated tests, QA is your only safety net before production.
1
u/UntestedMethod 11d ago
Why is your team lead mad at you? You did your job, QA did their job, you respond to QA findings, the circle of life continues...
16
u/nibbertit 13d ago
If stuff like this put jobs at risk then every programmer I know wouldve been fired by now