There are great things about being “just another developer”. You never burn bridges, your job is stable and respectable, your coworkers and bosses like you or are, at worse, indifferent to you beyond the work you do. Being just another developer is the best thing you can be if you’re interested in a long term, stable commitment with minimal controversy and stress.

And it is totally not for me.I admit, I have a terrible habit of speaking my mind. I have sometimes outlandish opinions. I often want to modify processes that I feel are either inefficient or philosophically incorrect.

I want to make things better.

Projects can go a long way with a steady group of non-offensive nose-to-the-grindstone developers. Things get done, commands get followed without question. And things stay the same.

Little annoyances stay little annoyances. Pain and friction points stay painful. Nothing changes, or changes so slowly that no one is around long enough to see the changes start to finish.

Being just another developer is anathema to kaizen.

I know, that’s a bold statement. It’s also potentially offensive to any numer of very talented, very smart people who just don’t see their work as something to get stressed out over.

I’m not trying to be insulting to those people. I don’t question their talent, intelligence or skill.

I have it in me to stress out. I have it in me to hear, “But you’d have to get buy in from everybody else,” and think, “Sure, why not?”

Yeah, changing things can be a lot of work. Putting yourself out there can be a huge risk, especially if you put yourself out there for something that doesn’t pan out. It’s a huge risk with no measurable reward.

I wouldn’t suggest it to anyone.

But I doubt I’ll ever change my personal outlook on it. I take too much personal pride in pushing forward the best changes that I can.