I’m a “software engineer.” One of the most interesting jobs I’ve had was working on a team of (mostly) electrical engineers at an industrial tool manufacturer. Most of the team designed electronics (primarily IC’s) for the controls. A few of us designed software that interacted with said controls.
That experience taught me that engjneering, at its core, is just solving problems in a given domain with a a specific set of “tools”. I was amazed by how much thought process overlap there is between software and electronics engineering.
My job is solving business problems. Writing code is auxiliary to that. And even though I don’t have have a degree or any certifications, none of the people on that team ever talked down to me or tried to make me feel inferior.
I’m a “software engineer.” One of the most interesting jobs I’ve had was working on a team of (mostly) electrical engineers at an industrial tool manufacturer. Most of the team designed electronics (primarily IC’s) for the controls. A few of us designed software that interacted with said controls.
That experience taught me that engjneering, at its core, is just solving problems in a given domain with a a specific set of “tools”. I was amazed by how much thought process overlap there is between software and electronics engineering.
My job is solving business problems. Writing code is auxiliary to that. And even though I don’t have have a degree or any certifications, none of the people on that team ever talked down to me or tried to make me feel inferior.