Keeping important code alive (SeattleJS, March 2015)

Keeping important code alive (SeattleJS, March 2015)

An exercise in Open source, psychology, and software engineering

D43e8ea63b61e7669ded5b9d3c2e980f?s=128

Charlie Robbins

March 12, 2015
Tweet

Transcript

  1. 1.
  2. 4.
  3. 8.

     A Long Time AGo In A GalaXy Far Far

    Away... OPEN SOURCE It s a Story ’ Actually ABOUT
  4. 10.
  5. 13.
  6. 16.
  7. 23.
  8. 24.
  9. 26.
  10. 28.
  11. 30.
  12. 34.
  13. 36.
  14. 41.
  15. 43.
  16. 47.
  17. 50.
  18. 54.
  19. 55.
  20. 57.

    ONCE AGAIN BACK TO OUR STORY...  WITHOUT THE ADEQUATE

    TIME TO MAINTAIN THE MODULES I WROTE...
  21. 58.
  22. 65.
  23. 67.
  24. 70.
  25. 71.
  26. 73.
  27. 76.
  28. 80.
  29. 85.
  30. 87.
  31. 91.
  32. 95.

    HIGH LEVEL PROBLEMS FIND THE TRIAGE INTO BUCKETS AND 

    NEXT-MINOR  NEXT-MAJOR  NEXT-PATCH
  33. 96.
  34. 98.

    THEN YOU CAN LAND YOUR PRS  DO NOT REFACTOR

    THE THINGS YOU HATE YET. For SeRIOUS.
  35. 99.
  36. 101.
  37. 102.
  38. 103.
  39. 108.
  40. 110.
  41. 113.
  42. 115.

    DO NOT BE AFRAID  NOT EVERYONE PAINTS THE MONA

    LISA. AND CERTAINLY NOT EVERY TIME.
  43. 116.
  44. 119.
  45. 122.
  46. 123.

    you're going to find THE TRUTHS WE CLING TO THAT

    MANY OF OUR OWN POINT OF VIEW DEPEND GREATLY ON
  47. 127.

    %06#-&%08/ %&13&$"5& (*7&"8": 45*--0/(0*/(  IT IS A PRACTICE. 

    SO DOUBLE DOWN,  DEPRECATE,  OR GIVE IT AWAY.