Do you think the best engineers are the ones who spot problems early or the ones who solve them quickly? I’m starting to think spotting them early creates far more value.

How do you know when it’s time to leave a job vs. stick it out and push through a rough patch? For me it comes down to whether the core reasons I took the role are still intact. If the work is still interesting and the people are decent, a rough patch is survivable. But if I’m dreading Mondays every single week, that’s usually a signal worth listening to.

Finally getting into AI in the way that I think it was meant to be used. Claude is a game changer. I was just using chat GPT to make goofy images. Claude can actually do work! Anyone else using AI in cool ways? Need some ideas

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?