Now that I, somewhat surprisingly to myself, co-run an AI-oriented software shop with Rich Ziade, I've been looking f...
Now that I, somewhat surprisingly to myself, co-run an AI-oriented software shop with Rich Ziade, I've been looking for repeatable patterns around development. AI doesn't (yet) have methodologies or processes that are reproducible and communicable—think Agile, or Kanban, or Six Sigma, which yes, can be nonsensical but at least they're SOMETHING. Despite a lot of promises, and big books of prompts, we're all wandering around a bit, constantly surprised and disappointed."
""
"This week for the Aboard newsletter I wrote about what I think is going to be a dominant pattern—it's a little wonky, but I guess one way to describe it is "re-ambiguation." (In the piece I call it "Specification Repair," it doesn't really have a name yet.)"
""
"Disambiguating inputs has been a goal of the technology industry since the first punchcards were entered, but interestingly, a lot of really effective AI involves letting the computer "talk" to itself, making lots of guesses and speculations, then letting it write code to address those guesses and speculations."
""
"To be clear: I don't have a process with a name and instructions, or a set of practices for breaking down the different phases into user stories, or tools for drawing clear lines between when the bot should add ambiguity and when it should write code. Maybe someone else does! But I do think that, when I squint, the future has a lot of this pattern in it."
""
"Bon weekend to all!"
""
"https://lnkd.in/eHD4C_uX