Advertisement
Advertisement

More Related Content

Advertisement

Asakusa ruby

  1. Hello, I’m Dave @/+pragdave 2
  2. Hello, I’m a Ruby Programmer 3
  3. Hello, I’m Agile 4
  4. Hello, I’m Dave Hello, I’m a Ruby Programmer Hello, I’m Labels Agile
  5. Labels
  6. Hello, I’m Agile 7
  7. Hello, I’m Using index cards
  8. Hello, I’m Using index cards Hello, I’m Having stand- up meetings
  9. Hello, I’m Hello, I’m Using index Doing unit cards testing Hello, I’m Having stand- up meetings
  10. Hello, I’m Hello, I’m Using index Doing unit cards testing Hello, I’m Having stand- up meetings Hello, I’m Refactoring
  11. Hello, I’m Hello, I’m Using index Doing unit cards testing Hello, I’m Having stand- Hello, I’m up meetings Using Hello, I’m Cucumber!!! Refactoring
  12. Why? Because that is what the Agile Experts tell me to do 9
  13. That is not agile…
  14. Hello, I’m Hello, I’m Using index Doing unit cards testing Hello, I’m Hello, I’m That is sticking RSpec!!! Having stand- Using up meetings labels on yourself Hello, I’m Refactoring
  15. Hello, I’m a Ruby Programmer 12
  16. I need to write a web application 13
  17. y ! I need to write a b u web application R 13
  18. I need automate all my work 14
  19. y ! I need automate b u all my work R 14
  20. I need to do what is best for my customer 15
  21. y ! I need to do what is b u best for my customer R 15
  22. I need world peace 16
  23. y ! I need world peace b R u 16
  24. Ru by ! 17
  25. Ru by ! 17
  26. Ru by ! 17
  27. Hello, I’m a Ruby Programmer 18
  28. Which means… 19
  29. Which means… • I know: 19
  30. Which means… • I know: • all 90 built-in classes and modules, and/or 19
  31. Which means… • I know: • all 90 built-in classes and modules, and/or • all 143,797 Rails methods, and/or 19
  32. Which means… • I know: • all 90 built-in classes and modules, and/or • all 143,797 Rails methods, and/or • I’ve written my own testing framework 19
  33. Which means… • I know: • all 90 built-in classes and modules, and/or • all 143,797 Rails methods, and/or • I’ve written my own testing framework 19
  34. That is not a Ruby Programmer
  35. That is pouring facts into your brain
  36. Hello, I’m Hello, I’m a Ruby Programmer Agile The Problem?
  37. Hello, I’m Hello, I’m a Ruby Programmer Agile Labels are static
  38. Hello, I’m Hello, I’m a Ruby Programmer Agile No Awareness
  39. Hello, I’m Hello, I’m Using index Doing unit cards testing Hello, I’m Hello, I’m Having stand- Using RSpec!!! up meetings Hello, I’m Refactoring
  40. That is not Agile 26
  41. That is not Agile This is Agility… 26
  42. http://www.geology.smu.edu/~dpa-www/robo/nbot/nbot_gravel_1.mpg
  43. t de(t) u(t) = P · e(t) + I · e( )d + D · 0 dt 28
  44. t de(t) u(t) = P · e(t) + I · e( )d + D · 0 dt Proportional Integral Derivative 29
  45. t de(t) u(t) = P · e(t) + I · e( )d + D · 0 dt fix = current + history + future error trend
  46. fix = current + history + future error trend what “don’t how to do panic” urgent
  47. A. Where do we want to be? B. Where are we? C. How do we improve our position? 32
  48. A. Where do we want to be? B. Where are we? C. How do we improve our position? 33
  49. A. Where do we want to be? B. Where are we? C. How do we improve our position? This is Agility 33
  50. A. Where do we want to be? B. Where are we? C. How do we improve our position? This is Agility There is no more 33
  51. Hello, I’m a Ruby Programmer 34
  52. Hello, I’m a Ruby Programmer 34
  53. Instead… 35
  54. Instead… • I like to solve people’s problems 35
  55. Instead… • I like to solve people’s problems • I know how to use computers to do this 35
  56. Instead… • I like to solve people’s problems • I know how to use computers to do this • One of my (many) tools is the Ruby language 35
  57. Instead… • I like to solve people’s problems • I know how to use computers to do this • One of my (many) tools is the Ruby language • I practice Ruby-do 35
  58. Ruby-do? 36
  59. Ruby-do Object-orientation is not the only way to program 37
  60. Ruby-do Sequential code is not the only way to program 38
  61. Ruby-do “Good” code is not the only code 39
  62. Ruby-do 40
  63. Ruby-do Ruby is not the best programming language 40
  64. Ruby-do Ruby is not the best programming language (there is no “best” programming language) 40
  65. Ruby-do for item in items items.each do |item| process(item) process(item) end end 41
  66. Ruby-do name = “Dave” name = “Dave” location = “TX” location = “TX” likes = “code” likes = “code” 42
  67. 1. Que0X said February 21, 2008 at 13:04 got your point !, could you please explain advantage of learning ruby over python? python already have a huge library from web to Academia , while Ruby looks focusing on web stuff if i may tell ! what do you think ? 2. Akitaonrails said February 21, 2008 at 14:52 @que0x I say you should learn both. period. no reason to learn just 1. http://webmat.wordpress.com/2008/02/20/do-not-learn-ruby/
  68. Ruby-do • Do you practice? 44
  69. Ruby-do • Confidence comes from practice, not knowledge • Constantly look for ways to practice 45
  70. Because then… • Distrust experts • Distrust “best practices” • Distrust labels 46
  71. A Label Freezes You A Label Defines You A Label Makes You Simple
  72. Don’t Label Yourself You are what you do 48
  73. Don’t Label Yourself You are what you do 48
  74. Be a VERB not a NOUN 49
  75. Do Good! 50

Editor's Notes

  1. \n
  2. \n
  3. \n
  4. \n
  5. \n
  6. \n
  7. \n
  8. \n
  9. \n
  10. \n
  11. \n
  12. \n
  13. \n
  14. \n
  15. \n
  16. \n
  17. \n
  18. \n
  19. \n
  20. \n
  21. \n
  22. \n
  23. \n
  24. \n
  25. \n
  26. \n
  27. \n
  28. \n
  29. \n
  30. \n
  31. \n
  32. \n
  33. \n
  34. \n
  35. \n
  36. \n
  37. \n
  38. \n
  39. \n
  40. \n
  41. \n
  42. \n
  43. \n
  44. \n
  45. \n
  46. \n
  47. \n
  48. \n
  49. \n
  50. \n
  51. \n
  52. \n
  53. \n
  54. Feedback\nLooking for and applying feedback\nMinimizing the feedback gap\nTen-minute audit\nNo Broken Windows\nStaying on top of the situation\nFixing small problems before they get large\nDefer decisions\nUntil you know better\nSimplify communication\nLearn Continuously\n\nNow we will apply these ideas to the project itself\n
  55. Feedback\nLooking for and applying feedback\nMinimizing the feedback gap\nTen-minute audit\nNo Broken Windows\nStaying on top of the situation\nFixing small problems before they get large\nDefer decisions\nUntil you know better\nSimplify communication\nLearn Continuously\n\nNow we will apply these ideas to the project itself\n
  56. \n
  57. \n
  58. \n
  59. \n
  60. \n
  61. \n
  62. \n
  63. \n
  64. \n
  65. \n
  66. \n
  67. \n
  68. \n
  69. \n
  70. \n
  71. \n
  72. \n
  73. \n
  74. \n
  75. \n
  76. \n
  77. \n
  78. \n
  79. \n
  80. \n
  81. \n
  82. \n
  83. \n
  84. \n
  85. \n
  86. \n
  87. \n
  88. \n
  89. \n
  90. \n
  91. \n
  92. \n
  93. \n
  94. \n
  95. \n
  96. \n
  97. \n
  98. \n
  99. \n
  100. \n
  101. \n
  102. \n
  103. \n
  104. \n
  105. \n
  106. \n
  107. \n
Advertisement