Status Update — FSE Blog

Status Update

The short answer to your question is on the status page (RSS feed). The TL;DR follows.

You're seeing this because you're looking at the blog, or because you asked me a question, and the question was where something is or what I'm doing or what I'm working on or when I estimate something will be done or something like that, and I sent this link in response. The intent wasn't to be terse or rude, but to save myself some time and avoid breaking focus.

Everyone that wants a status update (what is busted, what is fixed, what will be fixed, what I'm working on, when any of that is estimated to be done, etc.) can now go check the status page instead of asking me. I'm going to just give people a link to this page instead of unwinding the stack to answer that question.

Some people are interrupt-driven, and I am the other type: that shit just kills me. I can hack on things while making jokes or tossing GIFs at people or whatever, but unwinding the stack repeatedly is like putting my brain in a blender. This tends to make no sense to people that are interrupt-driven, so you'll have to either take my word for it and just check the status page when you want to know, or refuse to believe me and still just check the status page when you want to know.

I had been planning to do this for a while. I'd figured I'd go look and find something vaguely like Pivotal Tracker but not Pivotal Tracker. A quick script to generate a status page automatically when I update a text file took less time than choosing a piece of software and figuring out how to make it do what I want it to do. .plan files were a much easier way to do this, but people don't know how to type the name of a program any more and WebFinger doesn't exactly do what I want. I'd make this a bot and shove it on FSE, but that doesn't really do what I want, either, and it would be a somewhat chatty/boring bot. Doing it like this, you can just go look at the page.