Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How Vs Why

How Vs Why

A little dive into why the Why is greater than the How. This talk was given at MagmaConf on June 7, 2013

Ba4b0b302231bffb0f685bbef25db0d6?s=128

Bryan Liles

June 17, 2013
Tweet

More Decks by Bryan Liles

Other Decks in Technology

Transcript

  1. @bryanl How versus Why ... Monday, June 17, 13

  2. @bryanl Hola! Monday, June 17, 13

  3. @bryanl Monday, June 17, 13

  4. @bryanl Introduction Monday, June 17, 13

  5. @bryanl Monday, June 17, 13

  6. @bryanl How is good Monday, June 17, 13

  7. @bryanl Why do you use Emacs? Monday, June 17, 13

  8. @bryanl Why do you use Vim? Monday, June 17, 13

  9. @bryanl Why do you use Sublime Text? Monday, June 17,

    13
  10. @bryanl Why do you use Rubymine? Monday, June 17, 13

  11. @bryanl Why do you Test? Monday, June 17, 13

  12. @bryanl Monday, June 17, 13

  13. @bryanl Why do I Test? Monday, June 17, 13

  14. @bryanl How vs Why in ... Monday, June 17, 13

  15. @bryanl How vs Why in Ruby Monday, June 17, 13

  16. @bryanl Convention Versus Configuration Monday, June 17, 13

  17. @bryanl Rails Router Monday, June 17, 13

  18. @bryanl SOA Monday, June 17, 13

  19. @bryanl How vs Why in Software Development Monday, June 17,

    13
  20. @bryanl Mac Versus Everything Else Monday, June 17, 13

  21. @bryanl RFC 2616 Monday, June 17, 13

  22. @bryanl Monday, June 17, 13

  23. @bryanl Creating awesome software Monday, June 17, 13

  24. @bryanl How vs Why in Software Developers Monday, June 17,

    13
  25. @bryanl How do we get more women in software development?

    Monday, June 17, 13
  26. @bryanl How do we get more minorities in software development?

    Monday, June 17, 13
  27. @bryanl How do we get more _____________ in software development?

    Monday, June 17, 13
  28. @bryanl How vs Why in The Real World Monday, June

    17, 13
  29. @bryanl Want to be a better developer? Monday, June 17,

    13
  30. @bryanl Code like Indiana Jones Monday, June 17, 13

  31. @bryanl No such thing as bad code... Monday, June 17,

    13
  32. @bryanl This is Important Monday, June 17, 13

  33. @bryanl How do I take advantange of this? Monday, June

    17, 13
  34. @bryanl 1. Iterate on idea 2. Fail miserably 3. Pivot

    4. ... 5. Profit? Monday, June 17, 13
  35. @bryanl How < Why Monday, June 17, 13

  36. @bryanl Why > How Monday, June 17, 13

  37. @bryanl More $$$ == More Success Monday, June 17, 13

  38. @bryanl Understanding builds trust Monday, June 17, 13

  39. @bryanl More trust == More speed Monday, June 17, 13

  40. @bryanl More understanding == More speed Monday, June 17, 13

  41. @bryanl More speed == More $$$ Monday, June 17, 13

  42. @bryanl Understanding Why == More $$$ Monday, June 17, 13

  43. @bryanl In conclusion ... Monday, June 17, 13

  44. @bryanl ¡Es un gran momento para ser un Rails developer!

    Monday, June 17, 13
  45. @bryanl ¡Es un gran momento para ser un Web developer!

    Monday, June 17, 13
  46. @bryanl ¡Es un gran momento para ser un developer! Monday,

    June 17, 13
  47. @bryanl How is Good Monday, June 17, 13

  48. @bryanl Why is Great Monday, June 17, 13

  49. @bryanl The only way to discover the limits of the

    possible is to go beyond them into the impossible. - Arthur C Clarke Monday, June 17, 13
  50. @bryanl Difficult takes a day, impossible takes a week. -

    Jay Z Monday, June 17, 13
  51. @bryanl Test all the fucking time... - Bryan Liles Monday,

    June 17, 13