The problem is when your job is to get stuff out the door as quickly as possible. I just quit a job where I was writing primarily in a proprietary extension to a proprietary dialect of BASIC that has all manner of weird compiler quirks and just plain poor architecture. I knew there were ways I could do some better stuff long-term, but implementing them was completely outside the scope of the limited projects I was undertaking.
One of my earliest programming experiences was for a very primitive language. You had something like 26 variables total, all globals, and no flow control except GOTO. I ended up reinventing quite a lot of things to get even trivial programs working. I remember teaching myself loops, bitmasks and more, before I even knew what those things were.
Or that time I remember having to use VBScript. Someone had made an OCX marked 'safe for scripting' that would write out some assembly and execute it, allowing one to call any C functions that left the stack clean (e.g. Windows APIs). I remember finding some crazy ways to abuse that. I also remember turning a testing tool into a music player when I was bored.
That said, I understand not wanting to program like that 40-hours a week. I know it can be grating after a while. But sometimes, you can have a bit of fun by finding clever ways to expand the capabilities of very limited systems.