I’ve learned two valuable lessons recently: Don’t be lazy. Don’t be a brat. More specifically: add a subject line to your e-mails. It’s not that hard and it makes everyone’s life easier.

When I first started at Imulus, I was not accustomed to inter-office exchanges of e-mails. Most of the time if someone wanted me to complete a task, I would attach the completed item to an e-mail and send away. Naturally I would ignore the prompt asking me if I still wanted to send the e-mail without a subject line. After a while, my mail application would give up on me and stop the alerts.

Eventually, I was diplomatically informed by some of my co-workers that my neglect of subject lines may be a tad annoying. “Annoying?” I thought in my most indignant mental voice. “I’ll show them annoying.” After this cerebral conversation with myself, I proceed to add subject lines that had nothing to do with the actual e-mail. Subjects such as “sweet cuppin cakes” or “I like turtles” would crop up in my co-workers’s inbox giving them something to chuckle at or be irritated at.

My shenanigans ensued for around a year and a half until the day that cruel irony bit me square in the ass. During a dark day in Imulus’s history when we lost some information, I was doing my best as the diligent designer to help recover all that I could. This meant I had to look though old e-mails with my trusty search to help me. Side note: I am not a good organizer when it comes to my e-mail and I am a digital pack rat – bad combination. Anyway, back to our flustered heroine. As I was sorting through my old e-mails becoming increasingly murderous towards my past self I came to a harsh revelation – it’s not worth it. It’s not worth the inconvenience for maybe a couple of seconds of giggling at the silly subject line.

These days I have learned my lesson… Although occasionally I do like to slip in the old silliness, but only if it applies to the real subject line.

In the Beginning

When I first started using Mac OS X in college I fell in love with the Safari web browser. It was light weight, sexy, and fast. Unfortunately, the more I ramped into complex web development the more I realized Safari’s severe developer limitations. Back then developers had to enter terminal commands to even gain access to Safari’s developer menu. And, once turned on, the developer menu lacked the oomph of Firefox’s flourishing Firebug and Web Developer Toolbar extensions.

Since that day I’ve been using Firefox heavily for development and only occasionally jumping into Safari to test site feel and functionality.

Then, about a year ago, Safari started making real steps to support web developers. The release of Safari 4 earlier this year capitalized a nice upswing in Safari developer improvements. But, unfortunately, Safari still lacks some of the most basic development capability.

In my opinion, if Safari doesn’t address the following three issues, it will never become a viable competitor to Firefox for developers.

Source View Made for the 80’s

Any time your browser’s source code view renders like Internet Explorer’s you really need to sit down think things over. Is this acceptable, am I being an asshole? The answer, obviously, is yes.

Let Me View Background Images!

The web is no longer a mass of tables and img tags. Thanks to CSS we’ve started abstracting background effects from real content. Knowing this, there is absolutely no reason why Safari shouldn’t have a view background image option. Safari, do you really expect me to right click, inspect element, and then track down the CSS that links to that background image? Give me a break.

Target HTML Elements Faster

The best thing about the Web Developer Toolbar extension for Firefox is that you can hit cmd-shift-y and instantly view HTML elements. This is perfect if you’re trying to track down a styling issue or remember an ID name. It’s fast, easy, and accurate. Safari’s right click > inspect element isn’t even in the same ballpark as this. And, as hard as I’ve tried, there’s no way to reassign the Inspect Element shortcut in OS X.

Conclusion

Safari, you’re a great consumer browser. And yes, WebKit is a phenomenal web rendering engine. Hell, even Google loves you. Please, just fix these small problems and I’ll switch to you full-time, I promise! Until then, I’m going to continue buying FireFox t-shirts.

It’s 6:30pm and you’re tired from a long day of work. You’ve just finished writing a four page email to a client. Documenting all of the tasks you completed that day. In fact, you even took time to explain the reason you used nofollow linking to the client’s intranet website. Then, moments later, Mail unexpectedly quits. Your work is gone.

Or… is it. You remember copying the contents of the email to your clipboard minutes before. Quickly you open a new email and anxiously paste:

http://tr.im/OMG_ribbons …

wait, no, surely that can’t be right. You paste again:

http://tr.im/OMG_ribbons …

Then you remember, that co-worker of yours, Taylor, sent you a link on IM (”Haha, d00d this is hilarious”). But for some reason it didn’t format right and you had to copy it.

You think — there must be some solution, assuredly. Yet no, your work is gone. You swear to yourself, “never again.” Fortunately, moments later you find a blog post describing your exact scenario. It suggests downloading the free app Clyppan to record your clipboard history. “Wow, that’s awesome,” you say to yourself, “I’m gonna use this all the time.”

And guess what, you do.

Edit: One note, if you don’t set Clyppan to run on startup via system preferences > accounts, then you’ll have to start it manually every time you login to OS X.

Edit 2: Some might suggest the Quicksilver Clipboard module for this same functionality, however, as of 10.5 that module tends to randomly appear when quitting certain applications. Hence why I moved to Clyppan.