Irreal

Juan Manuel Tirado is a programmer who decided to write a book on Go. I’m not a Go programmer so I can’t comment intelligently on the book other than to bring it to your attention. What I can comment on is his post Writing a Programming Book in 2021.

If you’re thinking about writing a book, Tirado’s post is mostly good advice. I don’t agree with everything he says but, of course, every writer is different and it would be surprising if we agreed on every aspect of the writing process. To me, the oddest thing about his post is that he thinks writing a programming book in 2021 could be considered weird and feels the need to justify his writing it. As far as I’m concerned, a good book needs no justification. Those who are interested will read it. Those who aren’t are free to ignore it.

Tirado chose to self publish with Amazon. That’s a reasonable solution but puts a heavy burden on the author. It’s hard to overstate how much work a traditional publisher does to get your book into print. There’s copy editing, cover design, marketing and a host of other services they perform. On the other hand, self publishing puts you in charge. You make all the decisions.

His My recommendations section will probably be the most useful. Tirado found that spending a lot of time of the Table of Contents and then following it when writing was important. I’m more inclined to write the chapters out of order and settle on the ToC when the book is complete. Do whatever feels right for you.

All in all, his advice is worth reading and considering. If you’re interested in writing a book, take a look.

A few years ago I used to joke that I was getting in touch with my inner teenager when I texted with SMS. These days, I text more often than I send email and Apple’s iMessage makes it easy to text from any of my devices.

One way that email is superior to texting is that it’s easier to send messages without typos or mistakes. My texts often have mistakes. About half the time that’s because autocorrection thought it knew what I meant better than I did. The other times it’s because it’s harder to type accurately on an iPhone or even an iPad.

Whatever the cause of the errors, I’ve often wished that I could edit a text after it was sent. People have evolved a number of ways of dealing with this. One popular method sends the corrected word with a * prepended. That’s too ambiguous for me so I use the ed substitution notation s/xxx/yyy/. That’s pretty much a standard notation in the programming world—Sed, Vim, and Perl all use it—so it’s well understood by all my technical interlocutors but, oddly, even my non-technical friends and relatives have no problem understanding it.

Wil Shipley has an interesting idea: build a text correction protocol on top of the ed/Perl/Sed commands. His idea is that email clients supporting the protocol would allow the sender to edit the erroneous text, which would, in turn, send the appropriate Sed command to the receiver’s client. The receiver’s client would redisplay the text in its corrected form along with an indication that it’s been corrected. The old, erroneous, text would be viewable by clicking on the corrected indicator.

The beauty of this solution is that it has a soft fallback for nonconformant email clients. On the receiver’s end it would simply keep displaying the original message followed by the Sed command. In other words, just what I and many others are doing now. If the sender doesn’t have a conformant client, they can simply send the Sed command manually—again, what many us are already doing—and the user of a conformant receiver will see it displayed as a corrected message.

This is a great idea and should be fairly easy to implement without unduly impacting current clients. I hope one of the big players picks it up and runs with it. As Shipley says, once one vendor implements it, the others will follow.

Public health officials have seriously damaged their credibility with COVID-19 messaging. Many of the things they’ve told us have turned out not to be true. Some, such as their early advice on mask wearing, was a transparent lie that didn’t make sense even on its own terms. If you lie to me once, why should I believe anything else you tell me?

Now that we have a vaccine and the end of the epidemic seems in sight, it seems like a good time to ask where the virus came from. The received wisdom is that it came from bats via the Wuhan wet market. According to this theory, the virus made the jump from bats to an intermediate species, and then to humans. That’s how the SARS1 and MERS viruses did it. This theory is the one championed by the virologist community and some other public officials. And who should know better? Unfortunately, there are several problems with this theory.

The other major contending theory is that the virus escaped from the Wuhan Institute of Virology that was doing gain of function experiments on coronaviruses. That theory was immediately and emphatically disparaged by the virology community, most public heath authorities, and the press even though such leaks are frighteningly common. No evidence was adduced to justify this dismissal. Instead, they authorities simply said it was ridiculous and a conspiracy theory.

If you have a scientific or even a skeptical bent, these denials should be raising a red flag. They don’t sound scientific, they sound political. Irreal doesn’t take any position on the matter because, like most of you, I don’t have the domain knowledge to make an informed decision. Fortunately, Nicholas Wade has a careful and exhaustive article that considers the evidence. The TL;DR is that there’s no definitive evidence either way but that what there is argues heavily for a leak from Wuhan labs.

Wade’s articles seems to me an honest recitation of the facts. It doesn’t reach a firm conclusion but provides sufficient evidence for you to draw your own.