You’ll explore the very nature of magic and reality, learn all about the legends and ancient gods and monsters that dominated prehistory, bear witness to the great Mushroom War, and heed the tale of the demon princess and the ice wizard, reading all about their lives apart and together, and their eventual transformations into the Vampire Queen and the Ice King. After that, you’ll walk through the rise of the Land of Ooo and the Candy Kingdom, witnessing all of the events that transpired after the Mushroom War, over the roughly one thousand years between the war and the first episode of the first season.
Here’s a series of events that happens many times daily on my favorite bastion of miscommunication, the bird website. Person tweets some fact. Other people reply with other facts. Person complains, “Ugh, randos in my mentions.” Harsh words may be exchanged, and everyone exits the encounter thinking the other person was monumentally rude for no reason.
While some folks in some circles make hay over “well-actuallys” and being “splained to” by “randos,” seeing such replies as bad-faith social posturing or indicative of deep-seated bias, more often than not I chalk up the friction to, like our yelling New Yorker being taken for rude, cross-cultural communication breakdown.
You just went to the Google home page.
Simple, isn’t it?
What just actually happened?
The main issues in the case of technical debt are that the product is running slowly, not scaling well, or preventing your company from getting new improvements out the door — but conceptually the product is intuitive. Technical debt is usually bad, but fixable.
On the other hand, conceptual debt happens when you’ve made design choices that lead to an unintuitive product. The product is unintuitive because you’ve chosen the wrong way to model and represent the core concepts in your system.