Whether it’s explaining why the addition of a certain software feature is a bad idea or trying to convince your dev team that adopting one tool over another will kill the health of your stack, being a contrarian has kind of become part of a programmer’s job. But when does saying “no” too often become a problem?
In a new blog at Triplebyte, programmer Stephan Miller describes both some times in his career when swallowing his contrarian attitude would have made him more productive at work and some when voicing his oppositional technical take could have actually saved his company.
How do you balance “going with the flow” with your strong “I know best” opinions as a free-thinking engineer? I mean, the wheel has occasionally needed some reinvention, right?
Share your thoughts below or in our blog conversation thread here!
Given that most programmers are treated like slaves and are compensated as such, they need to be saying "no," more often, if not all the time. Remember, not all software developers are on 6 figure salaries.
Given that most programmers are treated like slaves and are compensated as such, they need to be saying "no," more often, if not all the time. Remember, not all software developers are on 6 figure salaries.