Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
×
1 of 102

Doing The Work, or, Applying Leverage for Great Products

14

Share

Download to read offline

Missing videos, in order:

* Alternative feed reader: http://creativescrape.com
( QuickSilver's use of Recent Items (type an app's name, then hit the right arrow -- bam! list of Recent Items)
* iPhoto's mouseover galleries
* Quick Time Entry in Freckle (http://letsfreckle.com) with on-the-fly project and tag creation

Related Books

Free with a 30 day trial from Scribd

See all

Doing The Work, or, Applying Leverage for Great Products

  1. 1. Doing the Work Or, Amy Pretends You Care About Interface Deisgn (But Not Really)
  2. 2. Amy Ruby & JavaScript Developer
  3. 3. Amy Teacher of Programming
  4. 4. Amy
  5. 5. Amy Crusader for Cheerful Software
  6. 6. Wait— "Cheerful Software?"
  7. 7. Wait— "Cheerful Software?" Are we hot-shot software developers or are we kindergarten teachers?
  8. 8. Software should be like a great concierge.
  9. 9. Software should be like a great concierge. Always there when you need it, doing things for you before you knew you needed them done, hovering in the background, ready to spring into action. Deferent, but not a brown- noser. And looking great in a 3-piece suit.
  10. 10. If software development was Magnum PI...
  11. 11. Magnum the car the smirk the chest hair the girls the TV show the goofy charm
  12. 12. Higgins the resources the control / power the connections the snarky jokes the (awesome) accent the style
  13. 13. If software development was Magnum PI...
  14. 14. End User
  15. 15. End User Developer
  16. 16. Magnum the car the smirk the chest hair the girls the TV show the goofy charm
  17. 17. knows kung-fu
  18. 18. knows kung-fu saves Magnum's ass
  19. 19. knows kung-fu saves Magnum's ass makes Magnum possible
  20. 20. If software development were a seesaw...
  21. 21. Developer End User
  22. 22. Developer End User
  23. 23. Seesaws have a fulcrum (point of leverage) go up go down require teamwork and equal effort fun?
  24. 24. Effort
  25. 25. Effort
  26. 26. Effort Effort
  27. 27. Weeee!
  28. 28. Weeee! Weeee!
  29. 29. And nothing says "good karma, happy users, and profit" like end users saying... Weeee! Weeee! Weeee! Weeee! Weeee!
  30. 30. Developer End User So, what's this here point of leverage?
  31. 31. Developer End User Code!
  32. 32. Developer End User Code! (Specifically: commitment & effort)
  33. 33. Code! Going the extra mile so the user doesn't have to...
  34. 34. Going the extra mile... accepting many types of input formatting data & error recovery pre-finding what's useful avoiding configuration integrating with other services syncing elimination of repetition
  35. 35. Going the extra mile... g ! in accepting many types of input y n o formatting data & error n a recovery nd A ! pre-finding what's useful selection workG I N R integration - O syncing B reduction of repetition
  36. 36. If software development were a mathematical problem...
  37. 37. 1x Developer 16x End Users
  38. 38. 1 hour - 15 minutes x 1 developer x 16 end users
  39. 39. 1 hour in 4 hours out developer end users
  40. 40. Going the extra mile so the user doesn't have to...
  41. 41. Spotting potential points of powerful leverage
  42. 42. Spotting potential points of powerful leverage ... and pushing
  43. 43. Developer End User
  44. 44. Developer End User effort required
  45. 45. Developer End User effort required Balanced
  46. 46. Developer End User effort required High Effort Balanced High Effort for developer for end user
  47. 47. Developer End User
  48. 48. Developer End User lazy developers are lazy end users tear their hair out & die
  49. 49. Developer End User
  50. 50. Developer End User dedicated developers spend effort and their end users win big
  51. 51. "good karma, happy users, and profit" Weeee! Weeee! Weeee! Weeee! Weeee!
  52. 52. Interface != Graphical Developers are "end users" too
  53. 53. True greatness is measured by how much freedom you give to others, not by how much you can coerce others to do what you want. —Larry Wall (thanks Tim)
  54. 54. Where to push?
  55. 55. Going the extra mile... accepting many types of input formatting data & error recovery pre-finding what's useful avoiding configuration integrating with other services syncing elimination of repetition
  56. 56. Finding points of leverage accepting many types of input formatting data & error recovery pre-finding what's useful avoiding configuration integrating with other services syncing elimination of repetition
  57. 57. & anywhere there's repetition repetition repetition repetition repetition repetition
  58. 58. 1 Open email client 2 Search for emails by "Bob" 3 Look for ones with paperclips 4 Open first email, look at filename Is it the one I want? No 5 Open next email, look at filename Is it the one I want? No 6 Open next email, look at filename
  59. 59. If people are doing things over and over again, the computer should be doing it. Machines are good at repetitive tasks. —Yehuda Katz, leader of Ruby on Rails
  60. 60. & anywhere there's repetition repetition repetition repetition repetition repetietion
  61. 61. Positive Examples
  62. 62. Scripting Languages Good Frameworks
  63. 63. banana:~ amy$ git statsu git: 'statsu' is not a git‐command.  See 'git ‐‐help'. Did you mean this?   status
  64. 64. 1 Open the container. Does it have what I want? No 2 Open next next container. Does it have what I want? No 3 Open next container. Does it have what I want? No
  65. 65. 1 Open the App. 2 Go to the File menu. 3 Go to Recent Files submenu. Does it have what I want? No Yes! 4a Go look for it 4b Open it 5 Open folders... 6 Open more folders... 7 Open more folders...
  66. 66. Recipe for Success 1 Find a point of leverage
  67. 67. Finding points of leverage accepting many types of input formatting data & error recovery pre-finding what's useful avoiding configuration integrating with other services syncing elimination of repetition
  68. 68. Recipe for Success 1 Find a point of leverage 2 Push hard on it
  69. 69. dUser En elo per Dev
  70. 70. Effort dUser En elo per Dev
  71. 71. Effort Weeee! dUser En elo per Dev
  72. 72. Recipe for Success 1 Find a point of leverage 2 Push hard on it 3 ... which bends time
  73. 73. 1 hour in 4 hours out developer end users
  74. 74. Recipe for Success 1 Find a point of leverage 2 Push hard on it 3 ... which bends time 4 ... which helps everyone win
  75. 75. good karma, happy users, profit Weeee! Weeee! Weeee! Weeee! Weeee!
  76. 76. good karma, happy users, profit and a better world. Weeee! Weeee! Weeee! Weeee! Weeee!
  77. 77. Thanks. Now go out and leverage! http://slash7.com @amyhoy

×