| Maybe you should practice what you preach. I'm 34 now and I'd side with the OP on this. I did a similar thing on my first job: took their web app codebase and totally remade it in the first couple of months, with demonstrable gains on efficiency (Mind it: it was the first web application made by some guys whose previous experience was in Sybase PowerBuilder). I was given a raise the same week I demoed it to my bosses. I still do programming and I'm still being humbled frequently by the awesome things some of my younger coworkers code effortlessly. I also share with OP the impression that 8 hours coding as a daily thing is totally overkill. That's suited for factory work where every minute you're not cranking out stuff means losses. My 'sweet spot' for coding seems to top at 4 hours, a few hours resting and then maybe another couple hours at the end of the day if I feel like I found a better way to do it. Fortunately I have flexible hours where I work, but I'm still suppossed to put in 8h every day. The result is: when things go well, I complete my tasks and are left with at least 3 hours a day where I'm supposed to be working (so: no relax, no rest, you're on the clock); and when things are not going so well, mostly due to planning mistakes from high up, I have to put in my 8 hours, and then some more. So please, go tell to be more open-minded to the right people, and let people work to the best of their abilities. |