The Eric Wroolie Blog

Overpass Experiences

  • Blog
  • Videos
  • Overpass Apps

Powered by Overpass Apps

In love with our own lingo

January 5, 2010 by wroolie 4 Comments

I worked on a software project recently where the interface was developed more by developers than end-users (you see this a lot, actually).  In this instance, the application needed a phone number (but not a mobile number).  Rather than asking for a land-line number (or just “Phone number”), the entry form asked for a PSTN.  I was doing a usability review of the app and pointed this out– “What the hell is a PSTN?”

The IT head pointed out to me that a PSTN is the industry term for a land-line (it stands for Public Switched Telephone Network) and that, now that I knew this, it should make sense to me.  I suggested he change it to “Phone Number”—since this app was going to be used by the general public.  He insisted that most people know this—just not me.  I told him he should still change it.  This advice fell on deaf ears, but we made some other good changes to improve the usability of the app.

I'm Not Sure What's Not Allowed
Creative Commons License photo credit: jakeliefer

My logic is (and continues to be)—if I don’t understand a term, it’s too confusing.  If I do understand it, would my grandmother?  In my situation, there are still occasions when I don’t understand something because of cultural differences– like expressions used in the UK but I never grew up with.  I still question them anyway.

This happens all the time—techies want to educate the non-techies on how to talk about technology.  Sometimes, these aren’t even terms in the technology industry—but acronyms and abbreviations used in a specific company that everyone adopts.  I’ve been in small twenty-person offices where you would think everyone went to school to learn how to talk like they do—even the secretaries: “Are you going to de-duplicate the NOC node or shall I?”  Eventually, no one knows how to talk like a regular person anymore.

We techies love our lingo.  In even smaller arenas (like a company or an industry) this lingo becomes even more precious. When we talk like this, we really sound like we know what we are talking about.  It impresses people (or so we think).  I can remember the feeling of working on a stock trading application for a major bank and talking about trade flips and different types of transactions and FSA systems and then stopping to reflect on how cool it must all sound—I was an insider.  I wasn’t a newbie—I sounded like an authority.

But all good software and hardware have the ability to take techie jargon and make it palatable to the masses.  A good site or web application should not imply when you log in that you have no business being there because you don’t know how to use it.  If you don’t understand the menu options, then you are in the wrong place.

In the future, people may look back at our gadgets today and conclude that Apple created the digital music player.  The truth was that portable MP3 players existed a few years before the iPod, but while techie ruled this area (with Rippers, LAME codecs, etc), Apple made the whole process simple for those who didn’t feel like pouring through thousands of forums and blogs to figure out who to rip a cd.  Try explaining to your grandmother how to set up a podcast aggregator while not using iTunes and you can see how much they simplified this area.  The term MP3 made it into the mainstream lexicon, but most of the terms of the early days did not.  Today, you still hear people argue about the benefit of Ogg or Flac over MP3, and can’t figure out why the mainstream hasn’t switched from MP3 to the superior Flac.  But the general public doesn’t care about this.

Google is revolutionary and I love the company, but to read many of the books out there (like “The Google Story” or “What would Google do?”) you would think that before Google, we were all randomly typing URLs into our browsers hoping to find something.  Yahoo, Ask Jeeves, Alta Vista, Lycos, etc were all there.  But Google made it easy in addition to being far more efficient.  One textbox, one button.  It was easy to tell your grandmother how to use it.

In technology, especially when it comes to interface design or anything that requires us to interact with the public, the best skill is to be a layperson.  Some people call this the “mother” test.  If your mother came to this site, or used your application, could she figure out how to use it without calling you?

I think about every time I have to fill in my tax forms how lost I am.  Even the “How to fill in this form” instructions confuse me.  It makes sense to someone, but they are in love with their lingo too.

Filed Under: Software Dev & Productivity

New Years Resolutions

December 31, 2009 by wroolie 3 Comments

I’m a big believer in New Year’s Resolutions.  Having said that, I hadn’t really thought of any.  Sure, there’s the resolutions that could be carried over from last years—all that diet and exercise stuff—but nothing new.

At this time of year, I feel self-conscious about running. Tomorrow morning will the the worst.  The sidewalks and pavements are always packed with runners on the first of Jan.  Since my long career in running has not done much to reduce my weight (imagine if I didn’t run!), I always look like a novice when I’m out there.  I look like a New Year’s runner.  But still, there’s nothing wrong with being someone out on a run because they made a resolution.  Good for them!  They probably feel self-conscious too, but they do it anyway.

This time of year, if you talk about resolutions, 3 or 4 people say the same thing– “My resolution this year is to not make any resolutions!”  Hah!  Get’s me every time!  How clever.

The problem I always had with resolutions is that I fear being mocked if I don’t carry them out.  I felt the same way when I started running or earlier this year when I started going to the gym.  I felt that if I start, I could never stop because that would be failure somehow. 

If I go for a run on 1 January, for example, I feel as if I have to run every day after that.  If I start going to the gym, I need to go for years.  But the truth is, this kind of fear stopped me from doing lots of things.  If I go to the gym once, it’s one time more than never going.  If I see it as something I need to do today rather than a commitment to something for the rest of my life, it makes it much easier to handle. 

My most famous resolution with my family is the time I decided I would become a vegetarian.  It lasted 7 days.  But that burger on January 7th was fantastic!

My parents quick smoking on New Years when I was a kid.  They never took it up again.  Resolutions are not always broken.

There’s nothing magical about a New Year’s resolution—it just gives you an excuse to make a goal.  An it’s easier to tell people how long you’ve been keeping it up.

I’ll spend today thinking of a good resolution.  It seems a waste of a calendar change if I can’t come up with one.

Happy New Year and I wish you a wonderful 2010.

Filed Under: Running

Complexity of software projects

December 22, 2009 by wroolie Leave a Comment

A good article was posted yesterday by the ComputerWorld Website saying that the leading cause of software project failures is the complexity of the applications.  The article quotes software architect Roger Sessions:

“Our goal should be to design the least complex architecture possible that solves the business problem”

I’ve been part of many projects that were mired in complexity.  They usually over-run or we end up with a sub-par system that awaits a never-to-happen refactoring and revision.

MiG-21MF Cockpit
Creative Commons License photo credit: Kecko

It’s easy to brainstorm a project and add feature-after-feature until you produced a project plan which stretches over months or years.  It’s easy to design an interface that looks like a cockpit dashboard with lots of functionality that you will probably never use, but looks impressive in the way it fills the screen.  “Wouldn’t it be great if this interfaces with every other system we have?  Wouldn’t it be great if we could use that new transactional system that’s really hot right now?  Wouldn’t it be great if . . .”

I’ve been guilty of this in the past—but I’ve been burned so many times that I tend to err on the side of simplicity (but I don’t always get final say in architectural decisions).

Over the past few years there has been a move to simpler architectures, simpler interfaces, and quicker release cycles.

Scrum is an agile methodology that stresses frequent releases over many iterations.  So, at the end of each 2-3 week iteration, you have working software—regardless of whether you release it to the public or hold until the next iteration.  It’s a methodology that resonates with a lot of people who have worked on failed projects in the past.  I became Scrum Master certified a few years ago, and it changed my whole view of how projects should run—but it is not easy to convince business owners to go this way.

37 Signals released a fantastic e-book called “Getting Real” which they stress that building software is more important that talking about building software.  They have released one of my favourite on-line apps ever with Basecamp.  It is quick, easy, and has a simple interface.  They refuse to clutter it every bit of functionality anyone asks for.

Interfaces in general are getting more simple to use—and not just for products like Basecamp.  10 years ago, you had apps that tried to fill your entire browser with things to do, but now you see more and more that are intuitive and easy to use.  Compare Yahoo! (with a browser window you couldn’t find any blank space on) with Google (a textbox and a button—no manual needed).

The software that has a better chance of reaching “finished” is the software that keeps the architecture simple, keeps the interface simple, and releases frequently.

Here’s the link to the ComputerWorld article:  http://www.computerworld.com/s/article/345994/The_No._1_Cause_of_IT_Failure_Complexity

Filed Under: Agile, Software Dev & Productivity

  • « Previous Page
  • 1
  • …
  • 34
  • 35
  • 36
  • 37
  • 38
  • …
  • 112
  • Next Page »

Recent Posts

  • The Last Human Developer
  • My Gig and the Imposter Syndrome
  • Getting Picked Last for Teams in PE
  • One Little Growth Opportunity at a Time
  • I’m sorry if I look like I know what I’m doing