Re:Ask HN:"Engineering” a sequence a projects to become a mo...
by gaandmaraa on Sunday October 26, 2014 @11:33PM
(#8513636)
That's a massive compendium! I wish I had been more crisp in my question; the thought over here was to figure whether there's a simpler step by step process to minimize frustration and maximize your confidence on your path to becoming an enlightened generalist (which would naturally takes years to accomplish). I'm mostly interested in the "sequencing" of these steps which is why I provided a rather contrived example of the web app that grows in features with each iteration. For junior devs it's usually pretty hard to figure this out on their own so they end up either doing a deep dive in a very limited number of technologies (ex: Building a webservice in Spring + Hibernate ecosystem comes to mind) without or just float up top at very superficial layers.
You've done an incredible job at detailing the expectations of a generalist but might you have some recommendations on forging that path for people interested?
Here, let's propose some things I'd expect a generalist to be able to do:
This is not an exhaustive list, and I don't expect everyone to be 100% on it. That said, if you call yourself a "generalist" and can't do like at least half of everything in each of those categories, you're either a novice generalist, or you're full of shit.EDIT:
I left out so things applying to programming languages, applying to machine learning, applying to graphics, applying to electronics, and several other things. Being a generalist is hard.
This is also why a good one is expensive.