Five for Friday – November 8, 2019

For the last day or so, I’ve been thinking a lot about programming and testing, about collaboration and walls, and about where this may all be going. This post is the start of my mental exploration of the subject. In the beginning… In How We Test Software at Microsoft, we told the story of Microsoft…

What a difference a decade makes. Amazon tells me that Dec. 10, 2008, is the release day of How We Test Software at Microsoft. Before I reflect on the content, take a look at this photo from the back cover: Or this one from a few months later at Barnes & Noble: I’ve aged (at…

After my last post, I thought I was done commenting on stack ranking (for at least another year), but two things inspired me to write just a bit more. First, a few people flat-out asked about my opinions for alternatives; and secondly, a consultant added some ignorance to the discussion that gave me just enough…

I took an internal training course last week where we heard lectures from a bunch of MS execs (I don’t do it justice – it was far more interesting than I anticipated and something I’d do again in a heartbeat). Anyway, one of the lecturers was talking about software markets and showed a diagram that…

Earlier this month, I spent a week in beautiful Copenhagen at what’s called a R&D Training week. The goal is that every new Unity engineer spends a week at the Copenhagen office, learning about the systems we use, and about engineering at Unity. Granted, since I’m on the services side, a big chunk of the…

A long time ago (for most of us), we built products over a long period of time, and hoped that customers liked what we built. It was important to give them all of the features they may need, as we wouldn’t be able to get them new features until the next release, which was usually at…