MessiandNeymar

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, October 18, 2012

Scott Hanselman nails it

Posted on 4:41 PM by Unknown

In a nice three-part series, Scott Hanselman talks about software, and bugs, and what to do:

  • In Everything's broken and nobody's upset, he calls out the Emperor for having no clothes, and speaks the ugly truth:
    Software doesn't work. I'm shocked at how often we put up with it.

    ...

    Here we are in 2012 in a world of open standards on an open network, with angle brackets and curly braces flying at gigabit speeds and it's all a mess. Everyone sucks, equally and completely.

    As Hanselman observes, one of the issues is that many people use Google as their principal problem solving tool:

    Here's the worst part, I didn't spend any time on the phone with anyone about these issues. I didn't file bugs, send support tickets or email teams. Instead, I just Googled around
  • In A Bug Report is a Gift, Hanselman talks about the question of whether it's easy or hard for users to file a bug against your software:
    Is it easy for your users to report a bug? Does you app automatically report crashes? Is your site friendly? Are you support people friendly and engaged? Are your bug support forums filled with reports but no company representatives? Do you use GetSatisfaction or UserVoice?
  • And in Help your users record and report bugs with the Problem Steps Recorder, Hanselman talks about some specific technical solutions that you can put in place to help your users send you bug reports:
    On the subject of bug reporting, there's a wonderful gem of a program that ships with Windows 7 and Windows 8 that you and your users can use to report and record bugs. It's the Problem Steps Recorder and it's like TiVo for bugs.

I love the practical advice and extensive examples that Hanselman includes in these posts, but what I really love most of all is the perspective he brings to the entire topic:

How hard does the user have to work to file a bug? It's OUR bug but the user not only hit the bug but also has to work to report it!

Every click or manual step that our users have to invest in our bug is a click too many. A bug is the pain that hurts the user and keeps hurting as they report it! A good bug report is a gift that keeps on giving and we should treat it as such.

I'd love a world where all crashes are automatically reported and there's a "Send a Frown/Smile" button on everyone's computer that offers to record a short screencast with just a single "record/stop" button.

You can't fix the bug until you find it, so the first step toward improving software is to make it as easy as possible to find, isolate, record, report, and track those bugs.

Thanks, Scott, for the helpful and well-intended suggestions; now let's get them adopted!

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Shelter
    I meant to post this as part of my article on Watership Down , but then totally forgot: Shelter In Shelter you experience the wild as a moth...
  • The Legend of 1900: a very short review
    Fifteen years late, we stumbled across The Legend of 1900 . I suspect that 1900 is the sort of movie that many people despise, and a few peo...
  • Rediscovering Watership Down
    As a child, I was a precocious and voracious reader. In my early teens, ravenous and impatient, I raced through Richard Adams's Watershi...
  • Must be a heck of a rainstorm in Donetsk
    During today's Euro 2012 match between Ukraine and France, the game was suspended due to weather conditions, which is a quite rare occur...
  • Beethoven and Jonathan Biss
    I'm really enjoying the latest Coursera class that I'm taking: Exploring Beethoven’s Piano Sonatas . This course takes an inside-out...
  • Starting today, the games count
    In honor of the occasion: The Autumn Wind is a pirate, Blustering in from sea, With a rollocking song, he sweeps along, Swaggering boisterou...
  • Parbuckling
    The enormous project to right and remove the remains of the Costa Concordia is now well underway. There's some nice reporting on the NP...
  • For your weekend reading
    I don't want you to be bored this weekend, so I thought I'd pass along some articles you might find interesting. If not, hopefully y...
  • Are some algorithms simply too hard to implement correctly?
    I recently got around to reading a rather old paper: McKusick and Ganger: Soft Updates: A Technique for Eliminating Most Synchronous Writes ...
  • Don't see me!
    When she was young, and she had done something she was embarrassed by or felt guilty about, my daughter would sometimes hold up her hand to ...

Blog Archive

  • ►  2013 (165)
    • ►  September (14)
    • ►  August (19)
    • ►  July (16)
    • ►  June (17)
    • ►  May (17)
    • ►  April (18)
    • ►  March (24)
    • ►  February (19)
    • ►  January (21)
  • ▼  2012 (335)
    • ►  December (23)
    • ►  November (30)
    • ▼  October (33)
      • HMS Bounty RIP
      • Programmers and Paparazzi
      • 24 hours with the "17"
      • The slow maturation of C++
      • Kinda quiet recently...
      • A random collection of random stuff
      • IPv6 Summit in Slovenia
      • Instance tasting
      • New Linux 0, Old Laptop 1
      • Quantal Quetzal
      • Photo-essay on cork production
      • Facing the tsunami
      • The age of books is not yet over
      • Paul Allen is in the Bay Area
      • Scott Hanselman nails it
      • Once there was a sailboat...
      • Wind: 1, Oracle: 0
      • Presidential Precedent
      • Drilling down, spreading the load
      • XCOM Enemy Unknown
      • MOOCing again
      • Gawker outs VA
      • Harborside Health
      • It's not just a game ...
      • Leo Messi piece on ESPN
      • Social coding and Atlassian Stash
      • Gone Girl: a very short review
      • Computers and Chess
      • A translation guide for the culturally impaired
      • Russell Coutts goes airborne!
      • Perforce Git Fusion
      • SHA-3 is Keccak
      • San Francisco Measure F
    • ►  September (34)
    • ►  August (29)
    • ►  July (39)
    • ►  June (27)
    • ►  May (48)
    • ►  April (32)
    • ►  March (30)
    • ►  February (10)
Powered by Blogger.

About Me

Unknown
View my complete profile