r/ComputerEngineering • • Dec 29 '23

Why is computer engineering getting bashed?

I’ve seen some computer science graduates belittling computer engineering in terms of pay, studies and work. Im currently in my last school year and I’m interested in computer engineering but the bashing pops up. Please help to convince me out with info on why computer engineering is good

251 Upvotes

108 comments sorted by

121

u/bobking01theIII Dec 30 '23

A CE degree can get any job a CS degree can. The other way around isn't true just because of hardware knowledge

15

u/fiery_prometheus Dec 30 '23

Partly not true, as far as I know, they usually don't have what is required to do things like computational theory, programming language development, crypto, distributed systems modelling, and the whole area of more advanced algorithms, but correct me if I'm wrong.

But if you are talking about most normal jobs out there, then yes, not much of a difference.

Edit: except when hardware knowledge is required of course, but the more hardcore stuff are for EE anyway.

10

u/om-nom-nom-normies Dec 30 '23

Most CS people I know forgot all of that knowledge anyways

9

u/[deleted] Dec 30 '23

Just depends how you structure your classes. You’re right but this is why some can do it and some can’t.

6

u/loaengineer0 Dec 30 '23

Yes and no. The high-level goal of any piece of silicon is to support all the things a software developer might want to do with it in a sensible/efficient way. So you need at least an intuitive understanding of a wide range of software topics if you are doing any architecture/uArch work.

1

u/fiery_prometheus Dec 30 '23 edited Dec 30 '23

Makes sense, but at this level, a lot of time and effort is involved to get to that point, and no education will just give you that level of experience I think?

I've worked with software and computer science mostly, but have done some electronics as well (introductory courses on analog and digital circuit design, and micro controllers in straight assembly was the most advanced I did, so not much experience in that field), and I have rarely seen or heard of people working with both in my software career unless they are pursuing something highly specialized.

When I've implemented some examples of a uarch from textbooks as a computer scientist, it was almost like treating the requirements and rules more like when you implement a programming language (mathematical constructs and logic) than when you are actually thinking about how the electronics side of it works. So I would be curious, at what level of abstraction do you work when doing uarch work in the real world, and how much depth of the different domains are needed?

Because at the electronics level, at least at some point, you cross into EE and physics territory, but those buildings blocks are probably not the right ones for the abstraction level where you are doing uarch work, right? Would be greatly interested in knowing how this type of development actually works.

2

u/loaengineer0 Dec 31 '23

When I write code, it is RTL (Register Transfer Logic) in SystemVerilog. So I’m defining state elements and the transformation of state from one clock to the next. Someone else uses a suite of tools to convert that code into a list of logic gates and wires, and then figures out how to lay that out on the chip.

Architects talk to customers and come up with a list of features. They define the skeleton of a software/hardware interface, collaborating with the software team. The architects usually get really specific, but the definition changes substantially later in the process. From there, micro architects break up the feature set into clusters, then define the major state elements and general control+data flow. UArch specs are reviewed to make sure that the interfaces between clusters is clear and consistent, but these documents are not shared outside the company. That uArch definition is implemented in an RTL language. There is a continuous process of negotiating the Arch, uArch, and RTL to keep everything consistent. Ultimately, the Arch spec is used by the software team to write firmware and drivers. The final version Arch spec may also be shared with customers.

I work in the uArch/RTL layers. The software knowledge comes in a few places:

  • “big O” costs of solutions that need to scale on different dimensions. Amortized costs of infrequent operations. All that basic stuff is generally applicable. Also scheduling and queueing stuff applies a lot.

  • Arrays and queues are sufficient for the vast majority of hardware structures, but occasionally you get a case where a linked list or some kind of tree structure is warranted.

  • Recommending Arch changes that enable better performance. I’m usually familiar with the APIs/workloads we are targeting, so I can intuit what the driver will be doing. Sometimes there is an opportunity to reduce the driver overhead by making a cheap addition to a hardware capability. ML and networking classes have been very applicable for me.

  • Recommending Arch changes that enable a cheaper implementation without impacting performance. Sometimes there is a parameter the Architects threw in just because they thought it was a trivial addition. Other times there is a slight semantic change that is inconsequential to the driver but is huge for the hardware. For a trivial example, a multiplication or division circuit (big/slow) can be replaced with a bit shifter (trivial) if the second operand is guaranteed to be a power of 2.

  • Debugging tool issues. The SystemVerilog simulators and other tools we use are all super shitty compared to typical software compilers. They all implement different subsets of the SystemVerilog spec, but they don’t always throw errors when they encounter some unsupported syntax, so you just have to figure it out. I still use skills from compilers class for this.

  • Formal verification is very useful, but it is applying a sat solver to non-trivial problems. You can get a lot more out of it if you have a general intuition about sat solver algorithms.

Random math stuff also shows up occasionally. Like a “rare” performance degradation that actually happens all the time because it’s a birthday problem and no one recognized it until we got initial performance testing.

1

u/fiery_prometheus Dec 31 '23

Thanks a lot for the detailed writeup, it was very interesting to know about!

I've looked up how to program in RTL in SystemVerilog, and it makes a lot of sense when you say that computer science is so applicable. I got the impression that it is akin to another programming language, but with a different mindset for the program flow and parallelization. Almost to the point where knowing about computer science seems more useful to me since the high level concepts about computation will always be valid, but I am biased I'll admit.

So having an intuition about how digital circuits work at a lower level seems helpful, but not wholly necessary? It seems like the abstraction stops at knowing boolean gates, clocks, flip-flops etc, and everything under that is handed of to other engineers?

As a thought experiment to know where the abstraction layer is, would it for example be useful to have an intuition about hysteresis when switching states quickly when you write RTL, or is it a valid assumption to think about the circuits as discrete steps which the engineers at the lower levels have guaranteed to always hold? Such that you can never trigger weird/rare edge cases where this might become an issue?

IE, every operation is driven by a clock edge, and for all components at this abstraction level (RTL) they are always atomic and do not 'leak' concepts like analog circuit concepts, can trigger leakage or cause interference with physically neighboring components etc. if they are abused?

1

u/loaengineer0 Dec 31 '23

> So having an intuition about how digital circuits work at a lower level seems helpful, but not wholly necessary?

It is extremely helpful. As an example, a 32-bit shifter can be implemented as a 2D array of multiplexers. The first row selects either the original value or the value shifted by 16. The second row selects either the first row output or that value shifted by 8. Then 4, 2, 1. If you code this explicitly, the synthesis tool might choose to implement all muxes with a transmission-gate-mux cell (4 transistors). The problem is that the drive strength of a transmission gate output is always less than the drive strength of the input. So by the time the signal gets to the output, it will be too weak. This can be solved by putting a row of inverters after the 2nd and 4th row of muxes to re-up the drive strength. The inverters cancel out, so the circuit with inverters is logically equivalent. This is a very old example (modern synthesis tools resolve this automatically), but there are similar cases I've hit more recently.

There are also lots of optimizations that synthesis tools can do if you configure them properly. It is best if you have a plan in advance rather than letting the downstream engineer try things randomly. For example, I might know that the path before a flop may be tight, but I can keep the path after the flop short so that clock-skew can be added in synthesis (basically, put a few extra buffers on the clock so that it hits that flop late, thus expanding the time available for a signal to get to the flop and decreasing the time between that and the next flop). Clock skew can only be inserted if there is sufficient room on the output path, so you need to plan for it early.

> would it for example be useful to have an intuition about hysteresis when switching states quickly when you write RTL, or is it a valid assumption to think about the circuits as discrete steps

For pure digital logic, you can mostly think in terms of discrete steps. One of the last stages of the physical design is to verify that the schematic doesn't violate those assumptions. The physical designers do a lot of work to prevent and resolve those issues, but that doesn't impact the RTL.

There are some situations like clock-domain-crossings and IO SERDES which require significant RTL+PD co-design. Those are treated more like analog circuits. That kind of function is done in a box and the boundary of that box doesn't violate the digital assumptions.

2

u/fiery_prometheus Jan 01 '24

I see, the example of the synthesis tool choosing a solution which might not be adequate seems to be a similar problem in which you know what some code has to do, but the compiler doesn't know and thus outputs for the most common general case. At the same time, it seems even more important to have this intuition for digital circuits and the synthesis tool, as it helps preventing being caught of guard by cases where the output could be plainly error prone and not just slow (as in established compilers output slow code more often than wrong code, I hope).

So it makes a lot of sense to catch these bugs, the down stream engineers might spend a significant amount of time even trying to identify where the errors come from, but it probably depends on the size of the 'program/function/unit' being worked on and the unit testing put in place.

Thanks for the answers! I was always curious about the processes one might go through in this domain.

Might take a look at SystemVerilog to program some fpga's in the future, but that will likely just be to settle my curiosity and dabble a bit in the domain to see how it is, but I find the intersection of knowing about the hardware and at the same time, thinking about the high level functionality to be very satisfying.

0

u/[deleted] Dec 30 '23

[deleted]

11

u/Traze- Dec 30 '23 edited Dec 30 '23

“Doesn’t exist as a real academic field”

I have seen thousands of job applications that specifically list “computer engineering, computer science or a relative degree” under their education requirements. You’re kidding yourself.

I also would not have landed my internship if it wasn’t for my degree. It’s a software engineering role that deals with lower level programming and my manager straight up said “one of the main reasons we hired you is because we were looking for a CE”

Keep coping while you complain why you can’t land a job on CS subreddits. The market is being flooded with CS graduates and 90 percent of them don’t know their way around embedded systems so all they can get are web dev jobs which have thousands of applicants per job opening.

I’m not trying to bash on CS but that’s the reality today. Even on subreddits that revolve around normal job hunting as a whole a great majority of the post I have seen have been from CS majors. Almost all my CE friends have found a job/internship and it’s simply because we learn different skills that are becoming exceedingly needed as more companies make tech oriented products that require hardware knowledge.

This is why for instance, Apple has separate interview questions for embedded systems applicants. The skills are completely different.

0

u/[deleted] Dec 30 '23

[deleted]

5

u/Durpn_Hard Computer Engineering Dec 30 '23 edited Dec 30 '23

Well, for what it's worth, I went to non-T50 schools, have a BS and MS in Computer Engineering and have a job that pays a solid amount better than your hypothetical number.

Maybe focus less on whatever hate boner you have against Computer Engineering and more on whether it actually matters or if you're just gatekeeping (you for sure are).

Edit: oh you're a new grad getting rejected a lot. Nevermind, makes sense. Also maybe nailed down why you don't land.

3

u/Traze- Dec 30 '23 edited Dec 30 '23

One of the undergraduate TAs for an embedded systems class I took last semester landed a 250k job at Apple in embedded systems. I go to a state school. Granted, a very well respected ECE university, but still a state school.

8

u/yaeh3 Dec 30 '23

Ok lol

116

u/yaeh3 Dec 29 '23

They have no clue what they are talking about lol. When it comes to software development jobs, CE and CS grads are almost always treated the same. No competent employer favors CS majors above SE and CE. CS grads however cannot land the hardware or electrical engineering jobs that CEs can get. CE is most of the time a better degree in literally every way for getting a job in the tech industry. All depends on the curriculum and work experience at the end of the day.

9

u/EncroachingTsunami Jan 01 '24

CE is better because high level programming (CS) is easy to do self taught, whereas engineering is a discipline with standards. There's plenty of guides and open resources for learning high level programming, but it'll be hard to get someone to properly teach you the levels of physics and hardware engineering you get from school.

But no, a CE degree doesn't qualify you for high level programming on it's own. But funnily enough, there's standardized testing for high level programming proficiency.

So CS has no standardized learning, can be self taught, but has standardized testing. Cs jobs have lower hard requirements since anyone can take the automated assessment and prove proficiency. CE has standardized learning, hard to self teach, and has no standardized testing. So there's a hard requirement for having a CE degree

7

u/LegitGamesTM Dec 30 '23

This is kind of true, although CS majors do get an advantage over software engineer jobs (high level).

10

u/yaeh3 Dec 30 '23

What I meant is that it isn't black and white. If these three majors applied for the same software job, the one with most experience and knowledge is going to get hired.

2

u/LegitGamesTM Dec 30 '23

Yeah that’s true, but let’s just say your goal is to work on high level software, you’re going to obviously want the CS degree. It’s super competitive at the top of that field and all else equal the CS degree is the move.

Personally, I think the CE degree is better bc it does allow you to go into both and the value of the education is better, but chances are it will be an uphill battle for you to beat out the CS guys for the top jobs out of college (high level programming).

0

u/[deleted] Dec 30 '23

[deleted]

3

u/yaeh3 Dec 30 '23

That is the opposite for us here in Germany. College status does not matter at all. A CE that went to a shitty applied university that does absolutely no math and laughably easy coursework and exams is equal to CEs that go through Calculus 1,2,3, excruciating exams and all the stupidly hard EE physics classes. Absolutely crazy to me. It is because employers do not care if you know how to do fourier transformations at the end of the day.

3

u/Karyo_Ten Dec 30 '23

Me hiring people for doing GPU-accelerated cryptographic Fourier Transform (aldo called NTT, Number Theoretic Transform) 🤨

1

u/yaeh3 Dec 30 '23

You might be the only person in the world hiring for this job. Just kidding. You get my point though. A lot of the coursework we do in a tough curriculum won't be necessary for employment. Most of CEs go into software anyway.

4

u/Karyo_Ten Dec 30 '23

You would be surprised, it's widely used for:

  • all Post-Quantum Cryptography today requires lattices which requires Fast Fourier Transform

  • Error-Correcting Codes, used in ECC RAM or file system like ZFS or BTRFS requires fast fourier transform

  • All Fully Homomorphic Encryption, getting big for private deep learning, require very fast GPU FFT, even considering FPGA.

  • Zero Knowledge proofs as well require very fast GPU FFT or FPGA.

  • Shamir Secret Sharing to securely create shared secrets / threshold signatures where M people out of N can sign a message on behalf of the group.

The high performance cryptography field has grown tremendously and there are many companies with millions to tens of millions in VC funding that are eother bottlenecked by it or trying to solve it.

19

u/rowdy_1c Dec 30 '23

Big influx of CS majors who are in it for the money, compared to CompEs who are usually actually passionate about what they do and don’t mind the pay cut in comparison to SWE (keep in mind that CompEs are completely qualified to go into SWE and the reason many don’t is because they don’t want to)

3

u/treeman0469 Jan 02 '24

am a cs major. can absolutely attest that a good portion of cs students have 0 interest in the subject itself and just want money/prestige/familial praise

4

u/rowdy_1c Jan 02 '24

I’ve noticed that most of my CS classes feel a little lifeless, whereas most ECE classes have most of the students genuinely interested to learn

1

u/ZenmasterSimba Jun 08 '24

Glad to know I’m not the only one who felt like this. I actually befriended a lot of EE and CE guys because we would often collab driven by passion while in my CS courses it felt like it was collaboration on just getting the assignment over with. It didn’t help that more CS students were very antisocial and weren’t a huge fan of group work(coming from my personal experience I know not everyone is like this).

1

u/treeman0469 Jan 07 '24

i feel the same way with my math classes (am also a math major). i mean, a lot of pure mathematics has little to no immediate application in the "real world", so the people in those classes are definitely there out of love rather than out of superficial desire

12

u/TheMineA7 Dec 30 '23

Im sorry thats funny. Dont listen to a bunch of nerds who cant make time to shower when they have 4 classes a semester vs engineering students having 6 to 8. Eng just lets us get to the low level with C or RTL with verilog/vhdl. Plus electronics so u actually know how transistors work. We all literally get the same jobs if not more due to hardware jobs being an option

1

u/system-32- Dec 30 '23

That was well said 👏👏

5

u/Classic_Analysis8821 Dec 30 '23

Many SWEs cant fathom people who are pursuing things that interest them instead of what makes the most money

3

u/MasqueradeOfSilence Computer Science Dec 30 '23

I did CS and I think computer engineering is much cooler, though I still loved my major. I didn't do CpE because I was not well-informed about what it was, and I liked some of the CS emphases my school offered. Going back I likely would've done CpE, or double-majored for the extra animation/game dev classes in the CS major.

But in CpE you get to work with both hardware and software, and you actually understand how a computer works from the ground up. With CS you're lucky if you get 1 microcontroller/assembly class, and everyone complains about how hard it is. Also, in CS there are too many tech bros now. It's not the hardcore nerd major it used to be.

3

u/rfdickerson Dec 30 '23

When I was comparing and considering CpE vs CS I looked at the curricula in each. I chose CpE since it seemed more rigorous to me.

At my school, CpE required the same core courses as CS (DSA, Comp Org, OS, networking, discrete math) but with much more engineering courses like (signals and systems, circuits 1+ 2, digital logic, microP, Digital design). While both required Calc 1-3 and LinAlg and stats, CPE went deeper in math with diff eq, numerical analysis- also a good science foundation with physics 1+2 and chem 1+2.

I got to choose electives in either the CS, CpE, or EE departments. I mostly chose CS electives. Anyhow, that was 20 years ago and now a machine learning engineer.

3

u/Opeace Jan 04 '24

I recently had someone in the industry tell me this: with a Computer Engineering degree, you are equipped to be a Firmware Engineer which has some Electrical Engineering facets and some Computer Science facets. It's the place where physical components meet digital computing.

If you want to go the route of a Hardware Engineer, you're going to less equipped than an Electrical Engineer. And if you want to be a Software Engineer you're going to be less equipped than a Computer Scientist. But if you want to be a Firmware Engineer, you have all the skills necessary with your degree.

A lot of Computer Scientists don't think (or know) that innovation occurs in the hardware/firmware side of tech. They also don't have the patience for low-level programming or circuit design.

As Computer Engineers, we are better equipped to pivot to either Software Engineering or Hardware Engineering jobs, having to only cover an additional 20% or so of subjects that we did not get to do in those 2 branches. However, a Computer Scientist would have to self-study about 90%-95% of Electrical Engineering subjects to be a Hardware Engineer.

That's all to say Computer Engineering Degrees (coupled with hard work and ambition) are far more versatile than either Electrical Engineering or Computer Science degrees. Computer Science degrees typically branch off into virtual stuff. They don't really touch any hardware design stuff.

3

u/ViceKnightTA Oct 09 '24 edited Oct 09 '24

9 months late to the party but I searched for this topic, and having a B.E. and M.E. in Computer Engineering currently working in software since the last 12 years, I am qualified to answer this thoroughly and effectively (and hopefully for others looking for alternate perspectives to your question).  

There are actually two answers, and the second answer takes the intent of your question into consideration. 

Answer #1: (academics) 

The main difference is, "Computer Engineering", by default, allows you to traverse the engineering degree of an academic curriculum, while "Computer Science" does not. Most "technical institutes" may have degrees delineated between "B.E." (Bachelor of Engineering) and "B.S." (Bachelor of Science).  It also depends on how a college treats the "Computer" aspect of both these degrees. In my college for example, Computer Science students focused more on coding rather than paying attention to how the circuitry and assembly below the high level language integrated together. Computer Engineering students actually had to take circuit theory and were able to elect other engineering courses of their choice towards the credits they needed to complete their degree. Computer Engineering students were also given more opportunities for work/study/co-op programs because engineers were also upskilled on the business and stakeholder aspect of engineering which companies sought. 

However today, thanks to progress made in areas such as Cloud (IaaS, PaaS, SaaS, DevOps, etc.), Machine Learning, and AI, the original lines between Computer Engineering and Computer Science are somewhat blurred. Anyone with any degree can gain additional vocational certifications in these "bleeding-edge" disciplines. In fact a lot of technical universities/institutes nowadays are also being rated on how quickly they can integrate these new innovative subjects into their degree offerings.  

Answer #2 (career market value) 

At the end of the day, the value which your degree is worth in the job market, is less in the hands of yourself or your peers, and more up to the companies (HR) hiring department and what they are looking for. You can also bet that each company is also extremely biased with their own grasp of a B.S. degree vs a B.E. degree. These days they have very advanced tooling and software which cross-references and even filters out schools and backgrounds which may not meet the concentrations of study they are seeking for you to have gone through (remember my comment about the rating of a school, based on how quickly they can incorporate the new upcoming subject matter).  

Looking at it from that perspective, there is no "one-size-fits-all". There are plenty of the same companies that will interview (and hire) someone with a Computer Engineering background or a Computer Science background for the same position/salary, so long as they fit all of the criteria. Heck I even know a guy who did his major in political science, changed his mind half-way into his career, and now he works as a lead cloud architect who can probably run plenty of circles around you, me, or any of the kids who make fun of your degree lol.  

My advice to you and anyone else, is not to let the college or your major (OR anyone who bashes you) make you second-guess your current path. You're already in the midst of it, why panic and maybe even change it for the worst? Follow through and get your degree. But also do your own research on life after studying. By the way, rhe studying and learning doesn't stop after you walk out of college. Plenty of chances to pivot into whatever career you wish to have even without going back to school. You just have to have the energy and determination to do it. Good luck to you, and all the best. 

2

u/TheKiznaProject Dec 30 '23

As a former CE, I got an advantage over cs majors when selected for my internship; but they were also much better at modern day programming languages than me on the other hand; I had to play catch up with full stack development after learning mainly arm ,C, and assm/registers. Picking up python ,jscript, and html completely from scratch.

In my experience I took Ce and swapped to cs upon realizing it’s far less courseload heavy and i’ll probably just want a software development or test engineer gig anyhow. The fact of the matter is that electrical engineering is just really hard. I love silicon and low level stuff but at the end of the day ,Most ce careers require further education such as masters,doctorate, and that was something I wasn’t willing to do for monetary reasons.

2

u/[deleted] Dec 30 '23

CS students are jealous nerds lol

2

u/anasouardini Dec 30 '23

CS in itself is a really fun field for details-oriented folks, but these 2 last years and probably the next 2 or 3 will has been and will be the hardest time to get into it, it's so saturated.

From my little experience and from what I hear, not on the internet (especially from tech content creators), but from people in the real world, these are some reasons as to why learning CS RIGHT NOW to make a LIVING is not a good idea:

  1. companies post fake jobs to make people think that this field have so much demand.

  2. recruiters have been posting "fake jobs": when they are competing with each other over the same position at the same company all of them (2-3 recruiters) will post for the same job which also gives a sense of high demand.

  3. influencers, especially after realizing that the field is saturated, jumped to content creation as a backup plan, and since that's a source of income, they started pushing people into learning these professions just to grow their audience. They only care about revenue. Even in these days when it's the toughest times at which to get a tech job, they still won't tell you to look for a different field or something.

  4. financial crisis caused most of the companies to layoff some employees and not hire as much as they used to. And the folks that were being let go are more experienced than you are which makes the competition even tougher.

I'm not saying don't learn tech skills, but if you only have the time for one job/field, the wise decision is to postpone tech jobs for now, especially if you're a student, find a job somewhere else and keep making connections with people, those connections might help you get in when the demand is so low and the competition is really high.

1

u/ansb2011 Dec 30 '23

Because CE is way harder than CS yet often doesn't pay as well or have as flexible options.

1

u/[deleted] Dec 30 '23

Simply not true, CE can get any job CS can and then some

1

u/sirfitzwilliamdarcy Dec 30 '23

😂😂😂😂😂😂

-2

u/[deleted] Dec 30 '23

[removed] — view removed comment

5

u/[deleted] Dec 31 '23

I cried a little bit but good thing I have all this money from my coding job to wipe my tears with 🤣🤣 thanks for the laugh clown

1

u/loaengineer0 Dec 30 '23

The range of CS salaries is much wider than for CE. They look at the list of starting salaries and think they are all going to be in the top 5%. At the median, CEs are making a lot more.

0

u/sirfitzwilliamdarcy Dec 30 '23

That is a flat out lie. CS majors are the highest paid on average AND have the highest median salary. You can look at any reputed source for this.

1

u/loaengineer0 Dec 31 '23

From talking to friends, I think (excluding recent grads and senior staff)

  • experienced hire writing scripts at a defense contractor is making <150k

  • experienced hire writing infrastructure code at AWS is making >400k

  • experienced hire doing silicon design is making 200-350k

I think there are a lot more jobs in the first group than there are in the second. I’m curious which part of that we disagree on.

1

u/sirfitzwilliamdarcy Dec 31 '23

Unfortunately talking to friends is not a real source. There are pay reports that show the means AND median pay for these fields. And in the US, cs pays significantly more. Also that third salary range is ridiculous. That’s like saying I make anywhere from $0-$150k. That’s one hell of a range. Also cs is way too broad to be summarized with average hire “writing scripts” whatever that means and infra code. And don’t get me started on the top in cs. You could spend 20 years in CE and not make what some of these entry level SWEs make. The reverse is obviously not true. There is a hard cap on entry level pay in CE. And this compounds as you progress in your career.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

CS still pays way more than other fields. CS interns make more than most engineers make full time. And once they become senior software engineers the gap widens significantly.

0

u/[deleted] Dec 30 '23

[deleted]

0

u/sirfitzwilliamdarcy Dec 30 '23

Average pay is higher now. You are just plain wrong about that. You can look at glass door or levels or linkedins pay reports. Entry level roles have become harder because of layoffs caused by demand cooldown post covid. But that’s recovering. The pay is never gonna be the same as another field. I don’t think you have any idea how much cs majors make. I was making $60/hr as a freshman from a no name school in an internship. While that’s def on the higher end of pay, a lot of companies pay in that range, and most entry level jobs in HCOL areas are 6 figures.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

Completely not true. EE and CE curriculums do not sufficiently prep you for SE. How are you going to do a systems design and OS interview when you don’t know what they are. CS majors have been using data structures and algorithms throughout their years in college, saying they are equally competitive for SWE is delusional.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

Those higher level algorithms classes are where you learn about things like dynamic programming and greedy algorithms things you will need for the SWE interview process. Of course you can cover this on your own, but that’s like taking every cs course and not calling yourself a cs major.

→ More replies (0)

1

u/sirfitzwilliamdarcy Dec 30 '23

I’m gonna piss people off and tell you this. It’s because CE is very limited in scope. Let me explain what I mean. Only a few industries and a few companies are or would be interested in custom silicon or custom hardware or need CEs on active payroll for their functions whereas all industries require software engineers in some capacity. Yes CEs can apply for and get SE roles, but obviously CS majors are preferred as they have more relevant coursework and are better on average at programming. I don’t think it’s debatable whether CS has more career opportunities than CE and frankly it’s pretty obvious why.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

I mean there are more companies that need CS majors than CE majors. The average medium sized company would definitely need some cs majors to at least maintain internal software and their website. But does not really need a CE. This is not to to minimize the importance of CEs they are gonna be using hardware with significant contributions from CEs but don’t need a CE on active payroll.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

Web development does not require a cs degree. And most grads are software engineers not web devs. If anything AI will increase demand for software engineers to set up the infrastructure and develop the systems that use AI to change every industry. CS is not about knowing the syntax of a programming language, it’s about creating systems that solve problems with software and that is a skill that is going to be increasingly in demand

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

Not true. For the more competitive Software Engineering jobs other majors stand basically no chance. There is no way you are passing those interviews. Obviously there are people that self teach equivalent courses such as OS and distributed systems on their own. But they are basically cs majors at that point.

0

u/[deleted] Dec 30 '23

[deleted]

1

u/sirfitzwilliamdarcy Dec 30 '23

So you’re telling me a CE takes OS, distributed systems, and advanced algorithms?

0

u/[deleted] Dec 30 '23

[deleted]

→ More replies (0)

1

u/Jaygo41 Dec 30 '23

I got to a senior-level VLSI class around designing digital circuits at the transistor level during undergrad and in week 3 a computer engineer asked "What's a gate"

1

u/goodbye_everybody Dec 30 '23

If your goal is money it's a 100% moot argument. Neither CS nor CE makes the most money; Directors/Management make the most money. Period.

No pure engineering position is ever going to compete with VPs, Directors or CEOs. $250k/year is for the turbo nerds who can code anything they can imagine, but can't be bothered to put on a tie, speak without being belligerent or shower every day. If you make 7 figures, you're management, not staff.

For that, you're going to need 1. Any degree, CS or CE, 2. A few years of applicable staff engineering work just to prove your pedigree and then 3. All the things you shouldn't be cheating at in your degree program, namely time management, design, general social and personality compatibility, teamwork, patience, resilience, reading between the lines, etc.

If your goal is to make money and just to make money, get any degree, put in 3-6 years (or less, if you're lucky and an opportunity comes your way), jump into management (where you're doing little actual engineering, but still have the chops to understand when employees are blowing smoke up your ass) and laugh at the guys arguing about whether CE or CS is more impressive... from your $2.1M house, quarterly 14-day vacations and retirement at 52.

1

u/tmlildude Dec 31 '23

because zsh has better plugins

1

u/glaba3141 Dec 31 '23

My job would be a lot harder if I did CS instead of CE, and it is in the industry that pays programmers the most on average, so... Haters gonna hate?

1

u/PaulKMandal Computer Engineering Dec 31 '23

Computer Engineering is a great pick, don't fret your choice. I did my B.S. in CpE, B.A. in Math, then got a job in AI/ML and am currently doing an MS in CS. Worst case scenario, you can always switch over pretty easily. One of my junior engineers has his B.S. and M.S. in CpE. He still does AI/ML work.

There are some senior FPGA Engineer jobs that pay 200-400K. Embedded work is hard, and there aren't a lot of people who can program microcontrollers in assembly and C. Yes, CS jobs can pay a lot but there are also a lot of low quality software and AI/ML engineers that over-saturate the market who will be lucky to break 80K/year.

1

u/stlcdr Jan 01 '24

Computer engineering is encompassed in other engineering degrees.

1

u/BensonandEdgar Jan 02 '24

Pay = Less, I don't know why. IMO CE is way harder

I am a cs major btw

0

u/travelinzac Dec 30 '23

Y'all get paid crap, sorry, sincerely, a SDE.

1

u/[deleted] Dec 31 '23

The last 3 years of levels.fyi data seems to contradict you...

0

u/[deleted] Dec 29 '23

[deleted]

65

u/RangerZEDRO Dec 30 '23

Lmao, yeah. Its true, everyone wants to have a software job thats pays $250k and a work from home. Thats why they go CS, because its less(time money and effort) than getting a Engineering degree

25

u/SMTG_18 Dec 30 '23

I feel so fucking left out. I’m a CS major who’s been interested in the subject but all I see is job job job job I feel so done

10

u/Mrsporn1 Dec 30 '23

You can definitely go into research/PhD! Focus on grades for GRE and getting a research internship.

4

u/SMTG_18 Dec 30 '23

That is my plan yes :D

2

u/Stock-Till4612 Dec 31 '23

No need to focus on the GRE. PhD admission does not care about your GRE score.

1

u/mofukkinbreadcrumbz Jan 01 '24

Don’t worry, those people burn out and become tech sales, PMs, change fields, etc. the people that live it stick around and up in those crazy paying lead/staff/principal/fellow positions.

Source: am one of those people. I contribute to OSS for fun. Had a bit of a burnout spell myself for a few years, but that was poor management more than falling out of love with puzzles.

4

u/MasqueradeOfSilence Computer Science Dec 30 '23

Yeah same here, it's depressing to see people in it only for the money, and they seem to be the majority now

10

u/0ctobogs Dec 30 '23

Don't worry, many don't make it through the degree, and then lots aren't able to actually land a SWE job, and the ones that do don't stick around because they end up hating it. They also perform worse because they don't care as much. The people passionate about CS stick around and do well. At least, this is what I saw from my graduating class.

2

u/MasqueradeOfSilence Computer Science Dec 30 '23

A great point. If they're not passionate it's going to weed them out eventually. I appreciate this perspective a lot!

3

u/Perfect-Rabbit5554 Dec 31 '23

CS has one of the highest dropout rates.

I would wager a large part of it is too many of them just want the job and aren't interested in the field itself.

1

u/MasqueradeOfSilence Computer Science Dec 31 '23

That is true as well, a lot of them dropped like flies in discrete structures.

2

u/Elsas-Queen Dec 30 '23

I sincerely feel like an outcast for this reason. I would 100% be willing to accept a lower paying job for a better work-life balance. I lost peers/former classmates before we were 30 (one took his life at 18!), and I've had near death experiences. That ended my chase for money very quickly.

Would I turn down the chance to make $250K? No. But if I was miserable or it meant near total sacrifice of my personal life and relationships? Yes. Money can be replaced. Time, not so much.

1

u/MasqueradeOfSilence Computer Science Dec 30 '23

Work-life balance is important to me as well. Yes, I love coding, and I enjoy spending lots of time doing it. But I have other interests too, and my own coding side projects I'd rather be working on, where I have full creative and stylistic control. I see no honor in pulling crazy hours for a company that would axe me immediately if it benefited the business' profits.

Historically the corporate drone types were in other majors and fields, but they're in CS now too. Of course I want to make a good living, but I'm not pulling 55+ hour workweeks to do it. It's also frustrating to see people in CS who clearly hate it because they're muddying the waters for the rest of us.

1

u/TheKiznaProject Dec 30 '23

The funniest thing is they don’t teach you much at all for actually being prepared in the workplace, i learned my entire stack on the fly at every job i’ve started. I suppose labs are kind of like ticketing and work documenting but just take 10x less effort.

7

u/[deleted] Dec 30 '23

I know it's why I did lol. But also my schools electrical and CE department is not very good, so I wanted to do something with a better program

1

u/Cyber_Fetus Dec 30 '23

How is CS less time, money, and effort than engineering? I have engineering degrees but any of the less applied and more theoretical (ie more science than engineering) classes I took along the way were by no means any easier or less effort. And similar degrees from similar institutions are going to cost the same and take the same amount of time.

1

u/RangerZEDRO Dec 30 '23

Are you talking about CS subjects that you took while doing engineering?

At least in my Uni, engineering is 4 years and CS is 3 years. Less time money and effort 🤷‍♂️

1

u/Cyber_Fetus Dec 30 '23

What university is that? I’ve literally never heard of a 3-year BS that wasn’t just condensed.

1

u/RangerZEDRO Dec 30 '23

I think its not a BS, just CompSci

1

u/Cyber_Fetus Dec 30 '23

CompSci... what? Like is it just a certificate? What program are you talking about? What university?

If we're comparing a BS in any engineering discipline vs a BS in Computer Science, they should be essentially the same length and cost.

2

u/RangerZEDRO Dec 30 '23

BS, CompSci Subjects, Bachelor in CS?.

I got confused but it turns out BS is 3 years in my UNI

2

u/Cyber_Fetus Dec 30 '23

Looks like the only engineering bachelors offered there is honors which would add a year, though I am reading that bachelor of engineering degrees in Australia are generally a year longer than bachelor of science. Not the case in the US, as both a BS and BEng would take four years, and most students focused on engineering get a BS with an engineering major, like a BS in Electrical Engineering, etc., so they're generally all the same in time, effort, and cost.

1

u/RovingShroom Dec 31 '23

Yea, as CS major, it gets annoying.

1

u/Latter_Freedom_3377 Jan 01 '24

I don’t necessarily know that this is true, at least for those who went to the school I did. We took the same classes as CE. The difference was - CE required chem, diff eq, and a couple other theoretical courses. Otherwise, the core classes and electives offered were the same.

Chem is what scared me away from CE 🤣 but a lot of my classmates double majored in CE/CS since the workload was effectively the same

-1

u/EncroachingTsunami Jan 01 '24

I went high level as well, low level programming just seemed like a time sink. It also felt like it could be automated in the near future, which is something we're seeing already. LLM's are already pretty good at writing code in simple but domain-specific languages.

29

u/[deleted] Dec 30 '23 edited Dec 30 '23

[removed] — view removed comment

3

u/Majestic_Yam_8478 Dec 30 '23

CE on top

16

u/[deleted] Dec 30 '23

[removed] — view removed comment

5

u/firecorn22 Dec 30 '23

CS is not a branch of EE, it's more a branch of math

0

u/[deleted] Dec 30 '23

[removed] — view removed comment

4

u/sirfitzwilliamdarcy Dec 30 '23

CS is a branch of EE? 😂😂😂

2

u/yaeh3 Dec 31 '23

Alan Turing didn't give a damn about electrical computers.

1

u/[deleted] Dec 01 '24 edited Jul 17 '25

fear childlike familiar soup sheet steer mysterious imminent seed continue

This post was mass deleted and anonymized with Redact

1

u/firecorn22 Dec 30 '23

That's definitely not why people considered CS more closely aligned with math. It's more to deal with the fact that CS is deductive aka we make mathematical proofs to make final claims about computation, like the computation complexity of an algorithm or if a problem is decidable. Unlike other sciences like physics where they use math to model natural phenomena then verify the model accuracy using experiment.

Also Alan Turing was a mathematician

1

u/[deleted] Dec 30 '23

I think CS is on top of that list, but that is because I am a lame math major 😛

2

u/sirfitzwilliamdarcy Dec 30 '23

Math is better than all of them including CS, so your opinion honestly carries more weight.

2

u/NoBrightSide Dec 31 '23

I have a math bachelors and I work as a self-taught embedded software engineer. As someone who actually has knowledge of math and partially of EE/CS/CE, the real truth is that CS is not a subset of EE. And if we’re organizing based on salary, right now CS makes the highest income. Hide me so that the angry bitter people don’t find me 😂