Clean Code II – Craftsmanship – Robert Martin

Einige seiner Beispiele wiederholen sich und kommen auch bei seinen Kollegen vor. Bei seinen Folien scheint er sich strikt an DRY zu halten. D.h. die Folien sind nicht speziell für diese Conference zusammengestellt. Er springt über Blöcke um in der Zeit zu bleiben. Inhaltlich motiviert er Clean Code sehr eindrucksvoll:
  • go agile
  • there is no one plan, you need iterations
  • separate when needed
  • no grant redesigns!
  • follow the boys scout rule
  • incremental improvements
  • the only way to go fast, is to go well
  • do TDD, do short round-trips
  • go incrementally, bit by bit
  • take a look in: “working with legacy code”
  • run subsets of tests (to be fast inside your cycle and run the whole while checkin or in your CI)
  • don’t have a huge bug base. keep it below a paper page, so that is can be easily striked out
  • avoid debugging
  • manual testing is inmoral
  • definition of done
    • all tests pass
    • unit and acceptance-tests
    • nothing more needs to be done

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: