As I’m pulling my life back out of a hundred cardboard boxes and settling into a new place, I recognize a kinship between moving and rewriting code. You spend a lot of time and effort, you Do Things Right This Time, you expend resources, and you feel productive for how much you’ve done. And in the end, you’ve probably just got a few new features and you’ll find a few new problems after a couple weeks.
ICANN is moving steadily to enact a fast-track process for gTLD creation (where “fast” here means “months instead of years”), so there could be a few more competitors for .com, .net, .pro, and the rest of the gang in a year or two. Some of the early candidates are .bank, .nyc, and .paris.
What this means, of course, is that www will never die. When a website could be advertised at “strand.nyc” or even just “google”, there needs to be something to indicate to the viewer they should go type this into their computer. It’s not going to be “Hey, now that you finally get that .com isn’t some kind of stutter, type this into your computer:” and it’s sure not going to be “http://”. It’s going to be www, and it’s going to just barely be the lesser of several evils for a long while.
Bram’s Law cleverly explains why a lot of common software sucks. I was just chatting in #startups and coined my own law to lay alongside it. I think I finally understand why all the gigantic content management systems and “Enterprise solutions” I’ve seen are so terribly bad.
We were having a conversation about designing a particular feature to scale up nicely…
<goldbond> if you are going to charge for your application, scaling really isn’t a problem right? because you can just throw a ton of hardware at it without eating up all of your revenue
<axod> goldbond: depends how badly you scale
<axod> as long as you charge more than it costs ;)
<Harkins> So clearly, the more you charge, the less competent you need to be.
<Harkins> I’d better go raise my prices.
I’ve been curious about git for a few weeks. I’ve heard friends recommend it, a lot of big projects (Linux kernel, Xorg, Rails) have switched to it, and I hadn’t yet learned a distributed version control system. I’ve bounced off the blog posts I’ve come across, they weren’t well-organized or assumed some basic familiarity I didn’t have. The man pages were also kind of intimidating.
I used the handle malaprop as my
username on sites when I started doing stuff on the web, and it worked
decently. Short, memorable, and almost always available. I got involved
in Chicago programming communities and found a shortcoming: it often
took weeks or months before someone connected my name and my handle.
There weren’t any wacky sitcom hijinks, but it was confusing.
I switched to “Harkins”, which is what I’m still using today. It’s
DRY (rather than two names for the same person), short, easy-to-spell, but it’s available less and
less regularly as more people get online.
I’m trying to pick a new username. I’d like it to be based off my real
name, but I’d also like to balance that with brevity. “Peter_Harkins” is
plain too long, I don’t want to use more than 10 characters. “PHarkins” is
right out, I don’t need to be conflated with phone phreaks and other
creative spellers. I’ve been assigned “harkinsp” at too many schools and
workplaces to enjoy it, and it’s not very unique.
I’m tempted to get a bit playful and do something like “hark_ins”. I’d
have some hassle with the various underscore/hyphen rules of different
sites, but it’d always be available.
Any suggestions? What handle have you based on your name?
I found this post on design constraints to be great food for thought. The restrictions look like they’ll make for great exercises that I wouldn’t have otherwise thought to do. They remind me of poetic forms, in that they’re difficult but perhaps ultimately liberating..
Then I saw a blog post saying:
This strikes me as so bogus, I can’t even begin to describe it.
A little poking around turned up plenty more people echoing the sentiment: that the exercises were unrealistic, needlessly restrictive, unproductive, etc. They’re right for the wrong reasons: these are all reasons that this is exercise. You’re cross-training, learning to swim with one hand behind your back. I’m going to stop belaboring the value of practice because Steve Yegge already belabored it quite well, but you’ll stagnate if you don’t struggle to improve.
(And hopefully we’ll all start practicing often enough to start figuring out what does and doesn’t work.)
Improvement and the Hawthorne Effect
Biz: 37signals, Hawthorne Effect, urgency, work week
37Signals decided to experiment with a 4-day work week and announced last week that it had been success in improving productivity and employee satisfaction. I saw it linked from a few places, and the most common comment was “Wow, they should try a 3-day work week, they’d be even more productive, right? Wait, how about a 2-day!?”
James Noble and Robert Biddle wrote Notes on Postmodern Programming in 2002, and I was reminded of it Wednesday. In section 13 they describe “A First Example of Scrap-Heap System Construction”.
Turning WordPress Categories Into Tags
Code: automation, insert into select, MySQL, SQL, WordPress
I recently updated this WordPress install from 2.2.something to 2.5 and noticed that it now supports tags instead of just categories. I had been using categories as tags, but I’d rather built-in tags than fake it anymore. I didn’t want to manually retag a couple hundred posts with ~200 tags, so I wrote some SQL to do it for me. If you’re in the same boat