From coding whore to opinionated developer?

January 05, 2009 | 1 Minute Read
This post was originally posted on my old blog.

Have you also been on projects where things were done entirely different to your own opinions.
Maybe they totally contradicted values that are most important for you? But you coped and went along?
Did you feel compromised, even dirty, for not resisting? Did it make you feel like a coding whore?

37signals and Ruby on Rails shaped the concept of opinionated software.

As most ideas from 37signals, I like the concept of opinionated software.

Now I am wondering if the concept of being opinionated could be extended from software to ... the developer?

When coming to a new project, take a good look! As a developer you don't have to put up with everything! Evaluate your opinions:

No Source Control? - Where is the exit, please ...

No Unit Tests? - Thanks, I am out ...

Continuous Integration is a foreign word? - Sayonara from me ...

Staging, what is that? - Good bye ...

Stakeholders are not readily available? - These boots are made for walking ...

...

Is that being arrogant?
If you have opinions, why should you not commit to them?