DbC Design by Coding - Allen Holub

แชร์
ฝัง
  • เผยแพร่เมื่อ 14 มิ.ย. 2024
  • Breakout session from DevWeek 2015
    devweek.com/
    DevWeek is the UK’s leading conference for professional software developers, architects and analysts. With insights on the latest technologies, best practice and frameworks from industry-leading experts, plus hands-on workshop sessions, DevWeek is your chance to sharpen your skills - and ensure every member of your team is up to date.
    Please visit devweek.com/ for information on the latest event.
    ---------------------------------------­­---------------------------------------­-­----
    DevWeek is part of DevWeek Events, a series of software development conferences and workshops, including DevWeek's sister conference 'Software Architect' (software-architect.co.uk/), brought to you by Publicis UK.
    ---------------------------------------­­---------------------------------------­-­----

ความคิดเห็น • 8

  • @BryonLape
    @BryonLape 7 ปีที่แล้ว +2

    I guess I remain the weird one. I don't want to read your code, no matter how wonderful and beautiful it is, to understand how it works. Give me your API docs. If I have more questions, then perhaps I will read it. I should not have to read your damn code to use it.

    • @houssemzaier
      @houssemzaier 7 ปีที่แล้ว

      You're a big fan of A.Holub I think, every time I watch one of his videos I find your comments :)
      could you recommend some must read books for OO design and Agile(agility)

    • @BryonLape
      @BryonLape 7 ปีที่แล้ว

      I'm not sure I'm a fan as much as I am intrigued by some of his ideas.

    • @lytecyde
      @lytecyde 7 ปีที่แล้ว +4

      "Growing OO programs with TDD", "Junit in action", "TDD explained" also look into design thinking, look a the criticism of SCRUM

    • @migoy
      @migoy 5 ปีที่แล้ว +1

      If you have test suite, arent they better than the api docs or serves even better(just my thoughts)?

    • @andres.a.traves
      @andres.a.traves ปีที่แล้ว +2

      The interface is the API docs. You have the type signatures and you can add javadoc style comments on every definition. There you have the API docs. You don't need to read the actual implementation. Nobody wants to read implementations in order to understand how to use an API. This is what Allen is trying to point out.