"hell no, I don't vibecode! I take pride in my craft and write things myself" said a devrel at cannes. I'm at the opposite end of the spectrum using LLMs all day and almost don't look at code anymore. here's what I do

hellno vibe coding snapshot july 2025
· use subtasks in parallel: overall speedup and LLMs are good at deciding what should be done in sequence vs at the same time in different processes

· get context and write lean PRDs: force the LLM to think longer improves everything. I was hesitant to do this after seeing @jc4p and @stephancill casting about it. turns out they are so right! taking time before writing code increases output quality A LOT and saves time to not get stuck in bug fix-vibe debugging loops later. 

· increase input speed
A) use snippets to replace keywords into expanded prompts. tiny example: /par → continue, execute subtasks in parallel if possible 
B) speech to text is fun and much faster. might require setting up some dictionary to recognize some words, but overall fast and easy

dev + founder | @vibesengineering.eth @herocast

How do you get to think longer, just prompting to do so?

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




ultrathink as keyword at each step. going from context to PRD to concrete implementation plan gave enough space to think