You get most of the day off after having worked a full day + still need a full and thorough shower + have low energy because it's a physically demanding job

Src: did it for 3 years as student job

Depends on how deep down the rabbit hole you want to go :p

• creating a new variable that contains the updated value
• recursion (e.g. it's not possible to make a loop that increments i by 1, but it is possible to turn that loop into a function which calls itself with i+1 as argument)
• avoiding typical types of operations that would update variable values. For example instead of a for loop that updates every element of a list, a functional programmer will use the map function, which takes a list and a function to apply to each element of that list to create an updated list. There's several more of these very typical functions that are very powerful once you get used to using them.
• monads (I'm not even gonna try to explain them as I hardly grasp them myself)

Paywalled article

It's all learned behaviour. If you grew up with F that makes total sense and C sounds ridiculous. If you grew up with C that's totally intuitive for anyone, just as much as F, so using a scale that has no point outside of the weather sounds dumb. Neither system is more intuitive by any means. Both systems ave benefits and downsides.

Whenever I talk to americans and they use F I need to convert it because I grew up with C and that just makes more sense to me, even if I know the "0-100 F is according to human experience" thing. Like sure, 80F is hot, but how hot is it? Oh 27C that's hot but not extreme.

Arguing one or the other is superior is not only pointless but also just silly

Reed hucks = redux Heather net = ethernet

FreeRTOS tasks are basically processes, IIRC other rtoses have similar mechanics too

if(condition) statement; Is valid in typical C-style syntax.

if condition { ... }

Is invalid in typical C-style syntax

Diese maimai stört mir nicht

One crate is still one item

Here: "yes it does support TLS1.3"

That's actually hilarious

Typescript saves ridiculous amounts of time in bugfixes and is IMO a lot more readable than JS.

I don't know how many times TS has complained about some type mismatch in my code that made me scratch my head for 2 seconds to only then realize I was doing something stupid. With plain JS that would've been no issue, until I have some obscure bug 30 minutes later and have to figure out it's source.

Also, whatever piece of code you are working on, to do anything you have to have the types of your variables/functions in mind. If you have to keep track of all of them in your head, you will definitely mess it up at some point or have to look through a bunch of different methods/files to track down the source of some piece of data to be certain what's contained in it.

So yeah, TS might take slightly longer to type out, but it saves you a lot of dev time.