Steve McConnell was a software engineer who worked at organizations like Microsoft and Boeing. He served as editor-in-chief of the IEEE Software magazine between 1998 and 2002. His first book, Code Complete, published in 1993, received outstanding reviews. It went on to win the Jolt Award in the same year. He has written and published more books. Many of them best sellers and all related to the software engineering industry. He’s now the CEO of Construx Software that provides training, coaching, and consulting for software teams and organizations.
Great to see you writing again!
I wonder about the desirability of having as low an overlap as possible. I think the less overlap, the more the problem is "solved"? But if you assume you have low overlap, you won't look for nuances and improvement won't happen?
Feel like in the context of "Fuck around and find out," low wickedness means that there's nothing to find out so there's no point in fucking around. I guess whether this matters is up to what you're trying to do - if you're just trying to complete a task (exploit mode) you want low wickedness, but if you're in explore mode, you make the situation more wicked.
Also, I was thinking about Cedric's wicked and kind learning domains and how they relate to this concept.