Minor fixes.
This commit is contained in:
parent
a91c3c36b0
commit
f83b6725e9
@ -8,7 +8,7 @@ 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.
|
||||
|
||||
## Identifying Complexity
|
||||
Before being able to manage complexity, it must be identified. In addition to the definition it is helpful to know indicators and examples. Seasoned engineers sometimes call these smells; complexity is not black and white, but more of an intuition. Some things that are simple now will be come complex in the future.
|
||||
Before being able to manage complexity, it must be identified. In addition to the definition, it is helpful to know indicators and examples. Seasoned engineers sometimes call these smells; complexity is not black and white, but more of an intuition. Some things that are simple now will become complex in the future.
|
||||
|
||||
#### Indicators
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user