Unsustainable promptomancy

The overlords of silicon blessed us with the newest messiah, the parrot. They only had to scrape the entirety of the known cyberspace to create it. The parrot is then able to recite from phrases, inputs, from a prompt. But there is only so much the parrot is able to ingest before it loses the thread. Even when the bite is the perfect size it can’t answer anything else than a slightly tweaked genericism. It is an amalgamation of all there is. If generic is the most common among the all it becomes the most probable.

And now it’s expected we use it for system crafting. Otherwise, they’re going to leave us in the past, they say. Proud promptomancers are spawning swarms of parrots, meanwhile burning tokens, energy, the Planet. So proud, yet so unaware; losing all context, knowledge, control in performing the rituals. But the parrot will know! It will file the knowledge! It’s small span can only take so much.

Think of a system as a realization of specification. How would any working software be than possible when abysmal documentation is so common, and comments in code are so few. The code itself is the minimal spec! The minimum that is understandable to a programmer and interpretable by a machine. If that’s true, what’s the point in using the parrot? Feed it badly and it’s going to stink. Prepare the minimal spec and you already wrote it yourself.

The apostles say “it writes the code faster!” Typing out a spec was never an issue. Coming up with a good system is an issue! A system crafter needs to understand in and outs to be able to present a meaningful and helpful interpretation. Leaving it out of the loop, leaving it up to the parrot can’t end well.

I say good luck to the Promptomancer! They’ll need it.

Meanwhile the Planet burns…