5 ms·
I have a BS in CS. 90% of the concurrency I know is self taught, 98% of the I/O I know is self taught , 85% of the networking I know is self taught. I went to
by Taek 6y ago
I have a BS in CS. 90% of the concurrency I know is self taught, 98% of the I/O I know is self taught , 85% of the networking I know is self taught.
I went to RPI, which is not an ivy school but it is a good engineering school.
- xmprt 6y agoFor me it's that 85% of the time I use networking, you're using something that I learned by myself. But that 85% accounts for only 10-15% of the knowledge. So there are a lot of concepts that I learned in school (like DNS, link/physical layer, microarchitecture, etc) that I rarely use. But just because I don't use a lot of the stuff often doesn't mean I never use it. And even the things that I really never use (like programming an FPGA) aren't things that I regret learning.
- bashinator 6y agoIs some of this a failure to distinguish between software engineering and computer science? Some famous CS person quipped that "CS is no more about computers than astronomy is about telescopes." That's fine for studying applied information theory and whatnot, but it seems like maybe the time has come for a formal bifurcation of the fields.
- Qwertious 6y agoComputer science needs renaming - like you said, computer science is not about computers, and it's obviously not about science either (it's closer to maths).
- deleted 6y ago[deleted]
- sjy 6y agoAren’t the fields already bifurcated? Software engineering degrees exist. The fact that many software engineers have a more theoretical degree in computer science isn’t that unusual; you see the same pattern with business and economics.
- selimthegrim 6y agoAny good concurrency resources you recommend?