9/10
2025 17. kitabı
“𝘈𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘵𝘩𝘳𝘦𝘦 𝘣𝘰𝘰𝘬𝘴 𝘪𝘯 𝘰𝘯𝘦: 𝘢 𝘳𝘦𝘢𝘭𝘭𝘺 𝘨𝘰𝘰𝘥 𝘪𝘯𝘵𝘳𝘰𝘥𝘶𝘤𝘵𝘪𝘰𝘯 𝘵𝘰 𝘋𝘐 𝘪𝘯 .𝘕𝘌𝘛, 𝘢𝘯 𝘦𝘷𝘦𝘯 𝘣𝘦𝘵𝘵𝘦𝘳 𝘰𝘯𝘦 𝘵𝘰 𝘋𝘐 𝘪𝘯 𝘨𝘦𝘯𝘦𝘳𝘢𝘭, 𝘢𝘯𝘥 𝘢𝘯 𝘢𝘣𝘴𝘰𝘭𝘶𝘵𝘦𝘭𝘺 𝘦𝘹𝘤𝘦𝘭𝘭𝘦𝘯𝘵 𝘪𝘯𝘵𝘳𝘰𝘥𝘶𝘤𝘵𝘪𝘰𝘯 𝘵𝘰 𝘖𝘖 𝘱𝘳𝘪𝘯𝘤𝘪𝘱𝘭𝘦𝘴 𝘢𝘯𝘥 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘥𝘦𝘴𝘪𝘨𝘯.” — Mikkel Arentoft, Danske Bank
𝗪𝗵𝘆 𝗶𝘁’𝘀 𝘄𝗼𝗿𝘁𝗵 𝘆𝗼𝘂𝗿 𝘁𝗶𝗺𝗲
• The authors show how DI connects with 𝗦𝗢𝗟𝗜𝗗 principles, familiar design patterns, and even 𝗗𝗗𝗗, making cleaner architecture easier to grasp.
• Frequent call‑outs to classics like Design Patterns and Refactoring reveal deep domain research and make each concept click.
How the authors define DI
“Dependency injection is a set of software design principles and patterns that enable you to develop loosely coupled code.”
Need an explanation fit for a five‑year‑old? The authors cite this Stack Overflow gem: stackoverflow.com/questions/16389...
𝗪𝗵𝗮𝘁 𝗲𝗮𝗰𝗵 𝗽𝗮𝗿𝘁 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘀
𝗣𝗮𝗿𝘁 𝟭 – 𝗣𝘂𝘁𝘁𝗶𝗻𝗴 𝗗𝗜 𝗼𝗻 𝘁𝗵𝗲 𝗺𝗮𝗽
Contrasts a tightly‑coupled sample (Ch 2) with a refactor to loose coupling (Ch 3). Great “aha!” moment if you still sprinkle new across your code.
𝗣𝗮𝗿𝘁 𝟮 – 𝗖𝗮𝘁𝗮𝗹𝗼𝗴
Pocket reference of DI patterns and anti‑patterns plus code‑smell checklists—I spotted a few offenders in my own projects the next day.
𝗣𝗮𝗿𝘁 𝟯 – 𝗣𝘂𝗿𝗲 𝗗𝗜
My favourite. Shows real apps wired without a container, then dives into lifetime management, decorators, interception & AOP—an eye‑opening introduction to Aspect‑Oriented Programming that felt genuinely new and inspiring. The authors even recommend 𝘼𝙊𝙋 𝙞𝙣 .𝙉𝙀𝙏: 𝙋𝙧𝙖𝙘𝙩𝙞𝙘𝙖𝙡 𝘼𝙨𝙥𝙚𝙘𝙩‑𝙊𝙧𝙞𝙚𝙣𝙩𝙚𝙙 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝙢𝙞𝙣𝙜 𝙗𝙮 𝙈𝙖𝙩𝙩𝙝𝙚𝙬 𝘿. 𝙂𝙧𝙤𝙫𝙚𝙨 for deeper exploration—now on my reading radar.
𝗣𝗮𝗿𝘁 𝟰 – 𝗗𝗜 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀
Deep dives into Autofac, Simple Injector, and Microsoft.Extensions.DependencyInjection—plus concepts like autowiring, configuration‑as‑code, and advanced
