The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

khtan (68) [Avatar] Offline

I am using the MEAP final version of the book.

I am interested in the footnote 17, the tip on section 1.5 Summary, page 24 that
"DI must be pervasive. You can't easily retrofit loose coupling onto an existing code base",
attributed to Michael Feathers' Working Effectively with Legacy Code.

I have Michael Feathers' book; there is no mention of DI or Dependency Injection that I could find. What specific places in the book would footnote 17 be referring to?

I have an existing code base that needs to be loosened, so to speak. Hence, any information on the dangers and pitfalls like footnote 17 will help me steer out of trouble.

mark.seemann (383) [Avatar] Offline
Re: Footnote 17 : Exact attribution needed
The footnote doesn't refer to any specific place in WEwLC - that entire book is about introducing loose coupling into a legacy code base. Feathers doesn't use the term DI, but he talks a lot about Seams.

Remember that DI isn't a goal in itself, but a means toward loose coupling. This is also what WEwLC is all about.