Pretty useless without a definition of what it meant by "grumpy". I've been a grumpy developer before because I didn't like my job and was constantly getting a

Pretty useless without a definition of what it meant by "grumpy". I've been a grumpy developer before because I didn't like my job and was constantly getting asked to work on waste of time projects that ended up getting thrown out, which I knew would happen. I should have fixed my attitude and been a more productive member of the team or quit and given professional feedback in the exit interview that might have helped them. I've been called a grumpy developer because I pushed back against a culture of unpaid overtime and 60 hour weeks for the developers and 4 hour days for everyone else. I've been called a grumpy developer because I pointed out technical problems with a proposed project or insisted that someone technical be involved in setting deadlines for the technical portion of a project. First you need to describe what you mean by grumpy. It's a broad word. I was interested by the headline, developers have to deal with always trying to find problems or potential problems in things and it can colour how you view the world. We do seem more grumpy than average. It turned out be be a bunch of words tacked around the idea of "don't be sad! be happy!". We aren't in kindergarten, if I wanted childish advice without nuance I will go to the self help industry. Also the advice telling developers not to publicly critique issues they disagree with is insane. The goal is a community striving towards improvement. Your self esteem issues can be handled by learning to ignore online idiots and learning to separate your self worth from your code (and definitely from the software tools you have chosen).