Okay, I'll admit I'm probably coming at this from a weird angle. My day job is building data pipelines, where everything is version-controlled, modular, and reproducible. So when I try to use Playground AI for generating synthetic test data or documentation templates, the chat-first interface honestly throws me off.
It feels like I'm having a conversation to specify a *job*. I find myself prompting, getting a result, then saying "now make it a CSV format," then "actually, make that field an integer," then "can you add 100 more rows?" It's this long, stateful back-and-forth. If I need to tweak something from three messages ago, I have to start over or try to re-explain the whole context. There's no "source code" to look back at.
What I keep wishing for is a more declarative interface, almost like a config file or a script. Something where I can define my intent, the format, the rules, in one place, run it, and get a result. If I need to change it, I edit the source and run it again. It would feel much safer and more repeatable.
For example, in my world, I'd love something like:
```yaml
generate:
object: "test_orders"
count: 1000
schema:
- name: order_id
type: uuid
- name: customer_id
type: integer
min: 1
max: 500
- name: amount
type: float
distribution: normal
mean: 50.0
stddev: 15.0
output_format: csv
```
I know the chat is great for exploration and brainstorming, which is clearly a huge use case. But for integrating into a semi-serious workflow, where you need an audit trail and reproducibility, it feels like the chat model adds friction. Maybe I'm just using it wrong? Does anyone else use it for more "engineering" tasks and have a pattern that works?
That's a completely valid perspective, honestly. You're describing a very real workflow gap. The chat paradigm assumes a linear, exploratory process, but you're right, many tasks are actually *specifications*. For repetitive generation jobs like synthetic data, you don't want a conversation, you want a recipe you can store, version, and re-run.
I wonder if the ideal is a hybrid approach. A chat interface for the initial exploration and brainstorming to figure out what you want, and then a "freeze as spec" or "export as template" button to capture the final instruction set for later reuse. Some tools are starting to offer "prompt templates" or saved custom instructions, which gets a bit closer to what you're describing.
Have you found any workarounds in your current process, or do you just grit your teeth through the back-and-forth?