3 ms·
In my 20s I had this mindset that I always needed to be learning a new tool or language. After a decade plus of that, I found a tech stack that I liked enough
by gdulli 5y ago
In my 20s I had this mindset that I always needed to be learning a new tool or language.
After a decade plus of that, I found a tech stack that I liked enough to stick with long term. I didn't plan it that way, I just found one that made work enjoyable again and decided none of the technical improvements other tools might offer would outweigh the quality of life I'd found.
What I found after sticking with the same language and toolset for 5 years was that there was a new level of mastery I'd never known before.
I was writing code as fast as I could write English. I was spending up to 100% of my dev time on a given day working on purely the functionality in my project. Little to no time spent looking up how to do things.
Nobody deserves any shame for looking up info to help them code. We've accepted it's an important and reasonable part of the job. And it never bothered me.
But when I experienced for the first time that I'd truly memorized and internalized nearly everything about my day to day work, I found a surprising and unprecedented level of focus on what really mattered.
All those context switches throughout the day hopping between coding and figuring out how to do something, they'd become so normal to me and to the field that it didn't occur to me that they were not strictly necessary.
I could switch to a new language today and be fairly productive with it a week from now. It wouldn't feel weird to anyone that I was spending a lot of time looking up info to learn how best to work with it. Even experienced devs do that.
But what I understand now is the true cost of being on that treadmill to chase skills I think I'm supposed to have because they're newer and fit one of the subjective definitions of "better".
Feeling less pressure to spend my free time constantly upgrading my skills hadn't been a motivating factor, but it was a bonus. You still want to learn new things, but you should understand that much of what we're bombarded with are new ways to do things we already know how to do, in a supposedly better but really just different way.
- dondraper36 5y agoThank you for writing this. It's not that I have many years of experience in the field, but the more experience I get, the more I understand that it's easier (mentally) to accept that I can concentrate on few foundational subfields without criticizing myself for not being proficient in multiple aspects. With my current programming language, I feel sort of productive, but then I find an article or a talk by someone infinitely more knowledgeable than I am, and that generates self-doubt.
- gdulli 5y agoA lot of blogging is shallow or wrong or irrelevant even if it is high quality. Knowledge is free, knowledge alone isn't important or very impressive. We don't get self doubt from not finishing the encyclopedia. You could be in the top 5% out of millions of engineers but that still leaves many who are better than you. You can go your whole life never running out of stress because there's some hypothetical way to be better. But that's a choice. It's not worth living in self doubt or pressure to catch up to the absolute top. There's no super bowl to win. You only need so much tech knowledge before your actual limiting factors are wisdom of how to apply it, which only comes with time, or non-technical development.