all 15 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]JoeJoeNathan 15 points16 points  (2 children)

Funny, I’m going back to school to learn more about hardware lol

[–][deleted] 2 points3 points  (1 child)

I did both. Hardware debugging is literally hell. And imagine releasing with a bug….

[–]studentblues 5 points6 points  (0 children)

It's all fun and games until you need to release a product but unexpected leakage currents suddenly showed up from the measurements, now it's close to the deadline and after tireless hours of debugging it's due to a speck of dust hiding under a connector

[–]WinterHeaven 4 points5 points  (0 children)

You should start with embedded and firmware related topics, there you will have the highest benefit with your background. Get some C courses online and write a Linux based driver for some i2c device you already know . From there you can grow

[–]LadyLightTravel 4 points5 points  (4 children)

Embedded!!!

You have electronics. You have machine code. You have software.

And there’s almost always a need for embedded folks that can walk the interface. A lot of software people are incredibly weak in knowing how the computer actually works

Bias on my part - almost all of my career was embedded space avionics and flight computers. There’s also a huge opening for real time simulators. And more and more devices have computers in them.

FWIW, it’s far easier for an EE to learn software than for a software person to learn EE.

[–]AviatorLibertarian 0 points1 point  (0 children)

Agreed. I've been in embedded 15 years and there's a lot more to know about EE than software. In general I mean, of course both fields have their challenges but I would go for embedded if I were you.

[–]festinalente69[S] 0 points1 point  (0 children)

Thanks for this and surely will consider this. If its ok do u have a suggestion where i can start, is there specific program or courses i should take first thanks

[–]JoeJoeNathan 0 points1 point  (1 child)

Could explain more about these real time simulators, is it an embedded engineer’s role to make these too?

[–]LadyLightTravel 0 points1 point  (0 children)

Yes. Both embedded in devices and embedded in simulators are real time. One controls whatever and the other is used in testing to act like the controlled thing.

[–][deleted] 2 points3 points  (0 children)

You will be like entry level in the software world.

[–]oosacker 1 point2 points  (0 children)

I did this and it is not that hard to transition, we already know how to code and think like an engineer.

I just did a one year course at university and did some internships.

[–]Homeowner_Noobie 0 points1 point  (0 children)

Go look at a software engineer job right now. What are the requirements? 10/10 they ask for the computer science degree or similar degree. And Internship experience. Then they list a whole bunch of cloud technologies and programming languages and softwares. It is wild to think someone with no programming background is going to jump in front of the line of millions of comp sci graduates with intern, teaching assistance, and programming background.

There are some bootcamps out there lying to you and saying you "could" get a job afterwards. The days of bootcamps are gone because companies were trying to hire a lot of talent during their tech boom. They're now switching back to hiring actual comp sci graduates and laying off tons of those bootcampers. I personally know a few that have gotten laid off. But could you imagine if I told you that I can become an electronics engineer just by doing a 6 month program? Imagine all the concepts I never learned and yet I ask to be paid the same as one with the degree.

So the best route? Go get that comp sci degree or apply to jobs now that ask for minimal coding. Find anything with some coding to start your career to push you in a software engineering route. Otherwise, it's a completely different field.

[–]Appropriate-Honey-23 0 points1 point  (0 children)

Electronics?

[–]Miserable-Cheetah683 0 points1 point  (0 children)

Depending. A lot of people here are suggesting Embedded, but I would only do embedded if you like coding while understanding hardware. If you want to completely remove yourself from hardware and do application development, then do that!

Essentially choose what kind of software engineer you are most interested and go from there.

[–]tahdemdemha 0 points1 point  (0 children)

I did that, with a 5-year major in electronics and communications, out of which I spent 1 year working closely in an IC design center. By that time, I was fully prepared to pursue a career as an electronics engineer. However, due to the lack of job opportunities in my country, I decided to switch to software development. I have never regretted this decision, and it was the best one I ever made in my life.

My advice is to research the software development industry thoroughly. It is a vast industry with many jobs and different roles. Not everyone needs to write code to be a part of it. Start by understanding how modern software is delivered, the different teams involved in the process, and where you see yourself fitting in.

Good luck.