Problem: Thanks to the amazing book Dependency Injection in .Net, but Mark Seemann, I recently learned how to use automatic dependency injection, but I experienced a lot of friction with my existing object designs and my approach to object construction. Why is that? Well, it has to do with my personal history, and the gaps in my education.
September 16, 2010
September 6, 2010
I found a great new book on Dependency Injection and Architecture
The book is a work in progress, by Mark Seemann, to be published by Manning Publications. It is entitled Dependency Injection in .Net. This book fills in a serious gap my software development education by explaining how automated dependency injection can help improve testability and composability of modules. It shows me both how to do something (with compilable sample code), and it also shows me why things are done (the resulting benefits). I love this book. It is by a real programmer, about a really important topic. And I’m learning a lot of stuff I can use in my daily programming work (more…)
September 2, 2010
Why do we write acceptance tests before we code?
Topic: Acceptance tests as requirements
Thesis: We should write acceptance tests before we accept a story for development. The story is not ready for coding until acceptance tests have been developed (or at least started). (more…)