In all honesty, all my professional development these days might have me testing locally on Windows, but deployment is almost universally to a Linux server. Doesn’t matter what it is, deployment is almost always to a Linux server*. Desktop software is a niche development category these days, and even mobile development is pretty niche (though it still seems to be a lucrative niche professionally). So little development needs to be done ON Windows these days (and a lot of development is actually HARDER to do on Windows vs something UNIX based). And even then, you can just use remote desktop and connect to whatever platform you need (my work issued laptop is running Windows 11, but it really just is a thin client and web browser, I don’t even have file system access for security reasons, and the computers at the office are literal thin clients**).
I’m really not sure what work, if any, truly needs WinTel anymore (other than vendor lock in workflows dependent on VBA or on Office itself). Well, okay, game development probably still heavily relies on WinTel, but, outside of PC Master Race sorts, most people running WinTel are either running browser based apps, Microsoft Office (or VBA dependent workflows), or writing desktop software for Windows. Anymore, PCs are either for computer gaming or are merely thin clients. I’m sure that horrifies Microsoft, but even they are adapting (.NET is now multiplatform, after all).
* Well, okay, there was that ancient VBA automation system I had to maintain on an earlier project, and that was Windows exclusive. But even on that project, I also pushed Python to Linux servers.
** Granted, thin clients running Windows 10 on x86, but still literal thin clients.