[prewett]

This is a thoughtful article, but I think the axis isn't between builders and algorithm researches, but between craftsmen and results-oriented builders. Both want to build something, but the craftsman cares about the quality of the result (usability, maintainability, code quality, UI polish, etc.) while the non-craftsman is happy with something that works, even if some of the corners are janky.

Or, thinking about Windows and macOS in the Jobs era, perhaps the difference is more between the quality of taste. Microsoft focused on quality code, and came up with COM, architectures where an instantiable button is 13 levels of inherited classes, and things like DirectX, where the architecture is clean and extendable, but forces every developer to do things like allocate their own @#$! framebuffer. High level of craftsmanship, but poor taste. Jobs tended to focus on the user experience and had good taste, so the results were generally pretty good, but I got the feeling that the code wasn't as much of a priority.

[marssaxman]

> Microsoft focused on quality code

That's a sentence I have certainly never read before!

[collyw]

It's closed source, how would you know?

[marssaxman]

I used to work there - but I was talking about their reputation, not the actual quality of their code.