2 ms·

IT is easier than CS, but it's a huge amount of knowledge. It just takes the to learn. Enormous accounts of time. Even more practice to be fluent and fluid. CS

• galdosdi 2y ago
  IT does, if you're doing it right: - Computer architecture (how do you make a syscall to the kernel? How do page faults happen? Branch prediction? Plenty of recent major vulnerabilities involving stuff like this) - OS architecture - blends in with the above - how does process scheduling work? - Networking protocols/algorithms and the underlying queueing theory (eg how does BGP work, what are its failure modes, what's the math behind TCP congestion control, exponential backoff, complex multicast architecture, blah blah blah. Networking can be genuinely hard if you push it hard (and you often do, when you are trying to make money) Traditionally these are harder to learn since they were harder to encapsulate and virtualize. Unlike "platonic" coding, these were traditionally hard to get experience outside of a real job situation (And even if you can simulate it, there's a lot less motive for a hobbyist to set up a simulated anycast network than to write some cool web app or desktop tool) leading to a chicken and egg problem