TDD, Refactoring and Dependency Injection

TDD, Refactoring and Dependency InjectionShort Description
Previous-era architects and stake-holders suggest that the only way to write software was after an exhaustive period of design. Latterly known as - “big up front architecture”. Craig Larman’s keynote cited plenty of evidence for this amongst other things being both problematic and perpetuated as a fact even today.

Website: paulhammant.com | Filesize: 3881kb
No of Page(s): 41

Content

Agile suggests embracing change is the key to success .. .. yet how do we convince process and control-drunk stake-holders that we are adept at embracing design change while building complex applications without a detailed prescriptive architecture?


Test Driven Development
• You write the unit-test BEFORE you write the implementation code - no exceptions.
• As a practice it helps drive design
• Many other methodologies cherry-pick from Agile …. but never TDD
• Also read up on Behaviour Driven Development

Get the file Download here

AddThis Social Bookmark Button
Related Books:
  • Introduction to Refactoring
  • An introduction to Software Refactoring
  • Refactoring Code in Visual Studio 2005
  • Refactoring, The Process
  • Analysis and Definition of a Language Independent Refactoring Catalog
  • Refactoring as Meta Programming
  • Binary Refactoring Improving Code Behind the Scenes
  • Refactoring Tactics and Strategies The Refactory Principals

  • Related Searches: , , , ,



    Comments

    Leave a Reply