This article is a continuation of Kiln’s Evolution, Part 1: DVCS as Code Review. In the fall of 2008, Joel was getting increasingly adamant that FogBugz needed source control integration, and most people in the company seemed to think Subversion would probably be the best SCM to make that happen. Tyler and I disagreed, believing strongly that we should use a DVCS instead, and that our code review tool gave a really compelling example of why DVCS was better that any software shop would…

Google’s motto is, “Don’t be evil.” I’ve always found that motto disturbing for two reasons. First, a company that can differentiate itself—successfully, no less—from its competitors merely by promising not to be evil implies that the average company is ridiculously corrupt. A person who announced, “My motto is, ‘don’t shoot people’” would be notable because no one thinks you should shoot people, making the promise weird and redundant—not because the promise represented some great sacrifice. …

Well. At least it makes it suck less. I bought a Droid the day it came out. While it was a tremendous improvement over my BlackBerry, I’ve been disappointed with the phone overall. The battery cover comes off constantly ([2]2, [3]3), the phone’s proximity sensor was extraordinarily finicky (usually resulting in me hitting the “mute” button with my cheek in the middle of a call), the camera was all but useless, and, for reasons I did not really understand, my Android developer phone running…

One of the things that really sucks about doing online code reviews is that, in all the systems I know, your code reviews do not integrate with your source control. If the code reviews are versioned at all—and they’re frequently not—then they’re in an entirely different system than your real VCS. For larger reviews, where you’re talking about a major piece of functionality, that means that your source control system will end up lacking the history of how a feature came to be. In other words,…

For the past year, an odd thing has happened, if you’ve followed my doings. My work on Fog Creek Copilot seemed to dwindle, I became tight-lipped about what I was working on, and I started getting really excited about an upcoming product release. Also around this time, my knowledge of Mercurial, Python, C#, and ASP.NET MVC all seemed to dramatically increase, even though my free-time code output shrank to nothing. What was going on? Oh, the usual. I was working on a top-secret brand-new…

“Implementing caching would take thirty hours. Do you have thirty extra hours? No, you don’t. I actually have no idea how long it would take. Maybe it would take five minutes. Do you have five minutes? No. Why? Because I’m lying. It would take much longer than five minutes. That’s the eternal optimism of programmers.” — Professor Owen Astrachan during 23 Feb 2004 lecture for CPS 108 Accusing open-source software of being a royal pain to use is not a new argument; it’s been said before, by…

These days, arguing that open-source software is crap seems dumb. How many websites are powered by a combination of MySQL, PHP, and Apache? How many IT applications, written in Eclipse, run on Java, using SWT widgets? How many design studios rely heavily on The GIMP and Inkscape for their everyday photo-retouching and page layout needs? Er, wait. That last one. Doesn’t quite ring true. In fact, as good as most people seem to insist that Inkscape and The GIMP are, I’ve yet to see a major…

When I first saw Palm demo the Palm Pre, I was very excited: for the first time, I saw a phone that looked as if it would be a genuine competitor to the Apple iPhone. Palm has clearly put lot of thought put into its design: the interface is intuitive and fluid, basically invents a reasonable way to do multitasking on a portable device, and still seems to adhere closely to Palm’s historical emphasis on simple, clean UIs—something that my nine-year-old Handspring still does better than my…

Not outsourcing to India; outsourcing to third parties. The Wall Street Journal details how Sony’s R&D budget paid for the CPU in Microsoft’s Xbox360, and how that ended up being part of the reason for the 360’s success against the PS3. Joel’s defense of NIH syndrome for core functionality in your product makes more and more sense the longer I spend in the industry.

I’ve long preferred Pownce to Twitter. It allows longer messages, has better uptime, has a better API, allows you to send links, photos, and files in addition to text…basically, it was just better in every way. The Copilot team made heavy use of Pownce during our Hair on Fire sprint, and continued to use it until we adopted Laconica internally. So I was deeply saddened to learn that, in a mere two weeks, Pownce will be no more. I guess Twitter’s where I’ll be now, whether I like it or…