This post was put together by Tom, his AI minions, and me. We have a really neat workflow, but the end result is lovingly hand-crafted by yours truly based on a bunch of background work. I hope you enjoy – this is the last of these posts until we get more praxis under our belts related to the theories we’re proselytizing here.
We have now covered the concept of “comprehension debt,” or where and what sorts of debt you take on when using AI in your product lifecycle. We’ve covered why it’s important to surface decision points and where to store them. Now it’s time to talk about why all of this is important, what it means about when and how to use an LLM.
Let’s get philosophical
I think one of the points of human existence and especially of science is to explore and describe a shared reality. Once a shared reality is arrived at, it can be codified and built on top of via further exploration. In Primed to Perform, they refer to this as what is “above the waterline” – EG if you blow a hole in the side of a boat, it really matters whether the hole is above or below the waterline. I believe reality is below the waterline. This is why hallucinations bother me so much, especially when based on texts that do establish a shared reality.
Continue reading

