How to write like an architect

I found this on kottke.org, and I know Jason Kottke’s audience outnumbers mine by several orders of magnitude, but I still found it interesting enough that I wanted to share it here.

I’ve been thinking about architecture (the occupation, not buildings themselves) a lot lately as I’ve been working with some architects as clients. The thing I like about architects is that I think there’s a lot of similarity between what they do and what I do — both architecture and web design/development require a mix of artistic sensibilities and methodical, scientific thinking that don’t often come together in other fields. Of course, it takes a lot more training and skill to become an architect; I won’t even pretend we’re in the same league in that regard.

Probably the biggest difference between the two fields is that what I do is almost entirely based on computers (obviously), whereas while computers are certainly an integral tool to architects, the end product of their efforts, along with many of the tools and techniques they use to do their jobs, are physical, tactile, hands-on. Paper, pencils, T-squares, rulers, etc. I use those types of physical tools so rarely anymore that I can barely even write my own name legibly.

Which brings me to this pair of videos on How to write like an architect. It’s fascinating to see how these letters come together and the orderly yet stylized results.

And here’s how you do it with a pencil…

In another age (maybe even if I were a mere decade older), architecture is likely something I would have pursued instead of the path of least resistance web design offered me when I emerged from college at precisely the right moment (1996). Working with architects as clients has allowed me to get a vicarious taste of that world.

Bring down IE 6!

IE6, R.I.P. I wish.Here’s a far more detailed, reasoned explanation of why Internet Explorer 6 is just plain bad than I could ever muster in the midst of one of my Microsoft-fueled rages. (OK, maybe that overstates it a bit and gives Redmond too much credit for my anger issues.)

Here it is, plain and simple: Internet Explorer 6 has been around as long as Windows XP, and it’s even longer in the tooth. A lot has happened to the Web in the last 8 years, and IE6 is simply not equipped to handle what 2009 websites throw at it. It’s a security nightmare, and it’s woefully lacking in support of even relatively modest features that all other browsers out there today support, and that we in the web design and development community desperately want to take advantage of in building functional, aesthetically pleasing, just plain cool websites.

But we can’t. Or, we can, but then we have to spend a substantial chunk of the total time and budget of a project (often a third or more) hacking our own (standards-compliant) work to try to make it even just passably functional in IE6. This has to end. IE6 is not just a pain in the butt of web geeks like me. Because it is wasting the valuable time and financial resources of anyone involved in the creation of websites (and by extension, any business or organization that has a website), it is a drain on our economy in the same way as old, gas guzzling cars or any other outmoded, grossly inefficient system.

It’s time. IE6 is dead. Lay it to rest.

The Mother of All Funk Chords

I just had to pile on to the mountain of people sharing this because it’s so cool:

Merlin Mann pretty much sums it up:

Unsolicited tip for media company c-levels: if your reaction to this crate of magic is “Hm. I wonder how we’d go about suing someone who ‘did this’ with our IP?” instead of, “Holy crap, clearly, this is the freaking future of entertainment,” it’s probably time to put some ramen on your Visa and start making stuff up for your LinkedIn page.

Because, this is what your new Elvis looks like, gang. And, eventually somebody will figure out (and publicly admit) that Kutiman, and any number of his peers on the “To-Sue” list, should be passed from Legal down to A&R.

Seriously, UPS… you had to TRY to do that much damage, right?

The other day I ordered a RAM upgrade for my new MacBook. I had contemplated buying it at Best Buy, but I balked at their price of $199. I went down to the Apple Store (no Internet on the Macs on display at Best Buy, and apparently they have the store wrapped in RF shielding, as I wasn’t even able to get a signal on my iPhone there, either), not expecting them to sell RAM upgrades, but at least knowing I could spend a few seconds on a display MacBook checking RAM prices at Ramjet. $69. So I ordered it as soon as I got home.

The package arrived today. Or at least what was left of it. Fortunately the RAM appears to be intact, no thanks to the best efforts of UPS to destroy it. The question of whether such a tiny product really needed to be shipped in such a huge box is another matter, but at least the RAM was shrouded in bubble wrap.

Here’s what I found at the front door:

ups_ram_7

And here’s the prize inside:

ups_ram_9

More photos after the jump…

And now I’m going to shut down my computer and install this RAM!

And now for a completely different complaint about modern technology: out-of-sync HDTV audio

Cletus vs. ComcastMost of my complaints about the modern technologies I love so well pertain to computer software. But here’s a new one for you: out-of-sync audio on HDTV programming.

Last year, just in time for the Beijing Olympics, we purchased a 42-inch LCD TV. It’s awesome. I know they make ’em bigger, but our smallish living room really couldn’t handle anything bigger.

It’s all great, except for one thing: frequently (like around 30% of the time) while watching HDTV programming, the audio becomes severely out of sync — at least a second or two ahead of the video. We’re getting our HDTV programming via the cable company (Comcast). We just have basic cable, but Comcast delivers the high-def signals from our local broadcast stations.

Now I have come to a point where, when I express a complaint like this, I expect the first response from many people I know will be, “Why don’t you get digital cable, cheapskate?” Why don’t I, indeed. Start with the fact that I’m already giving Comcast more money every month than I can possibly justify; 95% of what’s on cable TV is utter garbage I would never deign to watch, even though I am paying for it. The only reason I’m even paying for basic cable is because when Comcast bought out Time Warner, they changed the pricing schedule such that it’s actually $3 cheaper per month to get basic cable TV and Internet bundled ($62) than to get Internet alone ($65).

So, I’m just fine with the only HD programming I’m receiving being the local channels. That’s all I really need or want anyway. But it would be nice to at least be able to watch those channels without this ridiculous audio lag appearing with increasing frequency.

Why blame Comcast? How do I know it’s not just the signal itself? Well, I don’t. But perusing Google for similar complaints, I found some suggestions that the more intermediary devices — including cable TV itself — between the digital broadcast signal and your HD television set, the more likely this audio sync problem was to occur. Essentially what it boils down to, as I understand it, is that the digital video signal takes varying amounts of time to process, but if there’s not proper equipment in place to apply an equivalent lag to the audio channel, keeping it in sync with the video, this problem will occur.

What’s the solution? Well, if the above is correct, I have a hunch that pulling out the good ol’ rabbit ears and attaching them to my 42-inch LCD might fix the problem. And it would certainly add to the aesthetics of my living room. But ultimately, Comcast needs to fix this problem. If they’re going to deliver the HD broadcast channels’ signals, they need to do it right. After all, that’s what we’re paying them for.