Skip to main content

Restored

Back on September 30, 2013 I decided to take a break from blogging and mothballed my site. Today I've restored everything.

In the intervening time I've been pretty busy with...

1. Writing a ton of blog posts for CloudFlare (and doing all the actual work that goes into those blog posts). In particular, the posts about the OpenSSL Heartbleed bug involved a lot of work.

2. Speaking at various events including Codebits in Lisbon;  GopherCon in Denver; a Many-to-Many in London; Secure 2013 in Warsaw, Virus Bulletin 2013 in Berlin and Yandex YaC in Moscow. There was also a day trip to Paris for a private conference in there somewhere.

Here's my talk from GopherCon:



3. Working on small projects like a bike light that flashes in Morse Code, a Missile Commander Switch, and an Arduino-powered Hallowe'en lantern and releasing new versions of the GNU Make Standard Library.

4. Discovering that the one true way in the gym is the way of the barbell.

Some upcoming things:

1. A revision of GNU Make Unleashed is underway to bring it up to date with GNU Make 3.82 and 4.0 and add chapters covering new topics that readers have asked me about.

2. I'll be speaking at ICANN 50Wired 2014 and dotGo 2014 later this year.

3. Plan 28 continues (despite the lack of updates to the web site) and actual work started on intepreting Babbage's Hardware Description Language on June 1. We'll blog about that.

4. Lots of exciting things at CloudFlare that I wish I could blog about today.

And, finally, I might get back to blogging here as well.



Comments

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of