Measure twice, cut once. Carpenters have known this for more than seven thousand years. The proverbs suggest that you double-check your measurement for accuracy before cutting a piece of wood because, if it is inaccurate, you must cut a new piece, wasting
I do think that sometimes it's ok to not come back to understand the root cause, and be satisfied with the lucky fix. I had such a case just today, where we touched an area of another team, and we had a bug, and suddenly it dissappeared - I think because of a cron job that runs every hour and does something, but I'm not sure.
I can go deeper here, but I think my time is better invested in other things.
Thanks for the mention, Akos. I'm glad I could encourage you in some way. I also felt the same with other people in the community when I started. And I think that's the beauty of what we are doing here :)
About the post, you just triggered a memory of the template I have for these situations. It's called "🧪Labnotes debugging". When I need it, I go completely into an experimentation mode, getting rid of my biased understanding of the problem and approaching it with fresh eyes. The name and emoji help me get into this "scientist persona".
As you mentioned, we identify and understand with experiments and finding reproducible behaviors. Taking notes of these brings a better understanding. Only then we have the knowledge to go for a solution.
Thanks for the shoutout Akos!
I do think that sometimes it's ok to not come back to understand the root cause, and be satisfied with the lucky fix. I had such a case just today, where we touched an area of another team, and we had a bug, and suddenly it dissappeared - I think because of a cron job that runs every hour and does something, but I'm not sure.
I can go deeper here, but I think my time is better invested in other things.
Thanks for the mention, Akos. I'm glad I could encourage you in some way. I also felt the same with other people in the community when I started. And I think that's the beauty of what we are doing here :)
About the post, you just triggered a memory of the template I have for these situations. It's called "🧪Labnotes debugging". When I need it, I go completely into an experimentation mode, getting rid of my biased understanding of the problem and approaching it with fresh eyes. The name and emoji help me get into this "scientist persona".
As you mentioned, we identify and understand with experiments and finding reproducible behaviors. Taking notes of these brings a better understanding. Only then we have the knowledge to go for a solution.
"Measure twice, cut once."
Spot on Akos! That's how bugs should be solved.
Sadly, most of the time, only bugs that block the business come into the queue and it's a mad scramble to get things working...