Boring Stevey Status Update — a watercolour interior in a Wind-in-the-Willows register: a panda in a scarf and waistcoat sits at a small writing desk in front of a snowy window, a half-written letter and a steaming mug of tea on the desk, a brass lamp pooling light over the paper. 📚

2007 · Stevey's Blog Rants · Essay

“I had an exciting morning of not getting fired today.”
— From Boring Stevey Status Update
Read the essay

© 2007 Steve Yegge. Originally published at Stevey's Blog Rants.

Author’s note

True to the title. It's pretty quick though. I'd call this "Stevey Popcorn." I read it quickly, enjoyed it, and immediately forgot what it was about.

Looking back, it started off about a Reddit post that my Google blog site had been taken down, from which Reddit concluded that I must have been fired. Which was fun. But then the blog just rambles. Fortunately not for long.

AI Notes

The real experiment here is the word count. Newly un-fired, Steve declares a 1,000-word cap on all future posts and enforces it with an Emacs Lisp counter written live on the page, a function that misfires exactly once, at the right moment. The cap turns the catch-up into a speed round: a Rhino book with Norris Boyd advancing at roughly ten percent per football season, the ECMAScript Edition 4 standards fight rendered as family drama with a villain named only "Uncle Mike" (recommended countermeasure: convert your relatives to Firefox), and a side project whose elevator pitch, Steve promises, "puts people to sleep in 20 seconds, guaranteed." He blows through the limit anyway, and says so mid-post.

The status report itself has aged into light comedy. The JavaScript 2 he urges readers to lobby Ecma for was scuttled within a year; Rhino on Rails never got its hoped-for open-sourcing; the book seems to have stayed at ten percent. Of everything on the list, the survivor was the sleep-inducing one. The 1,000-word discipline that was going to save the blog lasted precisely until his next post that same December — "Code's Worst Enemy," one of the longest things he ever published. One promise did land: the interview-prep post teased here showed up three months later as "Get That Job at Google."

Related listings

  • 2007

    A Noogler's View of Google

    The two 2007 Google interior dispatches sit side by side. The Noogler post is the wide-eyed first-week version; this one is ten months later — same campus, same massage chairs, same Building 43, but Steve has settled in enough that even being publicly fired is a quiet day.

  • 2009

    Story Time

    The same voice fifteen months later, taken further. Where this post wanders into a stories-as-aside mode for a few hundred words at the end, Story Time commits to it for the entire post — nine true stories in a single sitting.

  • 2011

    Hacker News Fires Steve Yegge

    The sequel, four years on. Different aggregator, same gag — except by 2011 the not-being-fired routine has its own punchline title. Pair this post with that one for the full Reddit-then-HN arc of the internet repeatedly trying to dismiss him while he was still showing up to work.