Yeah there's absolutely value to being a jack of all trades, they're just different paths. Also, I don't think being a fullstack engineer necessarily means you can't also be a subject matter expert in something. 95% of "fullstack" engineers I've met tend to actually be more specialized than they might say, but just also happen to have enough knowledge to work in other areas than that specialty. And sometimes that piece of knowledge they are an expert in involves both sides of the stack (server side rendering for example). Also, your English is perfect. I didn't realize it wasn't your first language until you said so 👍

as a generalist you will always be very employable though. it’s beneficial in a different aspect. not a bad thing.

Thank you! I'm glad you're finding so much value from the content 😀

Thanks for watching 🤝

How you started? I'm learning html & css , will start javascript in few days. How much time it needed to get a entry level job. My goal is to be frontend developer.

Don't worry about it too much. Half of university students don't know what they want to do, let alone what they want to sub-specialize in. Most of the "best" developers I worked with bounced around between roles before finding the one thing they were best at and enjoyed the most. Many did this for a very long time, which is perfectly fine too.

@@ConnerArdman Thank you so much for the response. I'm on an internship right now and I feel like I've learned an insane amount of cool things from it, which I'm really happy about.

Yeah there's no one-size-fits-all answer. It just depends on what your individual goals are, where you're working, etc. That said, for the purposes of this video (not just being successful, but being in the top 1%), I think some degree of specialization is usually necessary. As for software architects, I don't have a strong opinion tbh. I've never worked anywhere that had "architect" as a position, at least not one that I've interacted with. I've always worked in environments where architecture decisions were made by the team as a whole and led by tech leads. That system has always seemed to work well for teams I've been on, but that's not to say having a dedicated architects wouldn't have worked better, or that it wouldn't be a better choice for other teams.

@@ConnerArdman I really appreciate your honest answer @CornnerArdman :) . To be honest, before I was trying to be specialist, technically speaking, but after that I realized that we need to have a balance, and now I have another mindset regarding to build a T Shape for knowledge. In few words, You need to know a little bit about everything, but you don't need to have the same deep of knowledge for everything, so it's like combining Generalist + Specialist. btw, really good content! please keep sharing the knowledge with the world. 🍻

If that's what you find interesting and you can consistently find work doing it, then more power to you. More realistically though, it probably makes more sense to be a frontend engineer who happens to have a bit of a subspecialty in accessibility. That would likely be a more marketable skillset imo.

no

I don’t. I might do it eventually, but probably not anytime soon.

The best majors in software engineering front end or back end or mobil developer

You mean like university majors? Computer science, computer engineering, software engineering, informatics, applied math, etc. are all “good”. Just depends what interests you. Same is true with specialties like frontend, backend, etc. None are better than others, just depends what you’re interested in.

​@@ConnerArdmanI am studying business administration at the university, but I want to learn back end or front end Because I do not like the Faculty of Management, but I have to stay in it

I just might be saying that 🙃

The point wasn't that you need to be an expert in exactly one thing and do nothing else. As I said in the video, the jack of all trades vs expert in 1 niche area comparison was an intentionally extreme example, and in reality you probably want to be somewhere in between. It also depends on the depth of each "area" that you choose to be an expert in. For example, you can be a JavaScript expert and make an incredible entire career out of that as it's a fairly broad area. On the other hand, if you're an expert in GraphQL queries, while that's great, you probably will need other areas of contributions as well to get there as there's less impact to have in that area. That said, if someone had the "standard" fullstack developer skillset while also being a deep expert in GraphQL queries, that one area of expertise will allow them to have some of that unique impact, while also still being broadly valuable to the team for other work. It's also worth pointing out that this video was literally about the 1% of developer impact, as in 1 out of 100. You can be anywhere on that spectrum of expertise and have a great career, and in many circumstances the jack of all trades might be the most valuable asset to a company. But every single developer I have met that truly had a unique 1% trajectory had a deep level of expertise in at least one thing, and as you mention some had that level of expertise in a few things. That's not to say they weren't great at things outside of that area of expertise, most were, but they just had one or a few things that caused them to stand out from every other great developer.

I'm not sure what you mean by "the scope of a subject dies out," but you can never learn everything (and should never try to).

Fair enough, thanks for the feedback 🤝 And glad you enjoyed the actual contents of the video!

Glad you liked the video! Most of these things are all things that can be worked on very late in your career, it's never too late 😀