3 ms·
> Their productivity is more a function of their understanding of economics writ large, than their recall of algorithms or specific toolsets I agree with your
by zasdffaa 4y ago
> Their productivity is more a function of their understanding of economics writ large, than their recall of algorithms or specific toolsets
I agree with your post except for that bit. IME it is very much down to a more creative and questioning approach to coding that separates the better from the less good.
I don't think, again IME, that asking the question "but should we?" has ever got me that far (though it is a good question) because bad managers take no notice and good managers have already asked it.
- cmollis 4y agoI think what I was trying to say is that the best performers attempt to understand the problem domain more holistically than, say, more average performers. What are the forces driving all of this and how do I deal with those forces in the most efficient way. Obviously, a dramatically more productive engineer also has deep experience is probably many toolsets, languages, etc., and that experience informs many of the decisions that they make when crafting a solution. However, I would argue that they have forgotten many of the picayune details of each, and only retain the most useful conceptual capabilities of those experiences so they can apply them quickly to some new and (seemingly) unrelated problem.