[thebigestmidget]

I'm currently in the middle of finishing a degree in CS. Do you think this will help me in terms of employment knowledge? I know they are completely different fields, but would base knowledge of the fabrication process not demonstrate a wide breadth of knowledge in CS to some degree due to its adjacency ?

[sevensor]

I recommend learning about semiconductor fabrication because it's fascinating. I spent five years as a process engineer in a semiconductor plant, and I saw some really cool technology while I was there. How many other fields use TEM micrographs for debugging? Or make factories with separate foundations for dozens of pieces of equipment, built on piles sunk 60 feet to rest on bedrock? Or have unit processes that include particle accelerators?

However, the chasm between undergrad CS and semiconductor fabrication is too big. There are dozens of layers in between, and all of them are interesting. If you want something more relevant to your degree, study computer architecture or VLSI design. Learn an FPGA synthesis language. If you like quantum mechanics, study semiconductor physics. Learn how a DRAM cell works and why it needs to be refreshed.

At any rate, I don't want to discourage people from studying semiconductor fabrication, but don't do it as part of a CS education. Do it because turning rocks into circuits is an awesome work of alchemy and you can be part of it.

[zamadatix]

From the perspective of someone else wrapping up a CS degree started after I already landed in the field: If you haven't already taken a dedicated "computer architecture" course (separate from whatever they covered as modules in your standard CS classes) I'd do that first and you'll probably get something out of that. If you have already taken such a course (and enjoyed it) then you might find this fun but I'm not sure on how much it well help in terms of employment knowledge vs more closely related study.

[practicemaths]

No not really. It's more for electrical or computer engineers. However there's nothing wrong with gaining more knowledge for the sake of it and it can be just nice knowing a bit about how your machine actually works.

Of course, maybe it is more useful if you're into some really low level programming. But for most CS hardware understanding isn't necessary.