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

1. Doing the Work
Or, Amy Pretends You Care About Interface
Deisgn (But Not Really)

2. Amy
Ruby & JavaScript Developer

3. Amy
Teacher of Programming

4. Amy

5. Amy
Crusader for Cheerful Software

6. Wait—
"Cheerful Software?"

7. Wait—
"Cheerful Software?"
Are we hot-shot software developers or are we
kindergarten teachers?

8. Software should be
like a great concierge.

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. If software
development was
Magnum PI...

11. Magnum
the car
the smirk
the chest hair
the girls
the TV show
the goofy charm

12. Higgins
the resources
the control / power
the connections
the snarky jokes
the (awesome) accent
the style

13. If software
development was
Magnum PI...

15. End User

16. End User
Developer

17. Magnum
the car
the smirk
the chest hair
the girls
the TV show
the goofy charm

19. knows kung-fu

20. knows kung-fu
saves Magnum's ass

21. knows kung-fu
saves Magnum's ass
makes Magnum possible

22. If software
development were a
seesaw...

23. Developer End User

24. Developer End User

25. Seesaws
have a fulcrum (point of leverage)
go up
go down
require teamwork
and equal effort
fun?

27. Effort

28. Effort

29. Effort
Effort

31. Weeee!

32. Weeee!
Weeee!

33. And nothing says "good karma,
happy users, and profit" like end
users saying...
Weeee! Weeee!
Weeee! Weeee!
Weeee!

34. Developer End User
So, what's this here point of leverage?

35. Developer End User
Code!

36. Developer End User
Code!
(Specifically: commitment & effort)

37. Code!
Going the extra mile so the
user doesn't have to...

38. 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

39. 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

42. If software
development were a
mathematical
problem...

43. 1x Developer 16x End Users

44. 1 hour - 15 minutes
x 1 developer x 16 end users

45. 1 hour in 4 hours out
developer end users

48. Going the extra mile so the user
doesn't have to...

50. Spotting potential points of
powerful leverage

51. Spotting potential points of
powerful leverage
... and pushing

52. Developer End User

53. Developer End User
effort required

54. Developer End User
effort required
Balanced

55. Developer End User
effort required
High Effort Balanced High Effort
for developer for end user

56. Developer End User

57. Developer End User
lazy developers are lazy
end users tear their hair out & die

58. Developer End User

59. Developer End User
dedicated developers spend effort
and their end users win big

60. "good karma, happy
users, and profit"
Weeee! Weeee!
Weeee! Weeee!
Weeee!

61. Interface != Graphical
Developers are "end users" too

62. 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)

63. Where to push?

64. 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

65. 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

66. & anywhere there's
repetition repetition
repetition repetition
repetition repetition

67. 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

69. 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

70. & anywhere there's
repetition repetition
repetition repetition
repetition repetietion

73. Positive Examples

74. Scripting Languages
Good Frameworks

75. banana:~ amy$ git statsu
git: 'statsu' is not a git‐command.
See 'git ‐‐help'.
Did you mean this?
status

86. 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

88. 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...

91. Recipe for Success
1 Find a point of leverage

92. 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

93. Recipe for Success
1 Find a point of leverage
2 Push hard on it

94. dUser
En
elo per
Dev

95. Effort
dUser
En
elo per
Dev

96. Effort Weeee!
dUser
En
elo per
Dev

97. Recipe for Success
1 Find a point of leverage
2 Push hard on it
3 ... which bends time

98. 1 hour in 4 hours out
developer end users

99. Recipe for Success
1 Find a point of leverage
2 Push hard on it
3 ... which bends time
4 ... which helps everyone win

100. good karma, happy
users, profit
Weeee! Weeee!
Weeee! Weeee!
Weeee!

101. good karma, happy
users, profit
and a better world.
Weeee! Weeee!
Weeee! Weeee!
Weeee!

102. Thanks.
Now go out and leverage!
http://slash7.com
@amyhoy