Have you faced pushback for setting boundaries?
1
Have you faced pushback for setting boundaries?
Do you think engineers spend enough time thinking about the user experience of internal tools? I’ve seen teams tolerate painful internal systems that they’d never ship to customers.
How do you handle disagreements with your manager about technical decisions? I’ve learned to pick my battles and always come with data instead of opinions when I do push back. It doesn’t always work, but it at least keeps the conversation productive. How do you approach it?
What’s something that seemed critically important early in your career but matters much less to you now? For me, being the smartest person in the room has become a lot less important than being part of a strong team.
What’s one engineering “best practice” that you think is actually overused or applied in situations where it doesn’t add much value? For me, it’s excessive documentation on very small, low-risk changes. Documentation is important, but I’ve seen teams spend more time documenting simple fixes than implementing them. Where do you draw the line?
What’s the greenest flag you’ve seen in an engineering team’s culture? For me it’s when senior engineers ask questions in public channels instead of always having the answers. It normalizes not knowing everything and makes it way easier for junior folks to speak up without feeling like they’ll be judged.
The most pushback I had ever received when I tried to set boundaries was when I was trying to backtrack all that I had been doing. Trying to set boundaries after it had been a free for all for so long was very difficult and took a long time before the dust settled over it.
Not really. My managers have been supportive.