6 ms·
Perhaps. But is it meaningful to talk about these incredible outlier cases when considering how you structure an engineering organization? I think there are tw
by UncleMeat 5y ago
Perhaps. But is it meaningful to talk about these incredible outlier cases when considering how you structure an engineering organization?
I think there are two kinds of companies that make tech:
1. Companies where all of the technical problems they need to solve can be solved by typical engineers.
2. Companies where some of the technical problems they need to solve are too difficult to be solved by typical engineers.
In the latter case you do need "special" engineers and you need to point them at these problems. But what percentage of companies fall into category #2?
- solveit 5y ago3. Companies that have technical problems that can easily be solved by typical engineers but not noticed and articulated by typical engineers. Which is most of them. The main value of "special" engineers come from them pointing you to the right problems. Notice how all of Ritchie, Shannon, Dean and Buterin certainly fall into this category. They were all technically proficient enough, but that's not the point. A seasoned veteran would have coded circles around Buterin at age 20, which is when he invented Ethereum. The point is that the seasoned veteran didn't invent Ethereum. Similarly, Shannon's most influential work (that paper that basically invented information theory) is fairly elementary, and basically any geezer with a relevant PhD had had the technical chops for the paper. But they never would have written that paper in a million years.