You know why browsers sprouted tabs? Because the DEs never handled multiple instances nicely. Great to see MS is regressing in this area.
A DE is what, now?
Shenanigans on Microsoft Feedback Hub
131–140 of 231 posts
Re: Shenanigans on Microsoft Feedback Hub
#132I once even spotted a Microsoft employee who took the time to raise their concerns on the public tracker: That is just incredibly exasperating to see. When even MS employees are being forced to "bend over and take it", you'd think there would be some sort of "find the people responsible for this shitshow in the Windows team inside MS, and keep emailing them to fix it" protest. That one employee he noticed seemed to h…
Re: Shenanigans on Microsoft Feedback Hub
#133Former MSFTy, don’t bother wasting your time giving feedback. Nobody cares, those that cared left. Microsoft has a weird culture, very top down, very passive aggressive between departments. For a brief while I would diligently prepare bugs for the dog food software. I would even walk over to visit people responsible for it and chat about it. Even for software where ‘zero bugs’ was important they’d just delete a whole…
The open-source equivalent of this behaviour is "stale bots" that close or lock issues with no activity. Or "moving discussion to a separate tracker", with all bugs getting closed and a polite request to re-open them. Or a "locking bugs older than X months, please open a new one if still applicable".
Sure, opening it again isn't a big deal. Re-opening all bugs ever opened by all humans is just pointless work for no obvious benefit.
Having zero open issues should never be a goal, any mature project has open issues. Trying to reach zero is chasing a number that won't make a product better; it's just a number.
Re: Shenanigans on Microsoft Feedback Hub
#134But no.
During the last year, a Microsoft PM called Gloridel Morales has thoroughly gone through hundreds of Developer Community suggestion for Azure Devops, and closed each and every one of them. Quite rudely. Just check out each and every link in [0]
Some were suggestion from fellow Microsoft people.
She did it using the following eyebrow-raising text, quoted below, suggesting either that Gloridel Morales and her team have no idea how to manage themselves by prioritizing a backlog of requests, or that her paycheck/review depends on having a clean backlog.
Thank you for taking the time to share your feature suggestion. Due to the high volume of suggestions in our queue, we are not able to respond personally to every suggestion. As a result, we depend on the community to validate the request via votes and comments. Suggestions that the community doesn't prioritize, we close out in order to maintain a manageable list of suggestions. It is our policy to close suggestions that are inactive in the community based on no change to customer comments or votes in the last 90+ days. We love your enthusiasm for our product and hope you will continue submitting ideas for the community to validate. [1]
That's just one example, it's the same for almost all requests in [0].The bit about "suggestions that are inactive for 90 days" might have looked good on Github with its somewhat primitive but sensible community around issue discussions, but the developercommunity site is inundated with garbage issues, making it almost impossible to search for proper issues.
That's just for Azure though. I must say that a couple of bugs I opened there for the Microsoft C++ compiler actually got prioritized and fixed in the last couple of years. Others were ignored.
[0] https://www.google.com/search?q=+Gloridel+Morales+%5BMSFT%5D...
[1] https://developercommunity.visualstudio.com/t/add-previous-b...
Re: Shenanigans on Microsoft Feedback Hub
#135Former MSFTy, don’t bother wasting your time giving feedback. Nobody cares, those that cared left. Microsoft has a weird culture, very top down, very passive aggressive between departments. For a brief while I would diligently prepare bugs for the dog food software. I would even walk over to visit people responsible for it and chat about it. Even for software where ‘zero bugs’ was important they’d just delete a whole…
I would rather have a bug report basically ignored than actually modified. There is a big difference between ignored and modified because it speaks to not only we are going to ignore this but no one will respect the content of the forum. I remember when an admin for reddit changed a bunch of comments and it was controversial when he did it an they introduced a policy that would disallow engineers to have that kind of…
Re: Shenanigans on Microsoft Feedback Hub
#136Earlier quoted context omitted.
VS Code and GitHub will hard carry Azure if need be
Shouldn't that be the other way around? What good is it for a company if the only products people end up using are the ones given for free? I'm sure other software companies faced similar fates (no one paying for services, only using freely available services) but I can't think of any ATM.
I think Facebook helps answer that question a bit: just because someone is a user doesn't mean they're not the product.
Giving out one product if it helps other ulterior motives is still profit. Vertical integration also plays a part in this. Especially if the paid product re-invents something in a non-standard way, and then the free product only supports than.
Re: Shenanigans on Microsoft Feedback Hub
#137Former MSFTy, don’t bother wasting your time giving feedback. Nobody cares, those that cared left. Microsoft has a weird culture, very top down, very passive aggressive between departments. For a brief while I would diligently prepare bugs for the dog food software. I would even walk over to visit people responsible for it and chat about it. Even for software where ‘zero bugs’ was important they’d just delete a whole…
> Even for software where ‘zero bugs’ was important they’d just delete a whole bunch of bugs and see if any bounce (come back). Eventually people get sick of refilling so they get to zero but bounce by exhausting the very people eying time help them. The open-source equivalent of this behaviour is "stale bots" that close or lock issues with no activity. Or "moving discussion to a separate tracker", with all bugs gett…
Re: Shenanigans on Microsoft Feedback Hub
#138Former MSFTy, don’t bother wasting your time giving feedback. Nobody cares, those that cared left. Microsoft has a weird culture, very top down, very passive aggressive between departments. For a brief while I would diligently prepare bugs for the dog food software. I would even walk over to visit people responsible for it and chat about it. Even for software where ‘zero bugs’ was important they’d just delete a whole…
> Even for software where ‘zero bugs’ was important they’d just delete a whole bunch of bugs and see if any bounce (come back). Eventually people get sick of refilling so they get to zero but bounce by exhausting the very people eying time help them. The open-source equivalent of this behaviour is "stale bots" that close or lock issues with no activity. Or "moving discussion to a separate tracker", with all bugs gett…
Re: Shenanigans on Microsoft Feedback Hub
#139> W11 taskbar is missing several key pieces of functionality which have incentivised new users to get into Feedback Hub and cast votes. By far the biggest and most controversial submission is about having multiple documents open in the same app. Actually the same reason for me to give feedback during W11 beta. Liked the beta as it gave me access to WSLg, but the productivity loss of the taskbar being useless made me…
Re: Shenanigans on Microsoft Feedback Hub
#140Earlier quoted context omitted.
> Even for software where ‘zero bugs’ was important they’d just delete a whole bunch of bugs and see if any bounce (come back). Eventually people get sick of refilling so they get to zero but bounce by exhausting the very people eying time help them. The open-source equivalent of this behaviour is "stale bots" that close or lock issues with no activity. Or "moving discussion to a separate tracker", with all bugs gett…
Agree, but forever open issues doesn’t give any value too. Because you don’t know if this issue still applicable for latest version of app/library. I think stalled issue should be closed, especially minor one.