Comments by "" (@ContinuousDelivery) on "How To Avoid Big Upfront Design" video.

  1. ...but since you were keeping your design options open, this should be a simple fix, of course, if you were keeping you options open, the SQL wouldn't have leaked outside the persistence code 😁😎
    4
  2. Not really, one of the key ideas that gave birth to science was that decisions from authority are not guarantee. This was firmly an enlightenment idea. As feynman said, "science is the belief in the ignorance of experts". https://en.wikipedia.org/wiki/Age_of_Enlightenment
    3
  3. I probably agree with Bryan, If these tests are high-level "executable specs" for a feature, as @gamer describes, that only say what the user should perceive at the end, then fine. If not, this really won't work well. There are lots of places that try to write SW this way, but they aren't very good at writing SW! If you have a choice, I'd look elsewhere. If you don't don't worry about adding more tests, because this is how you write good code faster, so it isn't "additional work" in the long run it is significantly less work.
    3
  4. Yup, I talk about architecture here: https://youtu.be/ElMnHDSFaCw
    2
  5. 💯
    2
  6. https://youtu.be/ln4WnxX-wrw
    1
  7. 💯💯Exactly my point! I think that the only sensible approach is to start out assuming that we are probably wrong. That focusses us on being more defensive, and so, when we find out how and where we are wrong, we can easily fix it.
    1