4 ms·
I would still learn at least basics of TCP and IP, so that you are aware e.g. what firewalls do and how this shows up on the client side (vs when nothing is lis
by isbvhodnvemrwvn 4y ago
I would still learn at least basics of TCP and IP, so that you are aware e.g. what firewalls do and how this shows up on the client side (vs when nothing is listening on the port but the port is otherwise open), what private IP ranges are, or what a timeout look like. These are the basics which are going to be extremely relevant when you start troubleshooting. Especially if they slap a docker image on their VPS. There's a frightening number of people who can't tell DNS resolution failure from a timeout, think they are going to get HTTP 500 if server breaks the connection, or don't take those failures into account (and it shows up in how they design their code).
- tusharvaswani 4y agoCan you please share some resources which could help me in that!
- __d 4y agoThe W Richard Stevens book "TCP/IP Illustrated, Volume 1" taught me, but it's not really a good overview: more of a deep dive. Still, that along with his companion volume "Unix Network Programming, Volume 1" will help set you up for a rewarding career. A quick search suggests both are available as PDFs from multiple sources, or you can get the hardcover Bible-style editions, which I personally find quite fitting.