Microsoft
Microsofti have organized all of my chatgpt chats in the last couple of years, and i have realized that 80% of the tech chats i have are about Microsoft and its services, no matter if you write a guide of recurring jobs or if you lose days to configure scripts or little apps, all the things you do will become obsolete really fast and you must re-waste time trying to understand what you have to do to re-do something you did already.
you change names, frontends, powershells, all the times there's something new and most of the time is just an useless change that brings new problems, remove features, or just make things more difficult. and while this changes are on the way (preview) you can still access the old pages jumping in and out from the old and new interfaces making things even more difficult.
I can still acces the old MFA page in exchange even if it's not working since 2 versions already, i mean there have been already 2 changes in mfa procedures and still the old not-functional page is still alive.
this is just an example.
You should keep and improve living services instead of killing them, and when you drop a command in powershell you should point to the alternative and provide guides for replacements.
you change your mind more quickly than my 13 years old daugther.
all of the MS things looks like an eternal WIP/beta
Sad but true. What's more, no "replacement" ever gets feature-complete so it can actually replace something. One reason for this is before it is finished, there is an even newer (again incomplete) replacement, so the earlier iteration gets it's development halted. That is why we still have things like mmc consoles for managing active directory, that are literally 20 years old, or Windows XP control panel controls in Windows 11. The mess just gets bigger and bigger.
This guy knows it.
chaloemkhompitoon
