From 8e42fc6e6d7dace4a2ee688549f718b63a8fd20b Mon Sep 17 00:00:00 2001 From: russoj88 Date: Sun, 19 Apr 2020 15:10:20 -0700 Subject: [PATCH] Fix date. --- content/blog/complexity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/complexity.md b/content/blog/complexity.md index 5bcb4a0..eb44ae4 100644 --- a/content/blog/complexity.md +++ b/content/blog/complexity.md @@ -2,7 +2,7 @@ img: /img/complexity.jpg title: Complexity author: Jeff Russo -pdate: March 28,2020 +pdate: April 19,2020 desc: What is complexity as it relates to software? --- The most [relevant definition of complexity](https://www.lexico.com/en/definition/complex) for this blog post is: (adj) "Not easy to analyze or understand; complicated or intricate." Intuition of complexity is important if you are designing, writing, or reading software. If you are purchasing software, it is important to prioritize simpler options; it will be cheaper in the long run. In this blog post, I will discuss identifying complexity, why it's bad, why simple is good, and how software engineers manage complexity.