|
|
|
|
|
by kylebrown
4879 days ago
|
|
I've recently been appreciating Cal Newport's latest book "So Good They Can't Ignore You". Wish I was able to read it when I was younger, but like most I was caught up with the "find your passion" hypothesis. The book deconstructs this passion hypothesis for a fallacy, and prescribes a craftsman mindset ("what can I offer the world?") over a passion mindset ("what can the world offer me?"). Don't worry about finding your true calling, just get good at something which few other people are good at (skills in low supply - so not video games, sports, etc). Get good by doing "deep work", not just superficial exposure. This Ira Glass quote spoke directly to me: "I feel like your problem is that you're trying to judge all things in the abstract before you do them. That's your tragic mistake." Doing "something with value" requires (valuable, low supply) skills ("skills trump passion". skills also trump courage, as in the "all it takes is courage to follow your dreams" message of courage culture from which comes the OP article). Developing skills requires deep work. The deep approach is to narrow the focus from "be good at math" or "be good at programming", or even "understand functional programming". This is the broad/abstract approach I've had in the past, which, in retrospect at the ripe old age of 28, has not worked super well. New plan is to hone a craft by choosing to work intensely with "this particular design pattern" or "this particular javascript library" (looking at you d3). Most importantly, to get good at building stuff by building stuff (craftsman mindset). Get good first, because you won't become passionate about something you're not good at. |
|
May I ask if you've always been a developer and this was limited to languages / paradigms or was this am I a DBA/Systems Analyst/Dev or perhaps even wider?