I am that kind of lazy. It works fine for me, but I have doubts about how valuable it is to my employer. The first bad case is that other, non-lazy developers d

I am that kind of lazy. It works fine for me, but I have doubts about how valuable it is to my employer. The first bad case is that other, non-lazy developers don't feel any resistance to the repetitive tasks in the first place. When I make a script to parse help desk tickets, it only helps me because they don't adopt. The second case is when they don't trust scripts, and prefer to work from their own understanding. The third case is when they have ways of doing things (mostly reading code directly) that I would approach with a tool to make finding the problem easy. I suspect that if I spent my time 100% on things that go into the codebase, the end users would be forced to use them so my efforts would be more fruitful for the company. I'm not going to expect to be able to persuade people to try Cygwin in my next job. If there's not an institution supporting my scripts they're not going to scale. So I guess don't hire a lazy developer if everyone else is happy doing it the hard way.