Skip to content
Source

About Bugs

A bit of post-Friday observations. On one hand, at work you should be engaged, try to understand better and better how your project works in every aspect. This makes you stronger, this makes you more useful and more expensive. On the other hand, people who came up with the phrase "the less you know, the better you sleep" are not fools either. Because your own sanity is more valuable to you.

Most bugs in code are some minor things that are almost clear at first glance. If they are stably reproducible and are somewhere in a visible place, then fixing them is quite simple. But the rest - these are the most interesting.

Sometimes you learn about what you'd better not know. You stumble upon problems after which you ask yourself: how did this even work before, if this is written here? You start digging deeper, looking for a solution to the problem and it turns out that it's generally global, you literally everything works this way and has always worked this way. Well, that is, it doesn't work and never worked. No one just ever found it. The author of the problem is somewhere no longer with you. It's either you from the past, who was stupid and just forgot something, or someone who already quit long ago.

Solving these detective problems is one of the most interesting parts of work. But the process itself, really, is not very. A lot of suffering, and the result is a grain of experience gained in some minor thing. Well, and the feeling that we all live on a powder keg where we don't control anything doesn't add peace.