It's not 'looking up the part code' it's identifying components that have level and drive compatibility, fanout and timing requirements met, acceptable internal and parasitic inductance/capacitance/resistance. Checking if the nets are still theoretically a wire and not a transmission line, that ringing isn't degrading intended application, that the final output of the logic can actually drive the output of the logic diagram. Ensuring the lead time, footprint, cost, and supply chain are all compatible with your manufacturing process and planning.

If you just use theoretical perfect lossless and timeless components you completely miss and forget about a huge portion of EE which is not just designing the logic but actually implementing it in reality. It sounds like the EE program was setting people up to take the real world and imperfections into account while the CS version of the same course makes the valid assumption an electrical engineer has already provided the hardware platform so you can focus on the logical implementation.

>Isn't the key lesson to learn the logic flow design

In CS yes, in EE no. In EE that is only one of many key lessons, and without interlocking with other key lessons necessary to pick the real world components you end up with a circuit that either works purely out of luck, only in low-speed designs in noiseless environments, or not reliably.

Do individual logic gates even have part numbers anymore? In my EE labs in college we had FPGA’s.

Here's a 4 channel OR gate

https://www.digikey.ca/en/products/detail/texas-instruments/...

But my logic labs were also done on FPGAs.

"Kids these days" ;)

Yes, I think now it's mostly the 74AHC, 74ALVC, some 74ALS/74HC families (maybe others) Depends on the application https://en.wikipedia.org/wiki/7400-series_integrated_circuit...

(using the fpga is fine, but I'd probably want to focus on the circuit itself ant not something like VHDL at first)

To be clear, this was a 200-level EE class that was, at the time, also part of the CS curriculum. One of my favorite classes, at least in retrospect.

The professor was simultaneously the founder of a company that made FPGA boards for EE students. They also made a little microcontroller board that was basically Arduino before Arduino; we used that in another class where we made robots and programmed them in AVR assembly.

They're still used sometimes for low level ancillary board functionality. Like, controlling reset lines going to SoC's, etc.

It's actually something that an EE may end up using in their career quite often if they're doing board design.

Though, we normally use CPLDs for that kind of stuff now, but if you can get away with a few logic chips, maybe it can simplify the design.

BTW these hardware glue logic is often done with e.g. TI LittleLogic series (i.e. 74LVC1/2Gxx) where you can use a tiny package for a tiny function otherwise not integrated into big chips.