Both my parents were teachers so I thought I had some idea, but it wasn't until I ventured into the middle school to assist a teacher with a coding class (probably this was 10 years ago now) that I learned something about education.
This must be the original "mac vs Windows" divide: I could never get my head around HP calculators. TI all the way. SR-52, TI-59/58. Sinclair if budget was tight. That said, I do have an HP-85C...
I've used surfaces of various kinds for more than 10 years. Overall they've been significantly less troublesome than the laptops from other major brands I've had over the same period. I put this down to the dogfood eating nature of the Surface. Whoever is responsible for the sound interface driver in a Dell laptop is unlikely to be a user of that laptop and even less likely to have the capability to get Dell to ship a fixed version. Microsoft however I suspect uses Surfacen extensively in house. In this respect it makes the Surface products more akin to Apple computers. The same is probably true for high end Chromebooks. I never used a dock, fwiw.
A (quite large) company that I worked for stopped offering surfaces to employees after the average lifetime over the 3 years they offered them was under 1 year. We even had a terrible batch of Dells at the same time that still handily outlived the surfaces.
Small sample size (N=3) but, nobody I know that works at Microsoft uses a surface or any other Microsoft branded laptop.
> Whoever is responsible for the sound interface driver in a Dell laptop is unlikely to be a user of that laptop and even less likely to have the capability to get Dell to ship a fixed version
Oh boy, don't get me started on Dell haha. Sure, they've got a better service model (people come to you), but at least in my experience they contract with service people who service multiple brands who can't help but shit-talk Dell. Not very confidence inspiring, particularly when the cause of the issue ends up being a connector not being fully plugged in from the factory.
I have never used any of the Surface products but I do remember how people liked the almost no questions asked replacement policy for them at the Microsoft stores. I knew a guy that worked there and he said it was an all day occurrence.
I think the general idea that your supply chain should be rooted in source repositories and associated commit hashes is the right one. Tooling can be made to automate the process of putting together a product from those defined sources. Some languages/systems already have some support for this. E.g. Golang and Rust. The concept of a "binary" artifact is really dead now everyone uses git and builds are quick. It lives on in things like npm and docker hub but we don't actually need it.
reply