r/ComputerEngineering • u/IllustratorSea9212 • 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
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.