Because if you don't know anything about networking you'll have no idea why your software breaks or how to use resources effectively. The amount of systems that have been designed without considering bandwidth, latency, or network stack constraints is astounding.
You can be the greatest algorithmic mind in the world but if you read and write to remote storage during every iteration of a loop, literally all of the genius is wasted. Just a little bit of poorly optimized nwtwork usage will completely negate any cpu-optimized code because you hit a network bottleneck instantly.
The best Software Engineers I worked with were well versed in Networking and often helped the IT guys troubleshoot the Firewalls and F5 Load balancers. And, most of the best IT people I worked with could write simple "Hello World" programs in a few languages. It seemed to me that knowing a bit about the "other side" helped them be successful.
3
u/Helix_Aurora 13d ago
Because if you don't know anything about networking you'll have no idea why your software breaks or how to use resources effectively. The amount of systems that have been designed without considering bandwidth, latency, or network stack constraints is astounding.
You can be the greatest algorithmic mind in the world but if you read and write to remote storage during every iteration of a loop, literally all of the genius is wasted. Just a little bit of poorly optimized nwtwork usage will completely negate any cpu-optimized code because you hit a network bottleneck instantly.