You find it, you fix it, and you're on your way. Simple. Easy. Quick. This is much preferred to some of the other problems you can fix as a software engineer.
At work (I'm an ops person) we have similar "bugs".
If for example a system runs out of RAM and the OOM-Killer is starting to semi-randomly kill processes.
It's similarly easy to fix (start the processes again), doesn't involve any "figuring things out" and so on.
However I strongly agree with the philosophy prevailing at work.
We don't want to fix such tasks, especially if they are repetitive.
Much more would we like to get rid of these tasks entirely to spend time with more challenging, meaningful things.
We would like to spend our time with the issues you "don't like":
The problems I don't like to encounter are problems with architecture, design, or dirty code. Admittedly these can sometimes be fun to fix, but they're much, much more difficult especially in a system that's been around for a number of years.
(not so much the dirty code though, unless it's about getting rid of it, or replacing it)
We'd love to fix architectural issues or design and build systems.
We don't want to fix such tasks, especially if they are repetitive.
I agree especially with the repetitive part. An old professor of mine said, "if it feels like a computer could be doing this, it should be doing this." Meaning that if you found yourself doing some menial task over and over again, you're doing it wrong. Get the computer to do it for you.
We'd love to fix architectural issues or design and build systems.
These are definitely the more exciting and engaging things to work on. They're also the most expensive things to work on from a business perspective. Fixing a broken architecture can take years depending on the software in question. I'm not saying it's not fun to do. I'm mainly saying that, if we design clean architecture and write clean code, the issues we'll have as we maintain and continue to grow our software projects will be much simpler to solve.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At work (I'm an ops person) we have similar "bugs".
If for example a system runs out of RAM and the OOM-Killer is starting to semi-randomly kill processes.
It's similarly easy to fix (start the processes again), doesn't involve any "figuring things out" and so on.
However I strongly agree with the philosophy prevailing at work.
We don't want to fix such tasks, especially if they are repetitive.
Much more would we like to get rid of these tasks entirely to spend time with more challenging, meaningful things.
We would like to spend our time with the issues you "don't like":
(not so much the dirty code though, unless it's about getting rid of it, or replacing it)
We'd love to fix architectural issues or design and build systems.
Thank you for sharing your comments!
I agree especially with the repetitive part. An old professor of mine said, "if it feels like a computer could be doing this, it should be doing this." Meaning that if you found yourself doing some menial task over and over again, you're doing it wrong. Get the computer to do it for you.
These are definitely the more exciting and engaging things to work on. They're also the most expensive things to work on from a business perspective. Fixing a broken architecture can take years depending on the software in question. I'm not saying it's not fun to do. I'm mainly saying that, if we design clean architecture and write clean code, the issues we'll have as we maintain and continue to grow our software projects will be much simpler to solve.