Category Archives: WordPress

The open source publishing platform I co-founded โ€” development, releases, community, and the ecosystem.

Best Route

Blogging to you live from Arizona. We’re going to stop in Tucson for the night and I wanted to solicit feedback on what’s the prettiest drive from there to San Francisco. Until now the plan has been “Get on I-10, go West” but I remember some very specific advice from people on what roads to take and not to take once in California, I just can’t remember what the advice was. I’d like to avoid LA if possible, but other than that I’m open to anything. Any suggestions?

Dumb Lawyers

I like lawyers, I consider a few to be friends, but I have to question how some of these people made it into college, much less pass the bar. I got a letter today regarding Agilepeople, which I have never even heard of until today, and they decided apparently since the site uses WordPress I was the “hosting company” and I should provide the “name, address, and telephone number of the owner of agilepeople.org. If we cannot secure the information from you regarding the identity of person or persons who are infringing on our client’s legal rights, we will have no other recourse but to consider litigation.” But wait, it gets better! I call the number on the stationary and apparently the lawyer who sent this doesn’t even have the correct number on the letter.

1.3 Cleanup

A few comments about some of the code changes in 1.3. Very nice to see people appreciating some of the hard work we’ve put into this iteration. In a perfect world we could stop the clock and rewrite large portions of the code from scratch, but that would take a long time and break a lot of things in the process. All programmers want to do this, it’s our weakness, but every time I get this urge I think of Netscape and how devastating their rewrite downtime was. We’re making some substantial changes but doing it gradually while introducing new features and responding to users needs.

For example, in 1.3 “the loop” is called very differently but it’s completely backward compatible with everyone’s 1.2 loop code. We deprecate things over time so any structural changes that need to be made come gradually for people upgrading, there’s nothing to drastic every time. This also saves a huge amount of time in support. (Regular users don’t want to have to redo their templates, hackers don’t want to relearn code they already knew.) Same for the new theme system we’re introducing, it adds a lot of flexibility, radically changing how the front end of WordPress operates (like plugins for templates and styles) but all the new stuff is completely optional. I’ve transitioned most of my custom code into a personal “theme” that makse upgrading a lot easier for me (which is good because I do it almost daily).

Next time you get the urge to rewrite from scratch think about the testing your code has gone through, all the edge cases that have already been addressed, the existing installed base, and how many new bugs you’ll introduce with the from-scratch code.