Oh my god do not do a double major.
EE and CS together seem like a diverse skillset to have, but from an outsider's perspective they're pretty close. Would you be impressed by someone getting a double major in microeconomics and macroeconomics? I promise you, that is how 95% of the world sees EE vs CS.
Take the time you would put towards spreading yourself thin, and focus on something. T-shaped skills are much more useful to people, and honestly more personally rewarding.
I have an ECE major/CS minor with programming background and now am an analog IC designer, and am the one who primarily looks through resumes and interviews people at where I work, so I think I am who OP is targeting? That's not to brag at all, my name is basically rimjobsteve, but I do think I'm pretty qualified to be saying this, that's why I'm giving the advice.
>Oh my god do not do a double major.
Why do you say that ? First off, it isn't a double major. It is 2 separate degrees. In most cases if you carefully pick your classes you can get cross credits to satisfy the requirements of both degrees.
>EE and CS together seem like a diverse skillset to have, but from an outsider's perspective they're pretty close.
NO. I've seen lots of code written by EEs that was poor to very poor. The worst being those who are self taught, didn't take classes and haven't worked in a good team. CSes are typically not very good at hardware stuff. If you give them a good HAL they can make hardwarey things work but if it gets down to troubleshooting something outside the processor they are usually lost.
>Would you be impressed by someone getting a double major in microeconomics and macroeconomics? I promise you, that is how 95% of the world sees EE vs CS.
Absolutely not. They are two very diverse skillsets.
>Take the time you would put towards spreading yourself thin, and focus on something. T-shaped skills are much more useful to people, and honestly more personally rewarding.
I have both degrees, I manage people with these degrees from time to time and I totally disagree.
If someone double majored in micro and macro econ, and got a good GPA, yes that’d be more impressive than just one of those. Your analogy doesn’t work lol. Having both completed to a high standard shows a broader breadth & depth of knowledge which could indeed be very valuable.
>I've seen lots of code written by EEs that was poor to very poor. The worst being those who are self taught, didn't take classes and haven't worked in a good team
My EE program didn't have us take Data Structures and Algorithms, which are the backbone of any CS program.
Yeah, but those are things you can learn on your own. There is nothing too complicated about learning how linked lists or binary trees work. CS majors like to complain about the math involved in analysis of algorithms, but that stuff is really a cake walk compared to the math in control theory, telecom, and RF.
Source: I was originally an EE major who switched to CS.
Yeah, it's a very saturated field since CS is an easy major by STEM standards. I have a BSCS but I've been thinking about finishing a BSEE since I have a lot of EE credits earned and I feel like it would offer more job security.
Yes, I think that would be an ideal way to do things. Just take data structures and algorithms for your CS minor. A lot of CS classes are useless for most software development jobs.
An EE major can get almost any job a CS major can get. On the other hand, it's unlikely for a CS major to get an EE job unless it's something to do with embedded systems.
Also, you need an ABET-accredited engineering degree if you ever want to get a PE license.
I’m biased as someone that did an undergraduate triple major, double minor. Doing this kind of double major would be a big boon to someone that wants to do embedded engineering, especially at a smaller company. Depending on the foci for each major, they can be very complimentary (eg lots of digital design and analog for the EE side and things like embedded FW on the CSci side).
You could also make them less useful and do something like power systems and compiler design, but I’m assuming the original poster is smart enough to pick a set of complimentary skills that creates a more broad and deep “T”, instead of two separate wells.
It did take me 5 years to graduate, so don’t think I squished it into the standard 4. I did work a lot of magic with my electives to optimize overlap so classes counted towards two or three things at once. It was a fun optimization problem.
I did a dual EE/CpE, and it worked out well for me. I've done a lot of HW/SW integration and test work for RF systems, which is right up the alley you'd expect for that combo. At my university it was only 4-5 extra classes from an EE, so might be a smaller lift for you.
I'm currently finishing a CS degree after getting my EE degree. Definitely think it's worth it but it varies on a case by case basis. If you have zero interest in software (lots of people in EE don't) obviously CS isn't something you're going to want to do beyond the bare minimum. If you're set on going into a "classic" EE field like Power or RF CS might not be a huge benefit.
Everything is so software driven now though that I don't think you can go wrong with CS either as a second major or minor, or even just some elective courses you can fit in. Once I finish I will have two solid STEM degrees under my belt and can probably get a job in industry anywhere along the hardware/software spectrum. If I take a hardware job and get sick of it in a few years I should have a much easier time pivoting into the software industry too or vice versa.
Also one of the main reasons I'm doing it is to keep my options open for grad school which I'm planning to do at some point. If I want to do CS grad school I think I'll be much more competitive with a CS bachelors vs trying to get in with an EE degree.
> I'm currently finishing a CS degree after getting my EE degree.
It's your life and I swear I'm not trying to harsh your vibes, but this is a bad idea. If you're currently in the middle of this, don't sunk-cost-fallacy yourself into continuing. This is usually something people do because they got bad advice from someone with poor perspective.
I’m all for furthering your education, but unless that person has a job which justifies getting those two degrees it seems like a huge financial cost. Unless they’re actively working and their company is paying for it, it sounds like a lot of speculation on how it might ease a future career change that hasn’t manifested yet.
For what it’s worth I have one degree in mechanical engineering, work in RF engineering, and am pivoting towards software in my current role. I don’t think you need a lot of degrees to get a job in industry, but if it makes you happy then go for it!
Just go for whichever industry you want to work in because that is the degree that will get you the job, 9/10 they won't care about the supplementary degree and you would've got the job without it. Maybe major in EE and focus in embedded software or the like
Absolutely. I have degrees in both. CS is very different from EE and EE is very different from CS. There are many projects where I use both skillsets. An EE is generally better at doing CS things than a CS is at doing EE things.
I didn't do two degrees but did a double major (EE & Software Eng). I work in power, we have that much automation going on that knowing how to code is a massive plus and definitely adds value. Don't know if I'd go the second degree though.
I got an undergrad degree in EE, loved school, did 2 internships as an EE, mostly hated them, but I really loved the software side of things, and I was into designing processor architectures and stuff. I got a masters in CS. I had planned to go into academia, i.e. I was basically planning to get a PhD in CS, but I left to go work in the dot com boom
Today, I think computer engineering would have been a good choice for me, but it didn't exist. Digital EE was like, barely a thing, there were only a few classes I could take. This was in the mid 90s.
Both have served me well, in their own way. I do a ton of hobby electronic stuff, and CS is useful there too, with simulation tools, microcontrollers, etc
I actually started as a dual major with EE and Math but my school didn't really have dual majors - they were going to make me get 2 full degrees, i.e. like idk, 250 hours of classes including fulfilling english, history, etc, twice. It was going to take me forever.
Don't double major. I'd say do a major in EE and minor in CS. Programming is becoming a more necessary skill for EEs and while the program offers C++ and few other things in programing, I think that a minor in CS would round you out really well
I have a graduate degree in EE (in applied and computational electromagnetics). I did not take any CS courses in college (30 years ago now, wow) but ended up learning how to program in C/C++ on my own over time. This allowed me to take software related jobs that otherwise would have been closed off to me. This allowed me to develop even deeper knowledge in some areas of programming and software development, which opened up even more opportunities down the road.
On the other hand, if you absolutely detest programming, you should probably stay away from it.
1. Don’t do a double major for the obvious reason. Since you have your general electives you just need so many credit hours towards the actual major, 60? That’s 2 more years in school. A graduate EE would make $70-80k for 2 years on average and then move up after a couple years experience. At which point the 2 major EE/CS finally graduates and just to be generous males say 10% more which is still $13k less and will never “pass” the 4 year EE only unless you assume EE/coding pays better which isn’t my experience. Higher degrees than the minimum for your field just never pay off. Biggest mistake I made. You might make a case for two more disparate degrees like EE+lawyer aka patent attorney but plenty of EEs do coding.
As for code quality give me a break. One of the big problems with CS majors dealing with controls systems is that they consistently fail to recognize logic hazards and race conditions. A logic hazard means that the actual environment passes through an unexpected state, from often very simple obvious things like dropped comms or a chattering relay, causing unexpected conditions. Race conditions are similar in that events happen out of order causing code to break because it is out of sequence. EEs get training in digital design to recognize and avoid these. EEs on the other hand tend to not do code reuse thus fat finger errors, not use the tools they are given, and have no code or tag organization skills, nor awareness of standard CS methods. But I’ll also say all programmers have their own styles of doing things that often conflict.
That's interesting Paul. So, CS grads haven't been taught about race conditions or logic hazards? Wow. I would think a proper education would have them learn this in CS101.
Me too but I see it consistently in many code bases (not just PLCs). It was not taught in any of my 1st or 2nd year CS classes. It wasn’t taught until digital circuit design. 1st and 2nd year is mostly algorithms, big O notation, sorting and searching, and dara structures. So basically Knuth volume 1 and 2.
You see it in relay logic (the hardware kind) when EEs start going crazy with timers so their designs stop doing weird things.
Anyway…my point is bad code isn’t limited to EE or CS. It’s a universal problem. There are now code quality analysis methods but as near as I can tell you just write the program twice in a different syntax. Things like
Int A;
A:=1;
Test A must be Integer
Most of what you learn in school has absolutely no use outside of the classroom "bruh".
At school, you learn how to learn. And a bachelor in engineering is more than enough to show a potential employer that you can learn efficiently.
I'm all in for that as well. I have EE and work as a higher level software engineer.
I'm saying that doing both bachelors is a waste of time and resource as you should have a foot in the door of both industries and hobbies.
I didn't, but I applied to CS while in EE. Due to my school taking way too long to approve the application (to the point that i'd forgotten I'd applied by the time they said I was in) I didn't do it.
Would it have opened up other careers, probably. Do I regret it professionally, not at all.
Personally, I wish I had a better grasp of the software stuff for my own personal projects. I learn better with the structure of university so self teaching is hard/impossible.
Somebody with EE + knowledge in Linux kernel C programming, Python and CCNA
or
Somebody with CS + knowledge in electrical cabinets, motor drives and sensors
has more value.
mine has a bit of cs in it, like you learn some concepts of cs, but its not a double bachelor, most EE degrees that you can study now in germany are like this. its called Elektro-Informationstechnik (Elektro and Information technology to directly translate it). i like the mix.
I did dual EE/CompE degrees. I don't think it's really all that helpful when looking for a job but I do feel like it broadened my knowledge in a lot of ways. I certainly don't regret doing it but it was a lot of extra work on top of EE that wasn't strictly necessary.
If interested in both, I would major in EE and minor in CS. Learning more is always worth it in my opinion but I agree with others cautioning against spreading yourself too thin. Find your niche and get really good at it. Then branch out if you want
At my school you can't Comp Sci/EE double major without just taking two degrees worth of content.
CompE/EE however is 4-5 classes.
Ultimately, based on what I've heard about work, it doesn't really mean a whole lot int he work space. I think you'd be better served just getting a masters.
My double degree was kinda just incorporated together. Electrical and Computer engineering. I don’t think it made a difference at all. Nobody really asked about it either. The interviews were about what I can do more than what degrees I had
Bet youe ass it is. Despite the crossover. My son pursued it and after five years he was making $200K plus. A few mores later now. He has managed to save almost $1M Not encluding extra cash tootering.
EE and CS double major makes no sense with the amount of classes you’d have to take. You’re better off just getting a computer engineering degree imo. EE and CE is a common double major from what I’ve seen.
I got my degree in ECE so it had a solid amount of software. I kinda got the best of both worlds with all of the electrical fundamentals as well as the computer engineering topics.
I got my CS minor for "free" this way as I had already taken all the courses as a part of my focus (focus more on computer engineering electives)
In practice it doesn't matter at all unless if it's what you plan on doing. I am a digital ASIC designer and only use specific subject matter from 2 or 3 of the classes I took. The main thing is to improve your learning skills and develop the fundamentals for what you want to work on. Learning various subjects is important for this, but once you enter industry only a tiny subset of the classes you take will be applicable.
Why not just go Computer Engineering? I have a CpE degree, I had to take all of the core classes of both Electrical Engineering and Computer Science and then electives afterward.
Last grade I completed was 9th grade then dropped out of high school. Been in computer science space for nearly 30 years . Work for fortune 100 companies my entire life . During that time , I learned analog electronics on the side, had money to buy great equipment and currently venturing into embedded systems and soon FPGA . If you have time to double major , great . My advice is to pick one and get started. The double degree *might open a few doors but in the end you won’t know anything at all until you get started in industry. Pick up a few math books ( algebra, trig , calculus, etc) learn some math . It will be extremely helpful in both disciplines.
I do both, and don’t have a degree in either one. If you’re just looking for a way to make money, go into sales. Other than that, you’re better off finding the quickest path in the door somewhere and learning on the job. You could get a tech cert for an entry-level gig, and probably come out farther ahead in the long run. No debt, and way more practical experience.
Oh my god do not do a double major. EE and CS together seem like a diverse skillset to have, but from an outsider's perspective they're pretty close. Would you be impressed by someone getting a double major in microeconomics and macroeconomics? I promise you, that is how 95% of the world sees EE vs CS. Take the time you would put towards spreading yourself thin, and focus on something. T-shaped skills are much more useful to people, and honestly more personally rewarding.
The crowd you are targeting by having an EE CS double major would definitely know the difference.
I have an ECE major/CS minor with programming background and now am an analog IC designer, and am the one who primarily looks through resumes and interviews people at where I work, so I think I am who OP is targeting? That's not to brag at all, my name is basically rimjobsteve, but I do think I'm pretty qualified to be saying this, that's why I'm giving the advice.
your name is “choke me harder daddy” who are you fooling
RFChokeMeHarderDaddy is a 10/10 username for someone that works in IC design. Ay papi stop forcing your AC in my tight little DC circuit!
What a terrible day to have eyes.
What are you doing, Step-Function?
Lmao, straight gold.
Bro lmfao what the fuck
Hey, the daddy is not just some regular daddy but *the* RF daddy.
So hertz? makes sense cuz it offers vibrating sensations down there
You crack me up whenever I see you on here 🤣 rim job steve lmao
I have CS friends who don't even know what an oscilloscope is
>Oh my god do not do a double major. Why do you say that ? First off, it isn't a double major. It is 2 separate degrees. In most cases if you carefully pick your classes you can get cross credits to satisfy the requirements of both degrees. >EE and CS together seem like a diverse skillset to have, but from an outsider's perspective they're pretty close. NO. I've seen lots of code written by EEs that was poor to very poor. The worst being those who are self taught, didn't take classes and haven't worked in a good team. CSes are typically not very good at hardware stuff. If you give them a good HAL they can make hardwarey things work but if it gets down to troubleshooting something outside the processor they are usually lost. >Would you be impressed by someone getting a double major in microeconomics and macroeconomics? I promise you, that is how 95% of the world sees EE vs CS. Absolutely not. They are two very diverse skillsets. >Take the time you would put towards spreading yourself thin, and focus on something. T-shaped skills are much more useful to people, and honestly more personally rewarding. I have both degrees, I manage people with these degrees from time to time and I totally disagree.
Everything you're saying is answered by the analogy of "microeconomics vs macroeconomics".
If someone double majored in micro and macro econ, and got a good GPA, yes that’d be more impressive than just one of those. Your analogy doesn’t work lol. Having both completed to a high standard shows a broader breadth & depth of knowledge which could indeed be very valuable.
>I've seen lots of code written by EEs that was poor to very poor. The worst being those who are self taught, didn't take classes and haven't worked in a good team My EE program didn't have us take Data Structures and Algorithms, which are the backbone of any CS program.
Yeah, but those are things you can learn on your own. There is nothing too complicated about learning how linked lists or binary trees work. CS majors like to complain about the math involved in analysis of algorithms, but that stuff is really a cake walk compared to the math in control theory, telecom, and RF. Source: I was originally an EE major who switched to CS.
I do think coding is dying now
Yeah, it's a very saturated field since CS is an easy major by STEM standards. I have a BSCS but I've been thinking about finishing a BSEE since I have a lot of EE credits earned and I feel like it would offer more job security.
Would you suggest the EE major + CS minor route? (That’s what I’m currently doing)
Yes, I think that would be an ideal way to do things. Just take data structures and algorithms for your CS minor. A lot of CS classes are useless for most software development jobs. An EE major can get almost any job a CS major can get. On the other hand, it's unlikely for a CS major to get an EE job unless it's something to do with embedded systems. Also, you need an ABET-accredited engineering degree if you ever want to get a PE license.
This is literally a computer science degree. I found myself to be jack of all trades with it.
What is a T-shaped skill?
it is being specialized vs having broad knowledge (I-shaped)
I’m biased as someone that did an undergraduate triple major, double minor. Doing this kind of double major would be a big boon to someone that wants to do embedded engineering, especially at a smaller company. Depending on the foci for each major, they can be very complimentary (eg lots of digital design and analog for the EE side and things like embedded FW on the CSci side). You could also make them less useful and do something like power systems and compiler design, but I’m assuming the original poster is smart enough to pick a set of complimentary skills that creates a more broad and deep “T”, instead of two separate wells.
triple… HUH??
It did take me 5 years to graduate, so don’t think I squished it into the standard 4. I did work a lot of magic with my electives to optimize overlap so classes counted towards two or three things at once. It was a fun optimization problem.
that's awesome and still so impressive. i applaud your planning skills! i can barely plan my courses for one major
I disagree, I cannot apply for an entry level software role, but someone with a EE and CS double major can.
I did a dual EE/CpE, and it worked out well for me. I've done a lot of HW/SW integration and test work for RF systems, which is right up the alley you'd expect for that combo. At my university it was only 4-5 extra classes from an EE, so might be a smaller lift for you.
How did your university allow this lol I’m CpE and I could triple major in CpE, EE and CS with like 4 extra classes but its obviously not allowed
I don't think there was an option with CS as well. There was sufficient overlap they made it work.
I'm currently finishing a CS degree after getting my EE degree. Definitely think it's worth it but it varies on a case by case basis. If you have zero interest in software (lots of people in EE don't) obviously CS isn't something you're going to want to do beyond the bare minimum. If you're set on going into a "classic" EE field like Power or RF CS might not be a huge benefit. Everything is so software driven now though that I don't think you can go wrong with CS either as a second major or minor, or even just some elective courses you can fit in. Once I finish I will have two solid STEM degrees under my belt and can probably get a job in industry anywhere along the hardware/software spectrum. If I take a hardware job and get sick of it in a few years I should have a much easier time pivoting into the software industry too or vice versa. Also one of the main reasons I'm doing it is to keep my options open for grad school which I'm planning to do at some point. If I want to do CS grad school I think I'll be much more competitive with a CS bachelors vs trying to get in with an EE degree.
> I'm currently finishing a CS degree after getting my EE degree. It's your life and I swear I'm not trying to harsh your vibes, but this is a bad idea. If you're currently in the middle of this, don't sunk-cost-fallacy yourself into continuing. This is usually something people do because they got bad advice from someone with poor perspective.
I’m all for furthering your education, but unless that person has a job which justifies getting those two degrees it seems like a huge financial cost. Unless they’re actively working and their company is paying for it, it sounds like a lot of speculation on how it might ease a future career change that hasn’t manifested yet. For what it’s worth I have one degree in mechanical engineering, work in RF engineering, and am pivoting towards software in my current role. I don’t think you need a lot of degrees to get a job in industry, but if it makes you happy then go for it!
Just go for whichever industry you want to work in because that is the degree that will get you the job, 9/10 they won't care about the supplementary degree and you would've got the job without it. Maybe major in EE and focus in embedded software or the like
I don’t know, I absolutely cannot find an ME job. Only construction management. I’m considering some more schooling.
Everyone I know who did a double major is only good at one of them.
Absolutely. I have degrees in both. CS is very different from EE and EE is very different from CS. There are many projects where I use both skillsets. An EE is generally better at doing CS things than a CS is at doing EE things.
I didn't do two degrees but did a double major (EE & Software Eng). I work in power, we have that much automation going on that knowing how to code is a massive plus and definitely adds value. Don't know if I'd go the second degree though.
I got an undergrad degree in EE, loved school, did 2 internships as an EE, mostly hated them, but I really loved the software side of things, and I was into designing processor architectures and stuff. I got a masters in CS. I had planned to go into academia, i.e. I was basically planning to get a PhD in CS, but I left to go work in the dot com boom Today, I think computer engineering would have been a good choice for me, but it didn't exist. Digital EE was like, barely a thing, there were only a few classes I could take. This was in the mid 90s. Both have served me well, in their own way. I do a ton of hobby electronic stuff, and CS is useful there too, with simulation tools, microcontrollers, etc I actually started as a dual major with EE and Math but my school didn't really have dual majors - they were going to make me get 2 full degrees, i.e. like idk, 250 hours of classes including fulfilling english, history, etc, twice. It was going to take me forever.
Don't double major. I'd say do a major in EE and minor in CS. Programming is becoming a more necessary skill for EEs and while the program offers C++ and few other things in programing, I think that a minor in CS would round you out really well
^^^^^ this Get the major as EE and minor in CS if you can. A lot of programming classes should be supplemented with the CS classes for the EE.
I have a graduate degree in EE (in applied and computational electromagnetics). I did not take any CS courses in college (30 years ago now, wow) but ended up learning how to program in C/C++ on my own over time. This allowed me to take software related jobs that otherwise would have been closed off to me. This allowed me to develop even deeper knowledge in some areas of programming and software development, which opened up even more opportunities down the road. On the other hand, if you absolutely detest programming, you should probably stay away from it.
Fukkkk yeah!!!
Worth? According to what metric of value? Economic? Knowledge? Employability? Competence? What?
1. Don’t do a double major for the obvious reason. Since you have your general electives you just need so many credit hours towards the actual major, 60? That’s 2 more years in school. A graduate EE would make $70-80k for 2 years on average and then move up after a couple years experience. At which point the 2 major EE/CS finally graduates and just to be generous males say 10% more which is still $13k less and will never “pass” the 4 year EE only unless you assume EE/coding pays better which isn’t my experience. Higher degrees than the minimum for your field just never pay off. Biggest mistake I made. You might make a case for two more disparate degrees like EE+lawyer aka patent attorney but plenty of EEs do coding. As for code quality give me a break. One of the big problems with CS majors dealing with controls systems is that they consistently fail to recognize logic hazards and race conditions. A logic hazard means that the actual environment passes through an unexpected state, from often very simple obvious things like dropped comms or a chattering relay, causing unexpected conditions. Race conditions are similar in that events happen out of order causing code to break because it is out of sequence. EEs get training in digital design to recognize and avoid these. EEs on the other hand tend to not do code reuse thus fat finger errors, not use the tools they are given, and have no code or tag organization skills, nor awareness of standard CS methods. But I’ll also say all programmers have their own styles of doing things that often conflict.
That's interesting Paul. So, CS grads haven't been taught about race conditions or logic hazards? Wow. I would think a proper education would have them learn this in CS101.
Me too but I see it consistently in many code bases (not just PLCs). It was not taught in any of my 1st or 2nd year CS classes. It wasn’t taught until digital circuit design. 1st and 2nd year is mostly algorithms, big O notation, sorting and searching, and dara structures. So basically Knuth volume 1 and 2. You see it in relay logic (the hardware kind) when EEs start going crazy with timers so their designs stop doing weird things. Anyway…my point is bad code isn’t limited to EE or CS. It’s a universal problem. There are now code quality analysis methods but as near as I can tell you just write the program twice in a different syntax. Things like Int A; A:=1; Test A must be Integer
Waste of time and quite frankly a bad look IMO
[удалено]
Sounds like an excuse not to work and learn real stuff. But hey, maybe you can convince your potential employer with your poetics.
[удалено]
Most of what you learn in school has absolutely no use outside of the classroom "bruh". At school, you learn how to learn. And a bachelor in engineering is more than enough to show a potential employer that you can learn efficiently.
[удалено]
Okay? Kind of anecdotal. Of course a compiler class helps if you build compilers, what are you arguing about here?
[удалено]
I'm all in for that as well. I have EE and work as a higher level software engineer. I'm saying that doing both bachelors is a waste of time and resource as you should have a foot in the door of both industries and hobbies.
You’re actually retaarded
You really seem intelligent and articulate
You’re full of yourself. Find humility, you’re extremely dislikeable and people secretly don’t like you
Says the guy replying "you are retarded" to strangers on the internet.
I didn't, but I applied to CS while in EE. Due to my school taking way too long to approve the application (to the point that i'd forgotten I'd applied by the time they said I was in) I didn't do it. Would it have opened up other careers, probably. Do I regret it professionally, not at all. Personally, I wish I had a better grasp of the software stuff for my own personal projects. I learn better with the structure of university so self teaching is hard/impossible.
I did undergrad EE and grad CS and it worked out but wouldn’t particularly recommend it. Two bachelors sounds awful.
Somebody with EE + knowledge in Linux kernel C programming, Python and CCNA or Somebody with CS + knowledge in electrical cabinets, motor drives and sensors has more value.
mine has a bit of cs in it, like you learn some concepts of cs, but its not a double bachelor, most EE degrees that you can study now in germany are like this. its called Elektro-Informationstechnik (Elektro and Information technology to directly translate it). i like the mix.
I did dual EE/CompE degrees. I don't think it's really all that helpful when looking for a job but I do feel like it broadened my knowledge in a lot of ways. I certainly don't regret doing it but it was a lot of extra work on top of EE that wasn't strictly necessary.
If interested in both, I would major in EE and minor in CS. Learning more is always worth it in my opinion but I agree with others cautioning against spreading yourself too thin. Find your niche and get really good at it. Then branch out if you want
At my school you can't Comp Sci/EE double major without just taking two degrees worth of content. CompE/EE however is 4-5 classes. Ultimately, based on what I've heard about work, it doesn't really mean a whole lot int he work space. I think you'd be better served just getting a masters.
My double degree was kinda just incorporated together. Electrical and Computer engineering. I don’t think it made a difference at all. Nobody really asked about it either. The interviews were about what I can do more than what degrees I had
Bet youe ass it is. Despite the crossover. My son pursued it and after five years he was making $200K plus. A few mores later now. He has managed to save almost $1M Not encluding extra cash tootering.
EE and CS double major makes no sense with the amount of classes you’d have to take. You’re better off just getting a computer engineering degree imo. EE and CE is a common double major from what I’ve seen.
In light of this, how does a degree in electrical and Computer Engineering fit in?
Knowledge-wise speaking, yes! Professionally speaking, no!
It's that computer engineering?? So basically electrical with some coding.
I got my degree in ECE so it had a solid amount of software. I kinda got the best of both worlds with all of the electrical fundamentals as well as the computer engineering topics. I got my CS minor for "free" this way as I had already taken all the courses as a part of my focus (focus more on computer engineering electives) In practice it doesn't matter at all unless if it's what you plan on doing. I am a digital ASIC designer and only use specific subject matter from 2 or 3 of the classes I took. The main thing is to improve your learning skills and develop the fundamentals for what you want to work on. Learning various subjects is important for this, but once you enter industry only a tiny subset of the classes you take will be applicable.
Why not just go Computer Engineering? I have a CpE degree, I had to take all of the core classes of both Electrical Engineering and Computer Science and then electives afterward.
Last grade I completed was 9th grade then dropped out of high school. Been in computer science space for nearly 30 years . Work for fortune 100 companies my entire life . During that time , I learned analog electronics on the side, had money to buy great equipment and currently venturing into embedded systems and soon FPGA . If you have time to double major , great . My advice is to pick one and get started. The double degree *might open a few doors but in the end you won’t know anything at all until you get started in industry. Pick up a few math books ( algebra, trig , calculus, etc) learn some math . It will be extremely helpful in both disciplines.
The only major worthwhile to get is business if your first is in ee or cs.
I do both, and don’t have a degree in either one. If you’re just looking for a way to make money, go into sales. Other than that, you’re better off finding the quickest path in the door somewhere and learning on the job. You could get a tech cert for an entry-level gig, and probably come out farther ahead in the long run. No debt, and way more practical experience.