For me, breadth of knowledge is more important than depth as I start working on a problem.
My thinking is that lots of different perspectives and a wide range of experience helps me pattern-match the shape of the problem — "oh, this is kinda like that thing and this other thing put together" — and make the right choice when deciding how to approach a solution.
The specifics come later, which is when I would try to build some depth in the solution space.
I have a front-end reading list on my website which has a whole range of talks and articles that hopefully help with breadth and depth. It's made of resources that I found I kept coming back to.
Specifically, I think it's really important that to have some experience with static types, functional code, immutability, and a few different async primitives like Promises and queues.
For me, breadth of knowledge is more important than depth as I start working on a problem.
My thinking is that lots of different perspectives and a wide range of experience helps me pattern-match the shape of the problem — "oh, this is kinda like that thing and this other thing put together" — and make the right choice when deciding how to approach a solution.
The specifics come later, which is when I would try to build some depth in the solution space.
I have a front-end reading list on my website which has a whole range of talks and articles that hopefully help with breadth and depth. It's made of resources that I found I kept coming back to.
Specifically, I think it's really important that to have some experience with static types, functional code, immutability, and a few different async primitives like Promises and queues.
Thank Tom!!