Is this a hill you want to die on?
I once worked with a developer that refused to work on a feature as long as any detail was unclear. He would not work on an image slider if the duration of the transition between images was not specified.
There are disagreements in all teams about what we build and how we build it. Given several options, we need to understand each of their effects. Does a difference in millisecond influence the required development effort? Does it impact the experience of our customers? If so, let’s talk about the pros and cons of all options so everybody understands them. Only then can we make an informed decision together.
Our reaction needs to be proportional to the severity of the situation. We need to pick our battles by asking ourselves if there is enough of a difference for us or our users if we choose wrong. Don’t start fights that distract from what is important, don’t stay quiet when you see something going wrong.
PS: If you find this newsletter helpful, you would help me out a lot by sharing it with friends: domhabersack.com/newsletter
If you don’t find it helpful, hit reply and tell me why. I am still experimenting with both content and format and need your feedback on what is and isn’t working.
“Being busy” is not a good measure of progress. By focusing on what creates real value, we can make good use of our limited time.
Retrospectives that end after letting everybody complain are a waste of time. Turn that frown upside down for a better result.
Job interviews are tests for both sides. Use them to figure out if the company you are applying to is a place you really want to work at.