Apps That Talk Back

Apps That Talk Back

Front End Ops Conference, San Francisco, 2014

0177cdce6af15e10db15b6bf5dc4e0b0?s=128

Rebecca Murphey

April 25, 2014
Tweet

Transcript

  1. Front End Ops Conf 2014 San Francisco • @rmurphey apps

    that 
 talk back
  2. None
  3. ˒˒˒ ➞ $$$

  4. None
  5. None
  6. None
  7. ˒˒˒ ➞ $$$

  8. apps that talk back

  9. keep you from 
 doing a bad thing

  10. None
  11. var  spawn  =  require('child_process').spawn;   var  command  =  'grunt';  

    var  commandOpts  =  ['check:push'];   ! function  onExit  (code)  {      if  (code  !==  0)  {          throw  new  Error('Prepush  check  failed  with  exit  code:  '  +  code);      }      process.exit(code);   }   ! //  Run  it  !!   var  child  =  spawn(  command,  commandOpts,  {  stdio  :  'inherit'  }  );   child.on('exit',  onExit);  
  12. BVReporter.assert(      this.componentId,        'View  '  +

     this.name  +  '  must  have  componentId'   );
  13. None
  14. None
  15. None
  16. tell you when
 you did a bad thing

  17. None
  18. None
  19. None
  20. BVTracker.error('No  productId  is  defined');

  21. BVTracker.error({      name  :  errorMessages.IMPLEMENTATION,      detail1  :

     'No  productId  is  defined',      detail2  :  component.name   });
  22. define({      errors  :  {        

     IMPLEMENTATION  :  'Implementation  Error',          API  :  'API  Error',          UNCAUGHT  :  'Uncaught  Exception',          CONFIG  :  'Configuration  Error',          THIRD_PARTY  :  'Third  Party  Service  Error',          TIMEOUT  :  'Request  Timeout',          UI  :  'User  Interface  Error',          FRAMEWORK  :  'Framework  Error'      }   });
  23. None
  24. None
  25. None
  26. “scout”  file customer  requests  component(s) core  application  file data render

     of  component  1 render  of  component  2 submission  
 interaction submission
 resources submission   render *  not  to  scale  (i  hope)
  27. “scout”  file customer  requests  component(s) core  application  file data render

     of  component  1 render  of  component  2 submission  
 interaction submission
 resources submission   render
  28. identify things before they are things

  29. None
  30. None
  31. None
  32. help fix the things

  33. None
  34. None
  35. None
  36. None
  37. priorities

  38. ✅ assertions ✅ git hooks (jshint, jscs, unit tests) ✅

    error classification & reporting ✅ production monitoring ⬆️ production debugging ⬆️ build optimization via coverage analysis ⬆️ build size monitoring ⬆️ performance instrumentation ❌ error alerting ❌ performance monitoring
  39. @rmurphey • rmurphey.com bazaarvoice.com