Also surely a lot of people would know tar -Create Ze Vucking File and/or tar -Xtract Ze Vucking File

Funny story actually. After year 1 I was in peak condition, year 2 was normal, year 3 I gained weight. Year 1 I worked slowest and year 3 fastest. I just became way more efficient :p

Running is not as extreme as you think, a lot of it is just carrying on the momentum of the truck after you jump off, other tham that it's mostly just brisk walking.

The heavy stuff depends, regulations typically impose a limit on weight but a lot of people don't follow it. You learn to use proper lifting form quite quickly though or you'll get a hernia

Src: did it for 3years as student job

Nope, IaaS. With a VPS you are in charge of everything except for the hardware. PaaS the only thing you're in charge of is your code.

"Your secret is safe with my indifference" - Taliesin Jaffe

Alternatively, get good, consistently win games against people who are worse, stop coping and you'll get to the rank you deserve.

There is no such thing as elo hell, if you're consistently outperforming your direct opponent you will win more games than you lose against people of your MMR and you will climb. "Elo hell" is just a coping mechanism for people who can't admit they're bad

Also being able to analyze any program and guarantee it will stop

I had to translate this to german to understand... and I'm not even german

JS was a mistake.

Actually I'm not so sure. That honestly sounds like it could lead to several significant issues, such a

I am dumb. The more things I need to think about when reading code that is not the logic of the code, the worse it is. Any time I have to spend thinking about the peculiarities of the way the language handles something is time wasted.

I'll give a very simple example, think like you're trying to find a bug. Assume we're in a dynamic language that allows implicit conversion like this. We can write our code very "cleanly" as follows:

if(!someVar) doSomething();

-> ok, now we gotta check where someVar's value is last set to know what type of data this is. Then I need to remember or look up how those specific types are coerced into a bool.

When trying the same code in a statically typed language that doesn't do implicit coercion that code will fail to run/compile so probably you'll have something like this:

if(someVar.length() == 0) doSomething();

-> this time I can just look at the type of someVar to see it's a string and it's clear what the condition actually means.

The second option is both easier to read and less bug prone even without the type system. It takes maybe 3 seconds longer to type, but if your productivity in coding is that limited by typing speed then I envy you

Depends on your eslint config, but yeah that's an option.