As someone who actually works with stories and writing, I can tell you, it's not easy. — Christoffer
Sorry, I meant from an abstract programming design point of view as to what constitutes "a story". I believe you.
You still cannot generate something that flows as a story with just a basic input/output mechanic as you described before. — Christoffer
I'm suggesting, again from a programming point of view (I am doing that as we speak) that one can easily
program the very intricate subtleties of what makes a great story following a relatively multipurpose and reusable (hence simple) coding function. That is to say it is physically possible for someone with enough time and expertise to create such a function, albeit not like what we see here.
Creating a great story takes skill, however I do believe in the idea that many things can be simplified yes it does lose defining qualities but still keeps its "essence" or innate quality ie. accuracy. What is a plot? Something happening. Some things are unlikely or simply cannot happen depending on the constants of the query ie. a story about a fish cannot take place in a bank but can underwater. Your request "write a story about why X doubts Y can be Z" for example.
X = Me
Y = robots
Z = must be (V)
V = only inputs and outputs (not equal, less than something)
Known (conflict): X believes Y is (Z)
Action (intro): Create reason why X believes Z about Y
Plot Options (resolution): X changes state (doubt to belief)/Y changes state (perceived to be/not be V)
Known: Y is a robot that is/is not Z.
Action (resolution): X meets a robot that is in fact Z.
Plot Options (filler): X (gradually, of course) changes state (doubt to belief)
Ending: Lesson learned, conflicts resolved.
I believe you wholeheartedly as to the complexities of the art of storytelling. Just, as I've been accused of on more than one occasion, sometimes, you really can just throw in witty things other people have said where it seems to fit and get a standing ovation. I have much respect for stories and their tellers. This could not be farther from anything other than a general observation applied under the context of programming philosophy. However yes I did hear a quote once that stuck with me. "Movies are designed for two audiences: male and female. Male-oriented movies the viewer is "chasing" something (Indiana Jones and the treasure, Borne Identity and the antihero). Female-oriented movies the viewer is "protecting" something (Titanic and the relationship, The Notebook and "eternal love", etc). We all have base emotions/fears/goals that don't take a lifetime of studying the human condition to know how to target.
I generally get the sense that you play the "unimpressed" person for some reason, like if the engineers who worked on this didn't achieve something monumental as a milestone for AI. — Christoffer
I think it's important to keep perspective. Perhaps it's only natural for man to belittle that which he fears or doesn't understand. I much enjoyed conversing with you, hope to again soon.