Trying to emulate Gassée, my team and peers, knowing my true nature, thought I had gone insane.
I continued to read his opinions. http://www.mondaynote.com Agree or disagree, I appreciate his heterodoxy, challenging my own assumptions and views.
Guy Kawasaki, not so much.
What characteristics from Gassée did you try to emulate in vain?
What do you dislike about Kawasaki?
Rereading just now, I'm amused that was the only Gassée lesson I remembered.
I like Kawasaki just fine. The followups I'd read didn't really land like Macintosh Way did. But I see now that he kept writing, all of which are rated highly. So I retract my judgement. YMMV.
For anyone interested, here's the demo in question: https://youtu.be/1tQ5XwvjPmA
How well does that scale to modern Apple? Do they retain 140,000+ employees, each one expecting the world to revolve around them?
I'm sure there are groups within Apple that think the rest of the company revolves around them, as there are in most companies.
I admired Kawasaki, but I don't think he had that much clout at Apple. This was the part that Apple never got. Indeed, not too many years later, Apple announced to the business press that they were going to de-emphasize engineering applications and focus on their core strengths in the arts and education.
I remember an article by Kawasaki proclaiming that the Mac was going to be the go-to platform for an emerging field called Embedded Systems. Virtually no embedded systems tooling was ever developed for the Mac. I created Mac hardware by programming it on an MS-DOS machine. I'm grateful that MacOS and MS-DOS let me bypass the Windows 3.1 era.
I am not sure that Windows was any better, but Windows allowed dropping back to MS-DOS mode and creating ugly-but-works tooling. Then Visual Basic came along and made it easy. And today, anything I'm like to do with "the engine" will preferably involve Linux.
But wow did a lot of systems get developed in it. Microsoft still haven't got a decent replacement for it and nobody else does either.
HC allowed "code resources" to be added, like plug-ins, which I wrote in Pascal or C. That's how I created drivers. It gave me the performance benefit of course, while allowing me to deal with just the tiny bits of the OS needed to deal with my hardware.
The hardware was either homemade (microcontroller programmed on a MS-DOS machine), or plug-in boards made by National Instruments that luckily came with a C API.
While the term "jailbreaking" was introduced for the iPhpne, the concept was already familiar to me.
An odd irony is that the stuff I've worked on over the years has always involved relatively slow processes, so I've been able to live with the performance tradeoffs of "easy" programming tools.
Think of it as an early version of LabVIEW.