Fix date.
This commit is contained in:
		@@ -2,7 +2,7 @@
 | 
				
			|||||||
img: /img/complexity.jpg
 | 
					img: /img/complexity.jpg
 | 
				
			||||||
title: Complexity
 | 
					title: Complexity
 | 
				
			||||||
author: Jeff Russo
 | 
					author: Jeff Russo
 | 
				
			||||||
pdate: March 28,2020
 | 
					pdate: April 19,2020
 | 
				
			||||||
desc: What is complexity as it relates to software?
 | 
					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.
 | 
					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.
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user