4 ms·
I've been looking for an opportunity to try out a pattern where the two approaches improve each other: 1. Generate a 95% accurate model 2. Use it to generate
by __MatrixMan__ 4y ago
I've been looking for an opportunity to try out a pattern where the two approaches improve each other:
1. Generate a 95% accurate model
2. Use it to generate test cases
3. Code the thing, with the help of the cases
4. Manually remove cases in the 5%
I image steps 1 and 2 being completed by a product owner and 3 and 4 being completed by a software engineer.
We're so horrifically bad at communicating a requirement's intent, I wonder what would happen if we tried to use AI to communicate them via their extent instead.
- lifeisstillgood 4y agoThat's probably genius :-) I mean ... can it be done? - build a platform (ie the data we care about and are going to build some workflow over) - have business describe what should happen in english - How does GPT build something that will run? Can it create the infrastructure? does it speak AWS? - then ... OK - I am actually excited by that
- __MatrixMan__ 4y agoI'm not familiar enough with AI workflows to weigh in on how easy or hard it would be. I've just noticed that it's much easier to describe why something is not what you want than describing what you want. So if AI can give us a mockup that's workable enough to skip the first few iterations of "no that's not what I want" and get right to the part where the engineer is asking questions about the edge cases that weren't explicit in the requirements... That's a win. I imagine you'd still want to have it in a box of some sort re: creating infra. Like you give it a very small cluster and probably make the stack decisions "write me a postgres schema for... write a fastapi API for the schema... write a react UI for the API... write me a k8s operator that up/down's the above components... Workshop the idea with other product people... ...and only then involve the engineer like: "make this AI-generated house of cards into a fortress".