You come across an issue that just ain't getting fixed in a short amount of time? What goes through your head, what do you begin to think about?
For further actions, you may consider blocking this person and/or reporting abuse
You come across an issue that just ain't getting fixed in a short amount of time? What goes through your head, what do you begin to think about?
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (24)
redo the whole project lol
not necessarily what exactly needs to happen to fix it, but how can the whole team be involved in fixing it so that it doesn't happen again. With everyone getting involved it:
if the bug is hairy as u say i will start with roots and re-build the whole code without rewriting it just double check everything and i hope u were using any kind of version control just print everything
I'll start suspecting a race condition or some other concurrency issue. These are usually the hardest to detect and kill.
Why fix it when I can make it a feature? 😁
The greatest part is the users might get used to it and fixing the bug may create churn 😁😆
“It's not a bug, it's a feature (now)!“ :D
Given that I have the privilege of just hacking and making it up as I go, this is half my day I swear.
My thoughts turn to mitigation and isolation.
First things first, how can I make it livable for however long I have to live with it? Can I put a cron in to restart a troublesome service? Can I add more retries to talk to a box with a bad network? Can I wrap a bad library with something that makes it less bad?
Second, how can I contain the problem so when I want to fix it properly I can do it quickly and without hurting the rest of the system? Interfaces, facades, etc.
Finally, I like to document how much the issue hurts the team in terms of lost productivity and hours spent messing with it - never hurts to have ammo to convince stakeholders and supervisors that we should make a persistent problem a priority.
How long has this bug existed, and is it generating issues for customers?
Can I present a work-around approach to the team to mitigate the bug's impact?
Can I make a business case to management/client to allocate resources to fix this bug? What are the costs to repair the bug? What are the costs to ignore the bug?
Can I add telemetry data or traces? Keep gathering data, which over time will give me enough information to formulate a hypothesis. Hopefully.
It's a feature leave it like that 😂😂
Usually if a bug is taking long to trace, then its better to sleep over it. Most of the times its just a wrong approach one is taking in tracing it. Also its better to take such bugs at the end, if they aren't show stoppers, to save and spend valuable time on being actually productive.