I could write a page of the issues like this. Maybe it would not be so bad if you only used Teams but when you use slack at the same time it is like someone is wacking you in the back of the head every few minutes.
This program used an SPA. The core workflow is hidden and split over multiple "tabs". Tabs include: question, given answer, score awarded. That's right, none of those are available simultaneously. Yes, 70% of its window goes unused when full-screen.
Going through all students can be done in (at least) two ways. In the first, you can press a button to proceed to the next student, but you cannot go back a student. In the other, you click "save" after grading each answer. This returns you to the overview of students.
The overview displays 20 students per 'page' (tiny font, tiny rows), irrespective of your window size. There is no "next student" button, you have to click the student you want to grade. If you're grading past the first page (e.g., student #21): surprise! You're back on page 1. Clicking the student's tiny row requires more precision than you'll need the rest of your work week on modern desktops.
I could go on. I will, actually. Apparently, standard workflow is you can never go back to an already graded answer and points awarded become final; I accidentally used a workflow that didn't have this idiocy).
In short, there is no way this product's core functionality was tested. Any tester would have exclaimed "are you kidding me?!", and have walked out. Or inflict physical violence on their computer. Or whoever hired them.
In short: setting this product on fire is the best reason for bringing back floppies in 25 years.
So: maybe, but the back end is probably too flakey. Official recommendation is to use IE for grading and only one grader may be logged in at any time.
Really, fire is too good for this mess.
[1] https://www.lawyersgunsmoneyblog.com/2014/01/christ-i-hate-b...
Pass!
I feel like this used to work properly until a month or so ago.
The worst bug I've seen, and this is also something that only started happening in the last several months, is select messages simply not appearing! So basically I open my computer in the morning and look at Teams and it'll have messages from overnight. EXCEPT some messages did not make it, like, at all. There was a whole thread that had replies that were simply not visible to me. I even replied to that thread and on my screen the reply appeared right after the last visible message whereas for everyone else it appeared after the 40 or so messages that came in overnight.
I haven't been the only one to run into that issue either. Restarting Teams is the only thing that brought the messages back.
Now that's what I call a critical bug! Who knows how many things I've missed.
MS in particular has the habit of actually introducing small bugs like this regularly through their usual updates. It's infuriating. One day something works the next it just doesn't. I know people who never update their machine because of this. Can't blame them. Once it works, why take the chance of breaking it with updates? It it is a certainty that at some point MS will break some functionality of your system with an update. It's just a matter of time. So turning off auto update is the most sane thing to do for most people. I recommend it myself, and if you update your Chrome or Firefox automatically it is safe enough to use an unpatched Windows for most people anyway.
Once MS started introducing new bugs rather than actually fixing old ones I knew the last MS machine I will service is a gaming machine for my family. As long as that needs to run, I will make it run. All my other systems are on linux now. Once the gaming craze is over I will ceremoniously burn the Windows license key that I used, and I will never, ever, run any software from Microsoft ever again.
Except at work of course, but I don't mind getting paid to be frustrated.
HA!
I was just testing a VR app that has a Windows component when things started failing in VR. I took off my headset and noticed my test machine going through power-on self test.
"Oh crap!", I thought, "a bug caused the system to reboot".
Nope. Just Microsoft deciding it's time to apply some updates. Doesn't matter that I scheduled for a time that I wouldn't be testing.
I've NEVER been able to successfully gain control of this, despite reading up on it and doing all the recommended things.
%windir%\System32\Tasks\Microsoft\Windows\UpdateOrchestratorhttps://www.joe0.com/2019/10/17/how-to-prevent-windows-10-au...
To this day, I still am unsure if they were joking.
A day never goes by without a delight.
Edit: IBM Notes
And now the expand/collapse UI pattern with right/down arrows or triangles is standard (e.g. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/de...). Don't get me wrong, the example button is terrible UI, but an interesting example of how norms change.
On more than one occasion I have misinterpreted the upvote icon on HN to be "collapse thread".
Interactions still feel like your mouse pointer is moving through molasses. Notifications are misbehaved trash. Video calls make your CPU beg for mercy (useful if you want to fry eggs on your laptop though). Switching between multiple organisations is still miserable (although at least now you get notifications for other orgs instead of them just getting lost in the aether, never to be seen).
The funny thing is, none of these problems exist on the mobile apps, which are actually quite well-behaved. I guess that's because they have to use system APIs.
That's not my experience at all. It's not great, but it has improved a lot.
https://support.microsoft.com/en-us/office/what-s-new-in-mic...
But the basics—the things that I mentioned in my previous comment—have remained all but unaddressed for the lifetime of the product so far, and it's utterly miserable to use because of it. They're just piling new features on. I understand why, it's just frustrating.
Teams started ok, but it has become worse than Skype, which is something I didn’t think was possible.
From the company that made MSN messenger it’s hard to believe they didn’t have any lessons learned
Honestly, the best UI Microsoft ever invented were always those inside their video games. I still think AoE2 is hard to beat.
I tend to just ignore the links and download everything because of this.
A small thing, but one that would annoy me almost every day...
The issue comes from my main language being French. And in French, for some reason, there has to be a space between the word and the colon.
But in Teams, and even Outlook Web, whenever I put a space and colon to introduce a list on the line below, so I type <space><colon><enter>, I end up with a freakin' smiley, so I have to go back, delete it, and put a colon in again.
Don’t worry guys, it’s on the roadmap for this month! https://www.microsoft.com/en-us/microsoft-365/roadmap?featur...
Next maybe we can fix issue where if you have the iOS app, you randomly appear available for hours?
- Apple is the designer: I want to make everything beautiful and perfect. Sometimes that pesky messiness of reality gets in the way, but if that's the case, it's reality which should change.
- Google is the engineer: Yeah cool this project sounds good, let's replace that old technology with this new thing that will be so much better! We'll release the prototype in a month, and six months from now we'll have the whole thing done. Hmmm 4 months later, some of those details that took years to refine in the old version are actually pretty tricky, and these weird users like actually want to keep them... Yeah details are hard, let's put this project on back burner because now I'm excited about new project!
- Microsoft is the MBA: Products don't matter! They're just interchangeable widgets the grunts working below me have to concern themselves with. The important thing is what I can sell to upper management with my power-point presentation. We're data-driven, so as long as my KPI's improve, that means I have made the morally correct decision. If I can leverage or trick users into using the product the way I want, it means I'm good at my job!
This is annoying.