Today there's lots of old code from the era before automated tests were widespread in the industry, and often automated tests which were previously maintained by the testers are now bitrotting. The culture of testing is not strong among developers in some parts of the company. The beta program can't catch everything either.

So telemetry it is.

And you need some telemetry. Minidumps/coredumps make debugging certain kinds of crashes much easier, and Apple captures that sort of data too. And I guess seeing whether people use some widget in Office a lot/not at all could be useful for improving the product. In practice it also leads to issues with the GDPR and governments, which MS does ultimately fix.

Apparently Win10 Enterprise users have a switch somewhere where they can turn off almost all telemetry, but not so for Home and Pro users, say what you will about that.

I was at a company that did the same (at roughly the same time) - this was a terrible mistake. But it's very hard to discuss, because any dev complaining sounds like they want to avoid testing.

Dear manager that I hope reads this:

QAs, at least the ones under discussion, aren't just mindless pressers-of-buttons. They have a skillset and domain knowledge just like (but distinct from) devs. A dev should absolutely test their own code...but they will do so with their domain knowledge which will be by definition more limited than someone for whom such knowledge is a key part of the job. Devs should test so that only problems worthy of the QA skillset make it to the QAs.

Asking devs to do QA work is asking them to build skills that are not their strength, and that will come at the cost of their strengths. It is asking them to build skills they probably don't enjoy, and that will come at the cost of their job satisfaction. Having devs do QA work is as bad as devs that test nothing and leave it all for the QAs - it's an inefficient and ineffective use of resources and time.

There is nothing wrong with encouraging Devs to deliver higher quality code to the QA/Test engs. There IS something wrong with thinking higher quality code from devs mean you don't need a QA/Test Eng.

In either case, it's also like cutting off your left arm because you still have your right arm.

My experience is across three different companies now, and in the first two (not my current employer who... still do it wrong but it's the best I've seen), they fired the Ops guys and expected the Systems Engineers\Software Engineers to take those roles.

No overtime pay in either company for the extra work load that was placed on them (e.g. me) of course. So the only cost the companies incurred was productivity and the quality of work. The burden was entirely carried by the staff and to a greater degree the clients who accept a shoddier product and service.

Fortunately I quit both jobs to get to where I am now, though the old timers no doubt are still working ridiculous hours and are too scared to ask them selves "can I find better else where?".

Long term, doctors aren’t nurses and patients suffer. Eventually someone dies.

This ignores that it discards specialisation, not merely quantity, and that testers are generally cheaper than developers.

And then QA does their good job and gets hate for saying that accidental nuclear genocide [or whatever] might be a bad thing so let's fix that before release to the customer.

Sure, "code to spec and you're done". But are you actually really done? Are you sure?

> ... Devs are expected to test their own code now

I'll never understand this line of thinking. A good tester doesn't think the way a good developer does. It's a different but equal and necessary skill in order to provide a strong product.

Not only messy, but also quite deadly.

And messy.

I don't know how Apple does it, but crash reporters have been around for a long time (Netscape had one!) and would always ask you if you wanted to send a crash report.

Then you have products like SCCM that are now forever beta, and they play games with release cycles so that you literally have about a 3 week period to report substantial bugs and get a fix. Before that, the product isn’t generally available. (You need to use “pre-release” to keep up with the quarterly updates) After that, you’ll be told that it’s too late in the cycle to fix bugs, because they won’t be fixed until after the support cycle ends.

- B2B is a large part of their income, telemetry has probably damaged their reputation as a business vendor.

- They have mostly failed at social media (except LinkedIn and Skype, which they have bought). So, there is no strong need for them to collect all this data to profit off (otherwise free) social media.

- They have a strong developer story with WSL, Azure, etc. They could have replaced Apple as the darling of developers. But not with telemetry, start menu ads, etc.

- At least in the EU, more privacy is where the puck is going. They could take on Google's weaknesses.

Ironically, it's Europe where privacy championing Apple is way less of a player than Google when it comes to smartphones and services, especially compared to the US market.

So I'm not sure if a privacy conscious approach would buy them much in the EU, at least among consumers.

Overall, I would say consumers' privacy-sensitivity in Europe expresses itself largely in the increased usage of Telegram, Tor, Firefox, and Linux compared to the US.

That's partly because Apple's rhetoric is not always matched by the practical realities of its devices and services. Are they better than Google/Android? Sure, by a long way. Are they actually good? Different question.

For example, assume that you do not wish to transfer any data to or from your Apple device via any third party online system, including Apple's own iCloud, at least not unless it is fully end-to-end encrypted and there is no realistic possibility of the external system reading the data. Instead you prefer to keep everything local, for example connecting to another device over your local network or directly using one of the secure wireless mechanisms. This should be an entry-level requirement for any genuinely privacy-focussed system, yet to this day Apple's lock-in effects and the lack of end-to-end encryption for many types of data using iCloud are in direct conflict with achieving that most basic of privacy requirements.

Apple has only just introduced the ability to transfer everything from one iPhone to another directly. You still infamously can't transfer many common data sets onto or off those phones through standard protocols, and Apple's proprietary software seems to have a poor track record, again pushing users towards iCloud.

If the particular app you have in mind doesn't support that feature (most of the ones I use do), that's not Apple's fault.

And the fact that Apple's entire system uses a proprietary storage scheme and doesn't support standard protocols other than for a few specific cases like photos clearly is a decision that Apple has deliberately made.

IME, wirelessly iTunes can be flaky, though better than in the past. My direct personal experience is that if you use a wire, as stated, it's flawless.

Originally iMessage was supposed to be opened up for third parties but that never happened for some reason.

Isn't that mostly explained by the fact that EUR prices have VAT included (typically 20%) and US prices do not?

Even things like the giant Console rewrite and WSL apparently owe just as much to telemetry meriting their resources as the (return) of Azure and DevDiv's "developer-first focus" to Windows (after all these years).

(A fun irony of the "Start Menu debacle" to which you refer was more of a sample size problem than a telemetry problem. With Windows Vista-8 keeping telemetry primarily opt-in, they mostly only had interesting subsets of newbie/casual users that clicked yes during setup and power users with vested telemetry interests. Newbie/casual users tend to launch apps "Search only" or "Desktop only" keeping all their shortcuts on the desktop. Power Users tend to use alternate launchers or become increasingly "Search only" over time, especially if you count Win+R old timers, which Windows did. Microsoft had a good argument that trying to make the telemetry opt-out would avoid such biased sample sets going forward.)

I'm used to this on web and mobile - because arguably their apps are their private property which I'm using, but there's something incredibly uncomfortable about my operating system running an experiment on me. I get that Windows is also Microsoft's property, but it's the lowest level in the stack, which makes my hardware more theirs than mine if they're able to do what they want with it.

I'm not even against telemetry as long as it's transparent.

Maybe I'll go back to Linux soon.

The biggest/wildest example that was A/B tested to date was Sets. Sets was a feature/system where nearly every window in Windows was heterogeneous tab-capable. (Illustrative example: Open a Word document, add a tab for some OneNote notes, add a browser tab for some research. Save it all as a Set to the Windows Timeline as Set, open it all back up at once.) But ultimately Sets never made the cut out of testing (too many compatibility issues, not enough telemetry usage, too confusing a UX sometimes, not enough apps in the wild with Windows Timeline support, etc) and it sounds like the project is now dead.

(Supposedly it was partly dropped too because apparently they were piggy backing on Edge's UWP tab control and with Edge going "Edgmium" that tab control was considered less critical infrastructure to any team and less of an "in-box" control to piggy back off of. Microsoft Terminal got a version of the UWP tab control pushed out into the open source UWP control toolkit, but probably not in time to be reconsidered as an in-box control for Windows.)

(I was sad I never ended up in the group with Sets turned on. I wanted to play with it.)

(ETA: Also, I really hope as Edgmium gets closer to launch it uses a XAML Island to pick back up the UWP tab control where possible. That would be one great way to feel a bit more Edge and a bit less Chrome knock-off.)

They fail to understand that "Be Like Facebook" is not a positive aphorism or outcome.

Office has sent documents in crash dumps up to Microsoft for a long time. None of the hand wavy security guys say much about it, because it isn’t an audit finding.

Hardly, from my perspective, but do you have sources for that claim, or for Apple formerly being the "darling" for that matter?

Much much bigger than Apple by having much much more marketshare of everything except smartphones.

Don't their Enterprise and business editions of windows omit all the telemetry?