DEV Community

Discussion on: Jack of All Trades, Master of Some

Collapse
 
oloryn profile image
Ben Coleman

There's also the risk of becoming the sole go-to person for too many things, which can lead to job fragmentation. I've been there, because I've always been the guy who actually reads the documentation (shortly after I graduated from college(back when dinosaurs roamed the earth), I was actually reading IBM mainframe manuals for leisure reading)), which meant that when anything new came up, I was the one who was typically given it. This can be enjoyable for awhile, particular if you're the type of dev that enjoys learning new things, but there comes a point where you're pulled too many directions at once.

Collapse
 
mattschwartz profile image
Matthew Schwartz

Absolutely agree. I also started back before Google when books were the primary source of information. I became the one who was usually able to answer my coworker's questions on various technical topics, so of course they often came to me first. I enjoyed it but after years it can get tiring.