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).
The 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.
They are Czech on paper, founders and most high level employees are Russian. Their main dev center used to be Sankt Petersburg, that's why Kotlin is named like that.
Most of the people I knew who used to sit in St Petersburg back in the day when I worked at JetBrains are now somewhere more western. They have a pretty significant office in Munich, for instance.
Their offices in Moscow (Capital of Russia. Largest city), Saint Petersburg (Second largest city in Russia) and Novosibirsk (Third largest city in Russia) were suspended indefinitely in March 2022[1]
It's not unlikely that you missed some hints of the latter part of the article (JS equality for functions or objects) although it's difficult to say without seeing the code.
I suggest never access native files, if you are still keeping your code in C:\ somewhere I think you're approaching WSL the wrong way. Go all in and I've never looked back
Stock docker puts entries in your iptables which usually fully bypasses your firewall. try installing docker on stock Ubuntu, run a container with an exposed port, put ifw up blocking all traffic, and the container is still going to be reachable.
It didn't work for me at all. I used the machine three times and always got different results. That was 2 years ago so maybe they improved, but I was very disappointed, especially with heel width.
Most people who have scooters around me use it for part or entirety of their commute. They just carry it in buses, trains or trams and have them stashed under their desk at the office. They are at no point left unattended.
