Two technical editors worked with me on Going Offline.
Jake was one of the tech editors. He literally (co-)wrote the spec on service workers. There ain’t nuthin’ he don’t know about the code involved. His job was to catch any technical inaccuracies in my writing.
I deliberately didn’t wait until I was an expert in this topic before writing Going Offline. I knew that the more familiar I became with the ins-and-outs of getting a service worker up and running, the harder it would be for me to remember what it was like not to know that stuff. I figured the best way to avoid the curse of knowledge would be not to accrue too much of it. But then once I started researching and writing, I inevitably became more au fait with the topic. I had to try to battle against that, trying to keep a beginner’s mind.
My watchword was this great piece of advice from Codebar:
Assume that anyone you’re teaching has no knowledge but infinite intelligence.
It was tricky. I’m still not sure if I managed to pull off the balancing act, although early reports are very, very encouraging. You’ll be able to judge for yourself soon enough. The book is shipping at the start of next week. Get your order in now.
“Technical balance”adactio.com/journal/13747 This book is sounding more and more like a must-read for all web developers.
“Assume that anyone you’re teaching has no knowledge but infinite intelligence.” adactio.com/journal/13747
“Why I had two technical editors working with me on Going Offline, with opposite levels of experience.” How Jeremy Keith avoided the “curse of knowledge” while writing his latest book. adactio.com/journal/13747
Technical balance adactio.com/journal/13747 I struggle with this on every single LinkedIn Learning course I author and still don’t get it correct often enough.
RT robweychert: “Assume that anyone you’re teaching has no knowledge but infinite intelligence.” adactio.com/journal/13747
Technical balance adactio.com/journal/13747
I think you’ve got a sale. Thanks for the reply.