| I think for building things, especially in a small team, a Jack of all trades is preferable. I think it depends on what you want to do. As you said, you feel confident in implementing something. I think that's the key thing, getting the implementation done or getting the project built. There is certainly room for the specialists, take security for example, implementing certain types of security take a specific set of knowledge and experience. If that's what you love to do, then that's a fine path. If you'd rather build things or like to experiment, a more general approach is good. You can always team up with other people later on if you need more specialisation in a certain area. I think as well that Jack of all trades doesn't apply as much to technology as it does to building for example. A builder may specialise in bricklaying for example. That's great, building a modern building on your own is going to take a team anyway. Besides, bricklaying probably isn't going anywhere any time soon. Technology on the other hand is constantly changing. You could be a specialist in a programming language that five years down the line is mostly irrelevant with weak support. I think in a way, you're both. You seem to specialise mostly in programming, while generalising within programming. I think that's a good mix to allow you to develop a strong and useful skill set while remaining lean and adaptable. |