3 ms·
IIRC the conversation I've had with a former Microsoft employee, some features are developed as mini competitions. Requirements are sent to the group(s) and fi
by bayindirh 7y ago
IIRC the conversation I've had with a former Microsoft employee, some features are developed as mini competitions. Requirements are sent to the group(s) and first acceptable implementation gets merged.
e.g. for the Ribbon-UI in Office, there was 3-4 implementations until one was selected as final.
So the Windows search UI is the fastest developed one with acceptable features.
- marcosdumay 7y agoOuch. If I wanted to create a process with the goal of generating technical debt, I wouldn't get something that effective. It's even beaultiful how it leverages all the competition flaws to get this result. I imagine the result is reflected on the employees productivity assessment and the worst performers fired, so it can exploit evolutionary dynamics to create the highest possible amount of debit.
- bayindirh 7y agoRemember, this is the same Microsoft where people are frowned upon for merging fixes and optimizations to the Windows kernel instead of implementing new-and-shiny features [0]. [0]: http://blog.zorinaq.com/i-contribute-to-the-windows-kernel-we-are-slower-than-other-oper/ http://blog.zorinaq.com/i-contribute-to-the-windows-kernel-w...
- TeMPOraL 7y agoI wonder who had such a brilliant idea. Merging in competing whichever variant got to meet the spec the fastest? It's setting yourself to fail.