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.
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 something that seemed critically important early in your career but matters much less to you now? For me, being the smartest person in the room has become a lot less important than being part of a strong team.
If you were given one extra hour each workday that had to be spent on professional development, how would you use it? I’d probably split it between learning new tools and studying how other industries solve similar problems. How would you invest that time?
Do you think the best engineering decisions are usually the simplest ones? The longer I’ve worked on complex systems, the more I appreciate solutions that are easy to explain.
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?
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