Is the whole full stack generalist / specialist dichotomy a correct one? I'm bootstrapping and I can do a lot by myself: setting up Linux from scratch, install

Is the whole full stack generalist / specialist dichotomy a correct one? I'm bootstrapping and I can do a lot by myself: setting up Linux from scratch, installing & configuring the DB, the proxies, the webapp server, the firewall, write administration scripts, set up the SSH tunnels, do the coding, do the HTML+CSS... Full stack "generalist" way. (Heck, I can even build the server myself if needed). But at the same time I'm definitely a "specialist" in some fields. For example I've been holding my SJCP (now Oracle) Java cert since the last century and I've been coding in Java since more than 10 years and I know some Java frameworks inside out. Sure I'm not a DBA nor a Unix sysadmin specialist but I'm both a generalist in that I can still do it if needed and yet I'm a specialist in certain programming domains. I mean: aren't all generalists still specialists in some particular domain? Maybe too that HN is representative in that a lot of the entrepreneurs in IT will tend to be "full stack"? As a side note, sometimes it sucks to be "full stack" because people ask you to do things you'd rather not do, because you're the one in the company (startup) knowing that area the best. It doesn't make you very good at it, but by knowing it more than the next guys, you get to do it. As a second side note, when working for bigger structure, I've noticed that the DBA, for example, or the Unix sysadmin, do really like it when they realize they're talking with someone who understands what they're doing. Heck, I've helped Unix sysadmin troubleshoot Java webapp server issues because they weren't that familiar with Java ; )