summaryrefslogtreecommitdiff
path: root/_posts
diff options
context:
space:
mode:
authorBrian Picciano <mediocregopher@gmail.com>2020-11-26 21:25:19 -0700
committerBrian Picciano <mediocregopher@gmail.com>2020-11-26 21:25:19 -0700
commite346068f586b6011f3e665a552945e30dce12c25 (patch)
tree9d757cc4306e554816cdc237674d5b1a5f74e955 /_posts
parent0450e50258fa0dacfd1c651942dfd97fc3b768e6 (diff)
working out how to use longer code examples
Diffstat (limited to '_posts')
-rw-r--r--_posts/2020-11-16-component-oriented-programming.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2020-11-16-component-oriented-programming.md b/_posts/2020-11-16-component-oriented-programming.md
index 2b6d9e9..b4e08bb 100644
--- a/_posts/2020-11-16-component-oriented-programming.md
+++ b/_posts/2020-11-16-component-oriented-programming.md
@@ -6,7 +6,7 @@ description: >-
---
[A previous post in this
-blog](2019-08-02-program-structure-and-composability.html) focused on a
+blog](/2019/08/02/program-structure-and-composability.html) focused on a
framework developed to make designing component-based programs easier. In
retrospect, the pattern/framework proposed was over-engineered. This post
attempts to present the same ideas in a more distilled form, as a simple