How can you expect a non software engineer thats never done software to do simpler code? Lol i find it so funny when experience professionals think u can do everything like them.
2
How can you expect a non software engineer thats never done software to do simpler code? Lol i find it so funny when experience professionals think u can do everything like them.
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?
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 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?
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.
I’ve been working in construction since I graduated 5 years ago. I’ve gradually realized I don't want to do this for the next 3 decades, but I feel stuck. Is it too late to switch engineering disciplines without destroying my career progression?
Companies expect all sorts of things. Companies will ask for 5 years of experience in a technology that has only been around for a year. Your job is to say yes and collect the paycheck as long as you can.
I mean, I was a non software engineer as well (optical engineering), but computer programming was part of my undergraduate curriculum and I could do simple coding (I learned Python, MATLAB, and C). So I don’t think it is an unreasonable thing to assume. If you can’t meet that expectation, then just be honest about that. From there though, I think the onus is on you to learn and try to meet the expectation. It is not unusual for the job you end up doing to not match your academic background. I had very little background in electrical engineering when I was first hired as an engineer and had to learn a lot on the job to fill the expectations of my job role. Now almost 15 years later, I can do a lot more EE work comfortably.
It’s a balance, there’s always going to be some learning in the job, but if you’re not meeting the expectations of your coworkers some additional training may be required
Claude!
Second the AI call, even if you don’t use it to do all the code you can definitely learn from it as well