I heard it just timed out.
Do other devs just open up multiple vs code windows for each project or something? I can't stand not being able to run everything in the same window with ctrl P picking up files from across projects as a reference. I…
The second part isn't...
> Rust can be too much of a mental overhead than it's worth for some. Rust has the least mental overhead of any language I've ever used. The compiler literally takes all the mental overhead away.
It's why breathing into a bag works. You need to slow your breathing during hyperventilation to increase your CO2 back to baseline. Not speed it up.
After the 20 or so comments that responded I'm still no closer to understanding. The SQL guy sort of made sense I guess maybe.
Amazing rant but I really wish they gave you a quick tldr on what the fuck the difference is between imperitive and declarative.
I did this when I looked after interviews. I'd print off a piece of legacy code that was particularly ugly and ask them to review it. I'd tell them I wasn't looking for silly stuff like parser errors and instead was…
Is this a course that teaches you how to make money making courses?
"analogies suck and we shouldn't use them"
I heard it just timed out.
Do other devs just open up multiple vs code windows for each project or something? I can't stand not being able to run everything in the same window with ctrl P picking up files from across projects as a reference. I…
The second part isn't...
> Rust can be too much of a mental overhead than it's worth for some. Rust has the least mental overhead of any language I've ever used. The compiler literally takes all the mental overhead away.
It's why breathing into a bag works. You need to slow your breathing during hyperventilation to increase your CO2 back to baseline. Not speed it up.
After the 20 or so comments that responded I'm still no closer to understanding. The SQL guy sort of made sense I guess maybe.
Amazing rant but I really wish they gave you a quick tldr on what the fuck the difference is between imperitive and declarative.
I did this when I looked after interviews. I'd print off a piece of legacy code that was particularly ugly and ask them to review it. I'd tell them I wasn't looking for silly stuff like parser errors and instead was…
Is this a course that teaches you how to make money making courses?
"analogies suck and we shouldn't use them"