|
|
|
|
|
by fdlaks
616 days ago
|
|
It seems like I took the inverse path that you did, I went to school for EE and then transitioned into doing fullstack engineering. I don't want to discourage you from learning more about EE because it is fascinating and rewarding, but here are some things to consider before you sign yourself up for a degree: - Like others have said, EE is a very difficult degree to pursue. Studying power systems will probably save you from having to study too much of the really complicated theory, but there are still some strange abstract concepts you will have to have a good understanding of in order to know whats going on, and A LOT of complex math that goes with these concepts. Make sure you know what you are signing up for and if you like to study these types of things before fully committing. - EE jobs are probably marginally safer than software related jobs from being consumed by AI, but making this switch will not guarantee job security. When / if the day comes that AI takes 90% of developer jobs, so too will it take a massive percentage of jobs that EE's have traditionally done. Power systems design is already one of those fields that is largely done via computers. Being the person at a power plant that helps debug when things go wrong isn't going go be replaced anytime soon, but you can say the same thing about software related jobs as well (maybe AI does a lot of the groundwork in the future, so there will be less need for swaths of people to work on software but there will always be need for a human in the loop until we get to a super intelligent AI which is unlikely in our lifetimes) - Part of the reason I left EE to pursue more traditional software was because of how slow it moves and how much investment upfront you need to do really anything. It's also more difficult to get a job as a EE in general compared to software because of fewer opportunities in general and also companies not wanting to hire new people to make mistakes at their company before they figure out what they are doing and move on to not make mistakes at other companies. It's also an order of magnitude more difficult to debug problems you encounter working on hardware or power systems. A large part of learning how to be a good EE is understanding how to use all of the very expensive equipment in the lab to gain any kind of understanding as to what is happening with your project. Overall I would recommend taking some classes about power systems and see if you like it or not before committing. I honestly wouldn't worry about the AI super intelligence taking your job anytime soon, if anything software fields might start to get more interesting because we won't have to slog through writing so much boilerplate before getting to the interesting areas where people are actually needed to think critically about. |
|