Sep 19th, 2018
In this episode Wes and Scott discuss specialization vs generalization - the different ways one can be a generalist or a specialist, advantages and disadvantages to both, and, ultimately, which is the better career path.
Get a 30 day free trial of Freshbooks at freshbooks.com/syntax and put SYNTAX in the "How did you hear about us?" section.
Dev Lifts - Thad and JC are on a mission to make web developers healthy. They're currently offering Personal Training and Nutrition Plans as well as a new program called Fit.Start. Get 50% off with the coupon code "tasty". Check it out today!
4:18 - What is a specialist?
12:20 - What is a generalist?
22:22 - Frontend vs Backend
26:50 - When to widen your focus
30:42 - When to narrow your focus
35:48 - How to master and expand
38:47 - Scott's journey
42:31 - Wes' journey
44:55 - How to know where to focus
51:03 - Should I be a generalist or a specialist?
Wes: There is nothing wrong with having a large skillset as long as you aren’t mediocre at everything. If you're optimizing for hire-ability I think having a defined focus on either front-end or back-end is best, but still an understanding of how the other works. Ideally you have 1) Very good JS skills, 2) an understanding of how things work on both ends.
Scott: You can do either, but whatever you do, do it well. It’s easier to do a few things well than many things well. That said there are some virtuosic devs out there who can be amazing at many things, however those people are not common. Most people have holes in their armor.