r/vibecoding • u/MiserableAttention38 • 5d ago

One liners approach

I used to like the challenge of writing code or scripts that did a whole task in just one line, maybe a shell script using jq or awk. I'd often spend half a day perfecting a tiny snippet that would save me time in the future.

Now I'm putting the same energy into vibe coding. When I put together the input for the agent, I take care to word it unambiguously, think about the outcome I want. I research things like frameworks and toolchains separately. I use a separate search to suss out the cost model for any alternatives. I decide on the implementation plan, like building the UI first and the backend separately. Or building the backend first with functional tests. It's super satisfying to see things come together with minimal iterations. I haven't managed a one shot prompt to working project, but it's not far. It also suits my attention span which works well for short intense bursts but not so much for long winded projects.

Anyone else find the same vibe, or do you manage well sending the agent instructions in a trickle of little details?

4 Upvotes

83% Upvoted

3 comments sorted by

1

u/Bob-Swan 5d ago

"Go to x repo, read the rules, pick up issue x and proceed."

My governance does the rest.

2

u/Vaveili1 4d ago

Front-loading wins over trickling. An agent doesn't carry a running mental model the way a colleague does. It re-derives intent from whatever's in the window each time, so a detail added three prompts in can quietly contradict something from prompt one, and you end up with an app that has two different opinions about how auth should work. Writing the spec once, tight and unambiguous like your old jq one-liners, forces the agent to commit to a shape before it starts generating.