• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
The user experience of CI systems - Penguicon 2012
 

The user experience of CI systems - Penguicon 2012

on

  • 2,432 views

Software architecture and engineering culture converge at the Continuous Integration (CI) system. It is absolutely essential that a CI system be easy to understand. Every failed test is a context ...

Software architecture and engineering culture converge at the Continuous Integration (CI) system. It is absolutely essential that a CI system be easy to understand. Every failed test is a context switch. Each test failure must be actionable, with a clear path to resolution. Unreliable or obscure tests will sow confusion and degrade confidence. Building a comprehensible, usable CI is a problem space that is new and largely unexplored by the User Experience community. I do not claim to have solved the problem. But I look forward to sharing screenshots, anecdotes, things that have gone wrong, and the story of how the color yellow turned out not to be as scary as I thought.

Statistics

Views

Total Views
2,432
Views on SlideShare
2,421
Embed Views
11

Actions

Likes
2
Downloads
9
Comments
0

4 Embeds 11

http://www.linkedin.com 7
http://tweetedtimes.com 2
https://si0.twimg.com 1
https://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The user experience of CI systems - Penguicon 2012 The user experience of CI systems - Penguicon 2012 Presentation Transcript

    • The User Experience ofContinuous Integration Systems Noah Sussman Penguicon 2012 Dearborn, MI
    • Chad Dickerson Describes the History of Etsy
    • Approximately 30 deploys a day,every business day, all year.That’s one deploy approximatelyevery twenty minutes, all day.
    • “an airport without an air traffic controller” Chad Dickerson
    • “Continuous deployment isConfidence-As-A-Service” ~John Allspaw
    • Cognitive LoadDevelopers are always maxed out.Every failed test is a context switch.
    • Busy, distracted people are not greatat making decisions.Good tools make it easy to makegood decisions under pressure.
    • Every alert, test failure and IRCmessage must have a clearlyactionable path to resolution.
    • What does it mean when a testpasses?
    • The ActiveUser Paradox
    • Users never read manualsUsers would save time in the longterm by learning more about thesystem. But thats not how peoplebehave in the real world ~Jakob Nielsen
    • Declaring aprogram“bug free,”is anentirelysubjectiveexcercise
    • Complete testing is impossible.
    • Sufficient testing is desirable.
    • So, what does it mean when a testpasses?The design of a CI system is all aboutmaking it possible to quickly makethat judgement call and to do it withconfidence.
    • What is an unstable build?Red means stop,what does yellow mean?Red is scary, yellow isn’t scary.
    • Everyone’s build process is different.Everyone’s CI is different.UX conventions for CI are few.
    • Listen to your users
    • Iteratively modify thesystem to better meetthe expectations ofyour users
    • Good tools make it easy to makegood decisions under pressure.All notifications must be actionable.We need to work toward establishinga UX design vocabulary for CI.
    • etsy.com/careers @noahsussman Mashable Cubicle Spy