Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I feel like I'm constantly fighting this with my manager at my current company. I receive a lot of feedback along the lines of, "well every other company I've worked for did it X way." For example deployments: company policy is that anyone can deploy any service from master at anytime, so if you merge your code into master, you're saying "this code is ready for production." My manager kept telling "we" should fix that because every other company he worked for deployed from staging into production.

I've found managing situations like this to be the hallmark of a good architect / high-level engineer. I really admire people who are able to think quickly on their feet and push back against people who push for ignorant or unnecessary changes. And it is something I am not good at.

I've taken to silently fixing peoples' mistakes as to avoid these kinds of discussions. While I'd really like to say, our architecture did not force you to push broken code into master hours before you went on vacation, my (agreeable) personality prevents that.



As an engineering leader I always insist that everyone follows the "ice cream" rule in any debate or discussion about how something should be done. Only technical merit counts. Never personal taste.

Whether it is a design pattern, deployment strategy, or choice of language, if your argument has no technical advantage then you are just expressing your taste preference. This is where someone will likely call you out by asking, "are we discussing technology or ice cream flavors?"


> This is where someone will likely call you out by asking, "are we discussing technology or ice cream flavors?"

I'll steal this and see how it turns out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: