[BackwardSpy]

I do. I seldom find frustration when I am programming. It's very rare that I come across an error that isn't entirely my fault. A flaw in my understanding is a learning experience. A mistake in my typing takes a simple correction, and perhaps an improvement in my tools to highlight or even automatically correct the mistake in future. I don't find this annoying.

Occasionally an issue presents itself that requires more than a simple tweak to fix. Sometimes these issues require totally rethinking my view of the problem. I find enjoyment in problem-solving.

On the rare occasion that a problem lies within a tool or library I'm using, at the very least I can usually raise it as an issue somewhere. In some cases I have been able to fix the problem myself and submit a pull request for it.

Sometimes frustration happens. I find it helps a lot to walk away from my desk for a few minutes, and come back later with fresh eyes and a clear head. Talking through a problem with someone else often highlights flaws in my logic.

[itronitron]

Have you ever worked in an organization where you were strongly discouraged from refactoring, or otherwise touching, the code without a change request? And if the answer is yes how did you deal with that?

[BackwardSpy]

Thankfully I have not. I currently work in a small team (<10 developers). We try not to change things just for the sake of changing them, but when there is a good reason to do so then we can. Our code base is far from perfect but I am content with our ability to fix issues that would make it painful to work with.

I don't think I would be happy in a job where I didn't have this freedom.