Complect
It’s an archaic verb. It’s bad. Don’t do it!
This is just one post in a series of posts, ultimately building up to how I think about Cybersecurity Operations.
So far, in this series, we’ve covered:
- A High Level Overview of a Small Part of Rick Hickey’s “Simple Made Easy”
- The Difference Between Simple and Complex
- The Difference Between Easy and Hard
If you missed one of those posts, this post will have a little more context if you take a few minutes to go check them out!
Unattributed block quotes in this post belong to Rich Hickey, and are from his talk, “Simple Made Easy”.
So there’s this really cool word called complect.
It means to interleave or entwine or braid.
I want to start talking about what we do to our [Cybersecurity Operations] that makes it bad. And I don’t want to say braid or entwine because it doesn’t really have the good/bad connotation that complect has. Complect is obviously bad.
It happens to be an archaic word, but there are no rules that say you can’t start using them again, so I’m going to use them for the rest of [this series of posts].
So what do you know about complect? It’s bad. Don’t do it. Right? This is where complexity comes from: complecting. It’s very simple.
In particular, it’s something that you want to avoid in the first place.
Look at this diagram.
Look at the first one.
Look at the last one.
It’s the same stuff in both those diagrams.
It’s the same strips.
What happened? They got complected.
And now it’s hard to understand the bottom diagram from the top one, but it’s the same stuff.
So, what does any of this have to do with Cybersecurity Operations and Network Defense?
Stay tuned! On Wednesday, July 24, we’ll finally start to tie some of these ideas together and talk about what Cybersecurity Operations looks like from 30,000 feet.
