When you’re vibe coding, you need to narrate long prompts, including things like “And remember not to hallucinate or make any errors.” All that is a lot faster to say than type.
Clearly, you’re not vibe coding, and your job will be (checks notes) automated away by someone with a #grindset.
If youre not using a custom instruction that brute forces different ways to try to get the other model not to fuck uo youre doing it wrong. If that doesn’t work, add another llm into the pipe
Edit what is a token and why is my boss sending me angry emails
God how i wish anyone I worked with understood throwing bodies at every problem doesn’t mean it gets fixed faster. On the the other end of problems, they don’t understand a developer can’t just start developing on immediately on complex application.
Can someone, anyone, tell me where it is that you work where input speed is the bottleneck in software development?
Because I have genuinely never worked at any company where the main thing holding up development was that developers weren’t typing fast enough.
When you’re vibe coding, you need to narrate long prompts, including things like “And remember not to hallucinate or make any errors.” All that is a lot faster to say than type.
Clearly, you’re not vibe coding, and your job will be (checks notes) automated away by someone with a #grindset.
/s, in case that wasn’t obvious.
If youre not using a custom instruction that brute forces different ways to try to get the other model not to fuck uo youre doing it wrong. If that doesn’t work, add another llm into the pipe
Edit what is a token and why is my boss sending me angry emails
It’ easy to convince management it is
Unless they’re aware of The Mythical Man-Month
God how i wish anyone I worked with understood throwing bodies at every problem doesn’t mean it gets fixed faster. On the the other end of problems, they don’t understand a developer can’t just start developing on immediately on complex application.
God being in project orient work is a pain.