Only those on the outside not involved with Windows desktop development with agree with a stellar job description.
Those still involved in Windows desktop, will assert that they are running like headless chickens, no clue which UI framework to invest, downgraded the development experience back to pre-.NET days, no longer hold the golden rule of backwards compatibility, and have teams of a ridiculous tiny size, only capable of bug fixing and very small feature development.
So most likely any employee involved in Windows desktop development, that doesn't drink the Kool Aid of COM/C++, will also not vote with much thrust on their business unit future.
Is this why Teams has steadily gone from useful to useless? It used to just work, and now it's a source of frustration multiple times a day with bugs and delays and features being lost in the new version. So annoying.
> Those still involved in Windows desktop, will assert that they are running like headless chickens
I was wondering what was going on there because Windows is so incredibly bad in so many ways. I need my computer for productivity - not consumption - and Windows really seems good at getting in the way a lot of time. If I could jump back to using a Mac for work I would do it in a heartbeat.
Those still involved in Windows desktop, will assert that they are running like headless chickens, no clue which UI framework to invest, downgraded the development experience back to pre-.NET days, no longer hold the golden rule of backwards compatibility, and have teams of a ridiculous tiny size, only capable of bug fixing and very small feature development.
So most likely any employee involved in Windows desktop development, that doesn't drink the Kool Aid of COM/C++, will also not vote with much thrust on their business unit future.