<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Liskov-Substitution-Principle on ✨</title><link>/tags/liskov-substitution-principle/</link><description>Recent content in Liskov-Substitution-Principle on ✨</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 15 Mar 2019 10:00:00 -0400</lastBuildDate><atom:link href="/tags/liskov-substitution-principle/index.xml" rel="self" type="application/rss+xml"/><item><title>No substitutions for Liskov Substitution Principle (LSP)</title><link>/post/clean-architecture-with-lsp/</link><pubDate>Fri, 15 Mar 2019 10:00:00 -0400</pubDate><guid>/post/clean-architecture-with-lsp/</guid><description>In this post, we’ll explore the relationship between two concepts, ‘high level policy’ and ‘low level details’ and how the Liskov Substitution Principle bridges the gap. High level policy is a function or a set of functions that describes what needs to be done in a certain program path, whereas low level details are implementations of the dependencies that enable the high level policy. Let’s take a look at an example.</description></item></channel></rss>