why it is hard to publish a book with zero errata

As Scott and are finishing up on Z0-815 book, I want to share an example of an error’s progress through the editing process.

We have a method. Pay careful attention to the name of the method:

public void requiresAssistance() { }

Then we reference the method: new MoreHelp().requireAssistance();.It’s an error. Let’s see what happens to it as the editing process proceeds:

  • Scott and I read each other’s chapter.
  • Our Tech Editor reads the Word document and runs all the examples. In theory it should get caught here. And most things do. But I’ve tech edited. There’s a lot to see and a ton of detail.
  • We reply to our tech editors comments.
  • The book gets turned into a PDF.
  • Our Tech Proofer reads the PDF. Excellent it got caught at this phase.
  • We submitted the request to change “requireAssistance” to “requiresAssistance”. Scott and I proofread each other’s change requests to ensure we don’t introduce more errors.
  • We got the final PDF back for review. (I’m not sure if this is part of the process, but we ask for them anyway). It says “requiresAssistence”.

We submitted a request to get this fixed before the book prints. But this shows how hard it is to get all the errors out of book. “Assistance” was spelled correclty in every draft and revision except the final one.

If you followed that process closely, the Tech Editor and Tech Proofer didn’t even have the opportunity to catch this. And it wasn’t created by the authors.

“resetting” docker

I tried to run “docker –version” on my Mac and it hung. That’s odd. I rebooted and same thing. After some useless fiddling, I decided to try reinstalling. Here’s what I did:

  1. Deleted /docker folder from Applications (this was the old Toolkit which I think I haven’t used in ages)
  2. Tried to delete Docker app from Applications. That failed because it was in use.
  3. Opened Activity Monitor and killed docker
  4. Actually deleted Docker app from Applications.
  5. Reinstalled Docker Desktop

While this was likely way overkill, it worked. And once I stopped fiddling, it took less than 15 minutes

Update: The next time I tried to do something, I got a prompt to accept XCode’s license agreement. That was likely the original problem causing the “hang”

the secret chromebook end of life policy

My mother is a happy Chromebook user. I’m a less than a happy Chromebook purchaser at the moment. Why you ask? Here’s my history

  • 2012 – first laptop. This was a second generation model (the first ever Chromebooks were in 2011. I waited a year to see if they would have legs. It end of life’d for security updates earlier this year (or 2018; I forget). Not bad.
  • 2014 – The first Chromebooks with built in 4G were released. I thought this would be good as she’d have 4G. It was. At first. Then we realized you have to be on wifi to get updates so I gave her an AT&T wifi hotspot instead. This computer hit end of life for updates this year. Luckily, it happened after the computer was in my possession and not hers. She wanted to replace it because computers age. No problem. Five years is a good amount of time for an inexpensive device.
  • 2019 – I picked the Acer Chromebook 15 (CB3-532). It end of life’s in August 2021. That means we only have two years before that machine can no longer get updates.
  • 2021 – I get to involuntary bug a new Chromebook.

I learned today that Google has an automatic end of life policy. It says you can’t get updates after 6.5 years from when the hardware is first released. So I only get two years of updates because the model of computer has existed for four years. I didn’t know this when I bought the machine. If I did, I would have sat there looking up the end of life dates for every model at Best Buy.

Granted the computer only costs $240. But there is a cost to setting up a new computer when you don’t live near it. One that I’d like to minimize.

Oh and the reason I was looking at the in the first place? Amazon Music is no longer working properly. I can’t tell yet if it is the war Amazon and Google are having or something more mundane.