4 ms·
This comment sounds hyperbolic, but it really isn't. It's really bad. This has been my experience with Microsoft employees also. In my experience, what makes
by freedomben 2y ago
This comment sounds hyperbolic, but it really isn't. It's really bad. This has been my experience with Microsoft employees also.
In my experience, what makes for bad software is PM and engineering hubris. You definitely need some vision and confidence as just following user feedback is a recipe for terrible software as well. The key is to find the right balance and straddle that line.
If it's been long enough for insiders to tell the story of Windows Phone and the eventual cancellation, I'd be fascinated to hear the story of that (from inception to death) and how that went internally given the culture.
- tracker1 2y agoJust wanted to say that I thought the Windows Phone (the last version of such) was relatively nice. It had a decent developer experience, but was pretty much an also ran and didn't have enough market share to overcome mindshare for first party apps. When so many first apps were iOS first and Android later, throwing a third option in the mix just missed the mark more often than not. I was already in the Android ecosystem and far less cynical at that point about Google.
- Ylpertnodi 2y agoI didn't get a Windows phone because i don't trust Microsoft. A friend had one and it was really ok, but no way for me.
- fingerlocks 2y agoCan confirm, it is 100% hubris based on my limited time of working at Microsoft. There is pervasive NIH syndrome, re-inventing the wheel, and massive amounts of over engineering and unnecessary abstraction caused by chasing the endless "But what if...?" dragon. This behavior is justified, and critics are silenced, by the "But we're an enterprise company!" cop-out