<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dip on wid's blog</title><link>https://wid-blog.github.io/en/tags/dip/</link><description>Recent content in Dip on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 23 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/dip/index.xml" rel="self" type="application/rss+xml"/><item><title>Layered Architecture and Dependency Inversion</title><link>https://wid-blog.github.io/en/posts/tech/architecture/layered-architecture/</link><pubDate>Fri, 23 Feb 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/architecture/layered-architecture/</guid><description>Layered architecture separates code into horizontal layers by technical responsibility. A summary of the four-layer structure, dependency direction rules, and how DIP decouples layers.</description></item><item><title>Dependency Injection — The Hierarchy of DIP, IoC, and DI</title><link>https://wid-blog.github.io/en/posts/tech/design-pattern/dependency-injection/</link><pubDate>Thu, 25 Jan 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/design-pattern/dependency-injection/</guid><description>DIP (principle), IoC (pattern), and DI (technique) sit at different levels of abstraction. The hierarchy must be clear before framework features and design principles can be told apart.</description></item></channel></rss>