Curtis Summers

What?…you’re not using git yet? Everybody’s doing it.  It’s all the rage (at least for Rubyists)!

I finally blocked out everything else for a few hours yesterday afternoon to learn git.  A couple of observations coming from SVN:

• The use of SHA1 hashes to identify revisions will take some time to get used to, but it appeals greatly to my inner geek.
• No central repository (every clone is the full repository) makes me feel safer about my data somehow.
• If you want a central repository like svn, use “git push <repo-url>”

There are lots of resources and tutorials out there, but I found the SVN Crash Course coupled with git’s own help pages “git <command> –help” to be all I needed.

Do you test in Safari with the same priority as other browsers? If not, you might should start making it a part of your routine. According to an article on Rob Pegoraro’s Faster Forward blog, Google’s new mobile OS, Android, contains a browser “built on the same open-source WebKit software as the Safari browser in Mac OS X and the iPhone.”

If Google can accomplish what they hope to with Android, namely, to be the mobile operating system, then developers will have yet another target browser to test for. I’m not complaining, though, Safari/Webkit is a great browser. And, as long as it maintains good adherence to web standards the additional testing only serves to better our web applications.

I think there is an interesting dynamic that occurs when a developer is freed up from the monotony of the development process. Specifically, there is a direct consequence on the usability of a product when a developer’s progress in slowed by monotonous tasks.

As a developer, I’d love to claim that my initial design intentions (sketches/wireframes, task flow) are spot-on every time. Ha! Let’s be realistic: creating a good user experience is hard to do.

It is often the case that the product is near a finished state before some usability issues are encountered. In other words, the product may be feature-complete, and deemed releasable, but it’s that extra effort towards usability that can really make a product shine.

What can we do as developers to make sure our end product has that finishing touch? Or, more specifically, what blockers exist to keep us from achieving this goal?

I’d suggest monotony is a key blocker:

Let’s define our two forces at play:

• Monotony – any repetitive, tedious process, task, or routine that drags down creativity during the development process
• Usability Luster – the extra, finishing touches on a product that exponentially elevate the product’s usability

For a developer, more monotony means less time and space (grey matter space) to cope with finishing touches. If, as a developer, I feel like a cubicle code monkey all day, every day, then that is affecting my ability to push out a quality user experience.

How can we combat monotony?

• Use tools that reduce monotony and increase productivity
  • Rails comes to mind
  • A good IDE
• Use good programming technique
  • DRY (Don’t Repeat Yourself)
  • Design Patterns (where appropriate)
  • Test (reduce your stress level by testing)
• Get a cheerleader
  • Find that guy/gal who encourages you through the monotony

What do you do to get through the monotony? What other techniques do you use to ensure that little something extra for the user experience?