How do you decide when to keep digging into a problem versus stepping away? I’ve learned stepping away usually helps more than brute-forcing through frustration.
3
How do you decide when to keep digging into a problem versus stepping away? I’ve learned stepping away usually helps more than brute-forcing through frustration.
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?
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?
What’s one thing that new employees often underestimate when starting a new job? In my experience, it’s how long it takes to learn the informal processes and relationships that actually make things happen. The technical side is often easier to pick up than the organizational side. What do you think?
I've been stuck in a pure maintenance cycle for six months, and I'm starting to feel like a script-runner instead of an engineer. I'm trying to move into a senior-level job, and I worry about stagnating, but I'm not sure what to do. Is this a common issue with engineers who hope to level up?
I made the mistake of being friendly to a new teammate, and now they're attached to my hip. They invite themselves to every break I take and get visibly upset if I grab coffee or lunch with anyone else. I'm feeling suffocated. How can I politely tell them I need space?
If you can afford to step away without any major impact then it probably isn’t worth your time
It's a terrible mentality that is unfortunately true because how modern business runs. Shoot the 70% solution now and make corrections later as needed. For now just stem the impact to the customer.
Sometimes stepping away and giving it a rest is the best thing to do , sometimes the answer will come out of the blue when you least expect it
Sometimes asking up the chain of command how important it is can help decide whether you should devote your time because your time may be valuable in other ways too. Of course, some digging in for details helps the original developers find a bug or find an alternative way to do what you need to do.
I step away when I get stuck for more than a day
Good advice