Speaking as a greybeard, it's not really that valuable. Younger people are just as smart, if not smarter, and they can figure it out if I get hit by a bus. There's literally nothing I know that someone younger couldn't learn or figure out.
The more sensible take is “don’t use new technology where it doesn’t make sense.” The start menu should need a web browser engine and a heavy JS framework because…?
Well I don't use Windows so I can't comment on the quality. And I actually don't even really care about it. I was just commenting on the curmudgeonly perspective that young people can't do things right.
Another way to look at it: Microsoft APIs have fallen from grace. Even their own devs don't dogfood anymore. They download something that Facebook made instead and reimplement the Holy Start Menu using that.
I think it was perhaps useful, at least in knowing which things are Chesterton's Fence. I doubt that AI can figure that out, since it's not always possible for humans to figure that out either.
But with AI, simple codebase understanding or even just paving over everything, including the fence, is potentially easy, and getting easier each month.
Certainly, a certain amount of senior experience is needed. The AI lacks taste and discretion. But the greybeard sensibilities the come with increasing seniority will probably hold back the new pace of things.
Get rid of their highest-paid employees, replace them with off-shoring and AI.
Eventually the fact that the US military and government is getting tech support from overseas will catch up. Microsoft is a walking national security disaster.
But all they care about is "line go up next quarter". Their monopoly has made them lazy.
They’re probably not the only people who keep the lights on. And if a few people are gate keeping information, you already have a problem that needs fixing.
How do you go about fixing the problem if you end up buying out all the people with the domain knowledge you were hoping to preserve? That's like burning all the treasure maps before you set sail.
Not saying a move like this won’t have any impact, but over emphasizing on domain knowledge is detrimental to engineering orgs. Some things will break, some things will be rediscovered by sinking more time, some things will be lost forever. But you also gain flexibility, fresh direction and the ability to move forward. When you work at a company for 20 years, you may be valuable when it comes to things that are done “the company way” but are also partially blind to how the industry has moved forward in those 20 years.
Microsoft is a services company with engineering roots. That can be a dangerous combination in the long run if they forget where their bread is buttered. I would hope the Windows 11 backlash serves as a warning that they can’t just ignore their customers in pursuit of a vision.
Yeah domain knowledge is expensive. Can you imagine how much it would cost to run a business where everyone knows the ins and outs of all of the customer use cases?
There might be these wizards, but probably most of them are dudes who were attached to something successful 15 years ago and have been riding out their time at an inflated level.
