mult.ifario.us

Most of the bug/issue tracking systems that I've worked with have “worksforme” as a common end-state for a bug or issue, e.g., in Trac or Jira, but I'm opposed to its use. (I see bugs and issues as distinct entities.)

For a bug, “worksforme” is irrelevant. A bug is already a well-defined and specific flaw in the software, so either a fix is completed and tested or it isn't. If the faulty code is no longer in use, then the bug is “vacuouslyfixed” or “nolongerrelevant” or some such.

For an issue, “worksforme” is potentially applicable but still semantically incorrect. Valid and semantically consistent states in the issue lifecycle might be “expectedbehavior” or “usererror” or “needmoreinfo” or “unabletoreproduce”, and even so “needmoreinfo” or “unabletoreproduce” aren't necessarily terminal states. The “worksforme” is at best dismissive and at worst a flippant if not inflammatory message to the customer.

I think that I emitted an audible snort when I read Paul Kedrosky's post about completion of graduate studies:

[...] people who don't finish doctoral degrees are people to watch. They have demonstrated deep intellectual curiosity by entering such programs, and they have demonstrated street smarts and a laudable willingness to ignore sunk costs by leaving before they get sucked into the vortex.

First off, this is blatant post hoc reasoning — “Successful people I know dropped out of graduate school, so people who drop out of graduate school are successful.”

Second, I think it's incorrect in addition to being poorly reasoned. I started my career at Berkeley with 68 peers and exited in a class of 19, and there are plenty of people I respect who finished and plenty of people I respect who didn't. Some left because of lack of ability, either in terms of raw intellectual horsepower or in terms of political savvy. (Political savvy matters more than you might think in staying supported, finding a strong advisor, promoting yourself and your work, and getting research signed-off by a committee.) Some left because of a change in personal circumstances, and some left because they saw an opportunity outside of academia in technology or financial services. If I may dabble in proof by example, two of the most successful extra-academic mathematicians I know, one trader and one entrepreneur, were successful in academia before leaving. Two of the most successful people who left without a Ph.D. did so after having completed (and even published) their research but made an informed and conscious choice about the academic career path.

I do agree with Paul that windmill detection is an incredibly valuable skill, but it's a much finer point than I think he's making. If it is really so disadvantageous to stay, then I question the base instincts of the person who got themselves into that circumstance in the first place.

Graduate work in physics, mathematics, chemistry, computer science, statistics, etc. is rocket science, but finishing is straightforward. Be disciplined. Choose wisely, put your head down, charge into the unknown, and look up to reassess frequently. Stick to your guns where you think you're right, demand thorough and valid reasoning, and aim for achievable and relevant ends. And, just like everything else, be at least a little bit lucky. Seems like good advice (and experience) for just about anyone.

I've been tinkering on a little language in Java with ANTLR v3 (still in beta, but desirable because it supports incremental parsing) as the parser generator, and so far ANTLRWorks is quite convenient as an editing environment for the grammar. (I'm also a fan and paid licensee of Prashant Deva's very nice ANTLR Studio Eclipse plugin, but it only supports ANTLR v2 for the time being.)

More approachable tooling for ANTLR will motivate fewer people to create XML languages, and the possibility to have out-of-the-box support for incremental parsing in a generic editing environment (e.g., Eclipse,NetBeans, IDEA, JEdit, etc.) should make writing a real parser a hands-down winner over using an XML parser and a ream of glue code as a crutch.

The EIN for “Multifarious, Inc” showed up in the mail on Monday, so I can finally get bank accounts set up, file the 2553 (subchapter S election) with the IRS, and finish up the initial accounting work. This will be my second company, although it has an undefined purpose by design initially and won't ever use “multifarious” as a brand. The company is a financial tool and a shell in which a number of different business concepts can compete, with one or more successful ideas getting spun out into their own entities.

Last year, I wrote a rudimentary sidebar to display Feedburner feed links in Typo, but I didn't really get it to the point I wanted at the time. So, I took another fifteen minutes to rewrite the sidebar to work with the enhanced API, ditch the auto-subscribe chiclets, add links for category feeds, and muck with routes.rb. In routes.rb, I mapped a new set of feed URLs for Feedburner onto the controller that currently serves feeds, switched the existing mappings to a two-line controller that 301's to the Feedburner equivalents, and left holes so that people can subscribe directly to article-specific or tag-specific feeds if they wish. (The bonus in this approach is that autodiscovery gets taken care of for free, because the autodiscovery feed is one that gets 301'd.)

Just for grins, here's the two-line controller implementation:

class FbController < ContentController
  def redirect   
    headers["Status"] = "301 Moved Permanently"
    redirect_to "http://feeds.feedburner.com/Multifarious" +
      params[:type].to_s.capitalize + params[:id].to_s.capitalize
  end
end

Sometimes I think that the cornucopia of methods on some of the Ruby core classes (like capitalize on String) is overkill, and sometimes, it's convenient.

I hope that the enhanced setup is useful to any readers (since Feedburner should ensure QoS), but mostly I hope that it's transparent. (FWIW, NetNewsWire did the Right Thing and changed the feed URL for my self-subscription to the new one in response to the 301.) If for some reason you can't see this, let me know...

Back in January, I blogged about the kid's sleeping issues, and things have suddenly and inexplicably turned the corner — last night she slept like a rock from 11:00PM until 5:30AM. (Do rocks dream?) The past few nights have been pretty good, too. While we worked through getting her to sleep, we talked to plenty of people who had taken a similarly permissive stance on enforcing sleep habits, and they all said the same thing, i.e., one day you wake up in the morning and the kid will have slept through the night. I guess that today was our day.

A while back, in order to get the tag functionality in Typo, I upgraded from the stable download to the trunk. Typo is in flagrant and ongoing violation of the “release early, release often” directive for software projects, but it's been a nearly painless experience each time. Except for this last time. To get an update to the Typo sidebar plugin API, I ran svn update on the Typo on my local machine, tweaked a couple of things, and tested; then I ran svn update on the Typo on my remote machine, and... crash. The difference was the theme that I use on the production server, and I resorted to Google before fishing through the theme layouts for issues. Ironically, I found a quick answer on Phil Cryer's blog and had things back to (what passes for) normal in a few minutes.

I say ironically for two reasons. First, it's ironic for me to find the answer on Phil's blog because he just gave up on Typo and went to WordPress over this very issue. And that is ironic because I gave up on Wordpress over a recurring annoyance with incorrectly set Media-type and encoding (see RFC3023 and Mark Pilgrim's discussion for some background) where I had to trace through multiple noodles of PHP spaghetti code to fix it each time Wordpress shipped a new version. (Each time, the upgrade was security related, so I felt obliged to apply it.)