Ken Kocienda, the engineer who led the team that created the original iPhone keyboard and predictive text system, wrote a book titled “Creative Selection: Inside Apple’s Design Process During the Golden Age of Steve Jobs.” So there’s at least one real engineer for you who speaks highly of Jobs.

They aren’t nameless. They write books and go on podcasts, their thoughts on Jobs are available to us. Plenty of them praise Jobs for driving them to do their best work.

Jobs definitely pushed engineers to work harder than they would have otherwise.

For example he complained the first prototype iPod was too bulky. And when they said it can’t possibly be made any smaller he tossed it in a fish tank and pointed at the bubbles as proof that it could be made smaller - the prototype was full of empty space/air.

There have been some detailed stories from the engineer that invented the first small touch screen keyboard that actually worked well, as part of a larger team that worked their asses off repeatedly being told their keyboard wasn’t good enough over and over. Steve was so unhappy with the early iterations that he was going to scrap the entire iPhone project unless they could fix it on a short deadline. From the stories it was clearly an extremely stressful project, with engineers pulled off other products to try to get the keyboard to work, but they cracked it - with a complex system that algorithmically (and invisibly) adjusted the size of each key based on english language patterns.

Even that wasn’t good enough. Steve gave it the all clear to ship that keyboard but years after the release he sent them back to start over from scratch. iPhone keyboards didn’t work like that for long. The latest version uses a scaled down version of a Large Language Model (Apple calls it a “Transformer-powered” that learns not just from english (or whatever language) but also your personal typing habits.

JdW clearly thought not very much of my thoughts and someone decided the name-calling warranted a removal. That said, I’ve responded to JdW with a direct message to share some examples I’ve been part of in my time. I do believe it’s a pattern you come to recognise after 20+ years in software development.

Undertaker

Software development. I’ve been on both sides of the equation I’m describing above, many times. Looking back, a large part of the achievements I’ve been fortunate to be part of started with someone who said “we can totally do it” while we, the team, were mouthing “how the fuck are we going to do that?!”.

But you find a way, usually. That’s all I’m saying.