if you're not building/producing stuff with AI that is going to survive (in your brain or elsewhere) beyond your current subscription term or token purchase, you really are setting yourself up for catastrophic failure.
20+ yrs dev exp, 8 books w/ 100k+ copies sold, 300k+ hours watched of my videos, 4k+ taught in person...
And you know what? I still struggle to get my code to work and it's still a tedious slog. And my code still confuses me the next day.
You're not alone in these struggles.
I was rejected for a job by @TwitterEng years ago, even tho I knew several people on the team who liked me & wanted me to join. I was later told by HR that one of the interviewers said I "didn't know JS" very well. That was part of the motivation for @YDKJS. #ShareYourRejections
"Arrow functions are bound to their parent's context." Nope, inaccurate.
Arrow functions do not have a `this`, which means any usage of `this` inside an arrow function is just like any other variable, and is looked up lexically through parent scopes until a `this` is found.
I had some code implemented and fully tested, almost ready to release. Then I was writing the documentation for it, and I realized the code's behavior is wrong and should be changed. TDD wouldn't have saved me here. Docs are equally as important as tests in designing software.
So you've never given a conf talk before, because you think you aren't good enough or haven't mastered a topic enough yet?
Neither have any of the rest of us. Seriously.
The best time to talk is right as you're in the midst of your journey.
The saying "Jack of all trades, master of none" is usually used standalone in a sort of slight against generalists as lesser than specialists.
But the original full saying is quite enlightening:
"Jack of all trades, master of none, oftentimes better than a master of one."
CSS #protip:
The ::before and ::after pseudo-elements don't mean "before the element" and "after the element", they mean "before the element's children" and "after the element's children".
Oh, and not even 2 months later, the first of several "new twitter" redesigns launched, and they used my LABjs script loader library. That's my favorite part of that story.