Have you faced pushback for setting boundaries?
1
Have you faced pushback for setting boundaries?
What was the biggest mistake you made early in your career that ended up teaching you a valuable lesson? One of mine was assuming everyone interpreted requirements the same way I did. Learning to ask clarifying questions saved me from a lot of rework. What’s yours?
It took me a long time to say it out loud, but I regret choosing this path. The pay is stable, but the constant pressure and lack of fulfillment are leaving me feeling like I'm ready to exit. I’m actually thinking about a total career change later in life. Has anyone successfully walked away from engineering after a decade plus?
I'm a junior engineer, but I inherited a project mid-construction because the designer left. I wasn't around for the early phases, but now I’m running the site meetings. I'm stressed about the technical gap and being asked questions I don't know the answers to. I don't want to appear clueless in front of the clients, even though I am. Is it okay to say that I don't know, but I will get back to them? Or does that look unprofessional?
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.
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?
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.