I’m not sure if you’re being serious here or not, but I too have a tux tattoo. I knew at the time that it wasn’t a unique idea, but I’ve never met anyone else who has one. There must be dozens of us.

Do people also ask you if it’s Pingu or something from club penguin?

From what I’ve read, it sounds like the update file that was causing the problems was entirely filled with zeros; the patched file was the same size but had data in it.

My entirely speculative theory is that the update file that they intended to deploy was okay (and possibly passed internal testing), but when it was being deployed to customers there was some error which caused the file to be written incorrectly (or somehow a blank dummy file was used). Meaning the original update could have been through testing but wasn’t what actually ended up being deployed to customers.

I also assume that it’s very difficult for them to conduct UAT given that a core part of their protection comes from being able to fix possible security issues before they are exploited. If they did extensive UAT prior to deploying updates, it would both slow down the speed with which they can fix possible issues (and therefore allow more time for malicious actors to exploit them), but also provide time for malicious parties to update their attacks in response to the upcoming changes, which may become public knowledge when they are released for UAT.

There’s also just an issue of scale; they apparently regularly release several updates like this per day, so I’m not sure how UAT testing could even be conducted at that pace. Granted I’ve only ever personally involved with UAT for applications that had quarterly (major) updates, so there might be ways to get it done several times a day that I’m not aware of.

None of that is to take away from the fact that this was an enormous cock up, and that whatever processes they have in place are clearly not sufficient. I completely agree that whatever they do for testing these updates has failed in a monumental way. My work was relatively unaffected by this, but I imagine there are lots of angry customers who are rightly demanding answers for how exactly this happened, and how they intend to avoid something like this happening again.

I know you’re joking, but having a seperate phone exclusively for work stuff is actually great, specifically because it makes it easier to entirely seperate yourself from work. At my old job, I was given a work phone and it was the only phone number I used for all my work stuff. When I was at work, I would answer it, and outside of that it was off or on silent in my work bag. If they wanted me to answer outside of work hours, they had to pay me on-call rates. The same thing applied to group chats and other work-related stuff like that, (e.g. emails). It all went to that phone, and unless I was being paid to be contactable outside of work hours, I wouldn’t be.

The only exception to that was my manager and a select few people who had my personal number for genuine emergencies, and if they used my personal number to contact me asking me about work, it was entirely at my discretion to respond and would mean I’d get on-call pay.

It also meant I could keep my work and personal accounts/apps/etc. completely seperate. If they asked me to download some random app, I could do it on the work phone without worrying about whether they would be able to access other data on my phone or anything like that. Whenever I needed a phone number for 2FA or whatever, I could use the work number and not worry about where exactly that number would end up or how it might be used. For example, I used my work number to register for a conference, and then for months afterwards I would get calls and texts from sales people. That was still slightly annoying, but it was much better than getting calls on my personal phone.

It also meant that when I left that job, I could just wipe that phone without having to worry about having personal data on there, because I never used it for anything except work stuff.

It does sound like Microsoft is asking their employees to pay for an iPhone which is a bit dodgy in my opinion, but I’d still probably take the opportunity to use it completely for work and keep my personal phone seperate. It’s easy enough to get another number, and then when you leave that job you can cancel it and get a new number for the next job, cutting that link entirely.

In the article it says they’re cancelling the “pro” version to focus on producing a cheaper version. So it sounds like you might get what you want, although “cheaper” will still likely be very expensive, and your point about compatibility with non-Apple devices still holds.

It looks suspiciously like a pay-for-award company that gives out awards to just about any product for parents/educators/related to children or parenting, as long as you pay the “application fee” (although they specifically say an award isn’t guaranteed).

I mean looking at their website they seem to give out an awful lot of awards, and they mention that for $500, you’ll get to use their award seal on your product and receive 100 award stickers, and for $1,500 you get more stickers, plus they’ll post about your product on their website.

Call me crazy, but I’d think that if an award isn’t guaranteed, they’d make you pay for the initial application to start with, and then (assuming you “win” an award) they’d offer to promote your product for an additional payment, once they’ve decided that you’re eligible. The fact that they talk so openly about how paying a larger application fee gets you promoted on their site (and some other stuff) makes it seem suspiciously like a pay-for-award scheme to me.

Well that’s clearly because parachutes aren’t effective at reducing the likelihood of causing serious injuries or death. There’s even a randomised controlled trial published in the BMJ that says so: https://www.bmj.com/content/363/bmj.k5094