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 engineering discipline would you recommend new students specialize in (or avoid) given the current/future job market?

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’s the biggest productivity killer in your typical workday? For me, it’s usually constant context switching between unrelated tasks. It feels like losing momentum over and over again. What’s the biggest distraction where you work?

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.