When I had one day’s notice that Hillary Clinton was going to release her schedule from the time she was first lady, I thought it entirely possible we’d have to scan it, or work with a scanned copy. So I signed up for an Amazon Web Services account in case I needed to rent some computing time via EC2 to process all the images.
I mentioned I’ve learned some rules of how database apps change over time, now that I’ve done a few dozen. They are:
I’ve got a Rails project in the works that needs a forum to live alongside it, so I went looking for an existing Rails forum to adopt and customize.
It’s been a long time since I’ve written
about what I’ve been up to at the Washington Post, so let me run down the apps
I’ve worked on since September 2007 in roughly linear order. Lots of these apps link different places,
so if you don’t see projects.washingtonpost.com at the start of the
URL, you’ve probably wandered off something I directly worked on.
I’ve had a few folks ask me if I really write tests for all my projects, like I mentioned in the last line of my second email in You’re Not Refactoring. Really?
If you’re a developer who doesn’t use IRC, you’re not being as productive as you could be. I was thinking about this when I read a blog post on how IRC can be a nice low-interruption news source. It can be handy for that, but the real value in IRC is other developers.
Changing code is a great way to break it, especially in really subtle ways that you won’t pick up on for weeks or months. The maintainer of Unangband, Andrew Doull, wrote that Refactoring Is Hell. I sent him a note in response to that blog post that I think I may just as well have blogged. So: