I feel like the only people that "like" javascript or those that had it for their first language. Its needed, its better than it was, but compared to just about any other language its a total mess.
I'm using TypeScript and JavaScript interchangably.
I know JavaScript like the back of my hand, so TypeScript isn't telling me much new, but the static type checking allows me to keep less of that knowledge in working memory. Pretty awesome language!
Rust is hardly omnipresent. I understand it has trouble with lesser used architectures and operating systems. While yes you probably dont use them, they do still exist.
I allow my kids to plea their case anytime they disagree. They get one shot so i usually remind them of that and they usually disappear for a bit thinking their case through before coming back. Now i keep an open mind and hear there side on why whatever i just decided was unfair or why i was wrong.
If its a good case (or they argued it well) i change my mind. IF not then the answer is final. Period. There is never a second go. Now this seems harsh but you can't negotiate with terrorists. Once a decision is made the sooner they learn its whats happening the sooner they quit that trying to wear you down thing.
Those are the standard tools of distraction which I employed in earlier years. I actually mean standing quietly still and shifting as much 'internal attention' as possible to the injured toe.
IF when discussed usually means fasting daily. So maybe your food window is only between 4 - 8 pm. The anti-aging stuff you saw/read (if its the same that i did) was more about actual fasting where you might not eat everyday and here they did find some linkage to aging.
I am under the impression that IF usually refers to the now popular (thanks BBC) 5:2 schedule. This is the context I've most seen/read about the topic, which often includes the talk of anti-aging and autophagy.
But this is all very muddy waters since it's fad diet territory and unscientific claims abound.
I was for a couple weeks... I had no hunger... had to add protein drinks during the day to get my protein in (at least 60g/daily). I'm trying to get back into it..lately.. I've been just trying to eat between 2/8 and not really care what I eat just try small portions and only till I'm 3/4th full.
Sunday, I started keto again though... and hopefully my appetite diminishes again... got a little lax around my birthday/thanksgiving.
Because Deep Work is more a "how", while The Shallows is more of a "why". It's good to know why, before you try to get to know how. Specifically, The Shallows is an investigation into what the Internet and modern technology does to the brain and what kind of side-effects it may have (affecting our ability to focus). It's a very well-written and accessible book.
Deep Work is more of a how-to book - about how to get ahead in world that's losing its ability to focus (due to the stuff described in The Shallows).
Excluding chasing the shiny object (the javascript race you mentioned) lifetime learning is part of the job description. If you don't love to learn and to apply the things you have learned the tech industry really isn't for you.
Also 1-2 languages... that's really on the shallow end most devs, myself included, will learn a lot more than that and each new language is much easier to pick up then the previous ones.
However as you get more experience, at least for me, you tend to stick to a handful of languages that each cover a domain.
OO, Functional, Dynamic/static variants and a language/stack that allows fast prototyping of ideas.
> If you don't love to learn and to apply the things you have learned the tech industry really isn't for you.
Should that be the case though?
I'm actually skeptical that a lot of the new things are actually as valuable as we think they are. We tend to allow our feelings on technology to bias our estimates on productivity. I've heard tons of developers opine at length about how some new library, language, or platform increases productivity. It usually boils down to the "niceness" of the thing and how they feel using it, or some sample project that only measures time to first deployment, and not the overall maintenance burden. None of it is ever actually measured.
Yeah 1-2 was me trying not to limit this to the guys who've been around for years. I'm probably at 4-5 and think it's common.
> If you don't love to learn and to apply the things you have learned the tech industry really isn't for you.
Not everyone is in this to learn. I've been on govt contracts where a dev has been there 10-20 years and has only learned 3 languages, (and is writing the same way this year as they did 5 years ago). It is not my cup of tea (hence the past tense).
My point is, not everyone loves to learn. If you want to excel you need to constantly learn but if you get into tech and you hate to learn you'll flounder until you find a gig that will let you coast for years.
