« Code must be nurtured | Main | Nobody is really smart enough to program computers »

Leak proof

So for now, my advice is this: don't start a new project without at least one architect with several years of solid experience in the language, classes, APIs, and platforms you're building on. If you have a choice of platforms, use the one your team has the most skills with, even if it's not the trendiest or nominally the most productive. And when you're designing abstractions or programming tools, go the extra mile to make them leak proof.
    -- Joel on Software

Comments (1)

Leak proof is a good one.

At Rojo we had a framework I wrote for performing quick joins against the DB.

The problem is most people never used it and I would print log.warn() messages that would be written to logs the developers would never see until they were put into production.

The speed boost was about 10-30x so it was important that we didn't hit this.

One of the developers suggested throwing an exception when they used non-optimal joins.

For some reason this didn't dawn on me and turned out to be a BRILLIANT suggested as we had no more pushes with non-optimal joins :)


Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)


This page contains a single entry from the blog posted on February 20, 2008 8:18 AM.

The previous post in this blog was Code must be nurtured.

The next post in this blog is Nobody is really smart enough to program computers.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.33