Youtube comments of Dean Schulze (@deanschulze3129).

  1. 145
  2. 136
  3. 105
  4. 88
  5. 42
  6. 37
  7. 27
  8. 18
  9. 18
  10. 16
  11. 13
  12. 12
  13. 10
  14. 10
  15. 10
  16. 9
  17. 9
  18. 7
  19. 7
  20. 7
  21. 7
  22. 6
  23. 6
  24. 5
  25. 5
  26. 5
  27. 5
  28. 5
  29. 5
  30. 5
  31. 5
  32. 4
  33. 4
  34. 4
  35. The claim that "It [waterfall] never really works" is demonstrably false, and Dave Farley should check before making such sweeping judgements. This is from chatGPT (I know, I know but it's better than not checking at all): The waterfall methodology, although less popular today, has been used successfully in the development of various software projects in the past. Here are a few notable examples: 1. NASA's Apollo Space Program: The development of the software systems for the Apollo space missions followed a waterfall approach. Given the mission's critical nature, the project had a well-defined scope, clear requirements, and a sequential development process, ensuring each phase was completed before moving to the next. 2. Windows Operating System: In the early stages of Microsoft Windows development, the waterfall method was employed. The development process involved distinct phases, such as requirements gathering, design, implementation, testing, and deployment. Each phase had well-defined objectives and deliverables. 3. Banking and Financial Systems: Many banking and financial institutions have used the waterfall model for developing their software systems. Projects involving core banking systems, payment processing, or risk management systems often have a stable set of requirements and a linear development approach, making the waterfall method suitable. 4. Defense and Aerospace Projects: Various defense and aerospace projects have successfully utilized the waterfall methodology due to the stringent requirements and critical nature of the systems involved. These projects often have long development cycles, requiring thorough planning, design, and documentation before implementation. 5. Large-Scale Enterprise Resource Planning (ERP) Systems: ERP systems like SAP, Oracle E-Business Suite, and Microsoft Dynamics have been developed using the waterfall method. These projects involve complex business processes, extensive customization, and integration with multiple modules, which can benefit from a structured and sequential development approach.
    4
  36. 4
  37. 4
  38. 4
  39. 4
  40. 4
  41. 4
  42. 3
  43. 3
  44. 3
  45. 3
  46. 3
  47. 3
  48. 3
  49. 3
  50. 3
  51. 3
  52. 3
  53. 3
  54. 3
  55. 3
  56. 3
  57. 3
  58. 3
  59. 3
  60. 3
  61. 3
  62. 2
  63. 2
  64. 2
  65. 2
  66. 2
  67. 2
  68. 2
  69. 2
  70. 2
  71. 2
  72. 2
  73. 2
  74. 2
  75. 2
  76. 2
  77. 2
  78. 2
  79. 2
  80. 2
  81. 2
  82. 2
  83. 2
  84. 2
  85. 2
  86. 2
  87. 2
  88. 2
  89. 2
  90. 2
  91. 2
  92. 2
  93. 2
  94. 1
  95. 1
  96. 1
  97. 1
  98. 1
  99. 1
  100. 1
  101. 1
  102. 1
  103. 1
  104. 1
  105. 1
  106. 1
  107. 1
  108. 1
  109. 1
  110. 1
  111. 1
  112. 1
  113. 1
  114. 1
  115. 1
  116. 1
  117. 1
  118. 1
  119. 1
  120. 1
  121. 1
  122. 1
  123. 1
  124. 1
  125. 1
  126. 1
  127. 1
  128. 1
  129. 1
  130. 1
  131. 1
  132. 1
  133. 1
  134. 1
  135. 1
  136. 1
  137. 1
  138. 1
  139. 1
  140. 1
  141. 1
  142. 1
  143. 1
  144. 1
  145. 1
  146. 1
  147. 1
  148. 1
  149. 1
  150. 1
  151. 1
  152. 1
  153. 1
  154. 1
  155. 1
  156. 1
  157. 1
  158. 1
  159. 1
  160. Farley starts out by saying that feature branches are bad. Everyone should commit to the same branch (the trunk). I can see some benefit to that. It may reduce merge conflicts. But then he goes from talking about the problems with pull requests to advocating pair programming. If pair programming is as beneficial as he claims it would be widely used. That goes for the other fads that consultants push, like TDD. Uncle Bob Martin used to go around saying the TDD would become the minimum standard for professional conduct in software engineering. He likened it to surgery with and without anesthetic. Maybe you've notice that uncle Bob hasn't been as vocal about TDD defining the boundary between professionals and amateurs. That change happened when I called him out on one online forum and asked him point blank if he considered Linus Torvalds and Peter Norvig to be amateurs because they didn't practice TDD. The dirty, unspoken secret of pair programming is that it comes with mandatory hours. There's a company that does real estate analytics that I really wanted to work for because I love real estate. Their recruiter called me and told me, with resignation, that they had hired Pivotal to setup their software development process and Pivotal had mandated PP with mandatory hours of 10 - 6. She said that she had not been able to hire any developers who wanted to work under that regime. I told her that I wouldn't be a good fit for that regime either. Now maybe Pivotal was being crazy like a fox. They dictated a regime that no one wanted to work under, so this company would be left with no other choice but to outsource their software development. Maybe to a company like Pivotal. Maybe there are problems with PRs, but there are much bigger problems with PP. And PP advocates don't want to discuss them publicly.
    1
  161. 1
  162. 1
  163. 1
  164. 1
  165. 1
  166. 1
  167. 1
  168. 1
  169. 1
  170. 1
  171. 1
  172. 1
  173. 1
  174. 1
  175. 1
  176. 1
  177. 1
  178. 1
  179. 1
  180. 1
  181. 1
  182. 1
  183. 1
  184. 1
  185. 1
  186. 1
  187. 1
  188. 1
  189. 1
  190. 1
  191. 1
  192. 1
  193. 1
  194. 1
  195. 1
  196. 1
  197. 1
  198. 1
  199. 1
  200. 1
  201. 1
  202. 1
  203. 1
  204. 1
  205. 1
  206. 1
  207. 1
  208. 1
  209. 1
  210. 1
  211. 1
  212. 1
  213. 1
  214. 1
  215. 1
  216. 1
  217. 1
  218. 1
  219. 1
  220. 1