3 ms·

One of the issues with vibe coding vs. outsourcing agencies is the sheer volume of code it can produce in a short amount of time. I vibe-coded a simple helper

One of the issues with vibe coding vs. outsourcing agencies is the sheer volume of code it can produce in a short amount of time. I vibe-coded a simple helper script. If I wrote it myself it would have been 1/3rd the lines, not covered most edge cases (some of which were completely irrelevant, some of which actually useful), and it would have taken me way longer than just checking if the vibe-coded code works (this was the "either it works or it doesn't" kind of task, not something where subtle errors could reasonably be introduced). I skimmed the code and removed the line that deletes temp files to reduce the risk that it accidentally wipes my home dir and ran it. As I was trying to work with the data deeper, I noticed missing temp files, and realized that there were two other temp file deletion lines that I missed. It's simply too much code for a human to reasonably read, but the speed benefits are real. (My plan for the future is not reading the code more carefully, it's putting it in a sandbox and letting the AI play.)

DevDesmond 1y ago
I like to keep a personal recipe book of prompt modifiers. For bash scripting I often write my prompt and then copy-paste the following to prompt: ``` When making edits to the script, ensure the script remains - Idempotent - Functional after a fresh install of a virtual machine Additionally, keep things stupid simple and avoid: - Unnecessary error checks - Defining colors and custom logging functions - Bells and wistles - Backups - Branching Paths - Script Arguments ``` I find it helps cull back the LLM 's overenthusiasm for abstractions.
- SOLAR_FIELDS 1y ago
  In general I usually toss “follow KISS principles” into nearly every plan prompt. If you tell it that, it helps cut out a lot of the noise and only focuses on the core functionality
- dotancohen 1y ago
  I'd love to see some more of that recipe book. If you don't want to share here, my Gmail username is the same as my HN username. Thank you!
  - mattmanser 1y ago
    Try this one, it works 100% of the time: X. Don't write stupid code. Replace X with your prompt.

DevDesmond 1y ago

I like to keep a personal recipe book of prompt modifiers. For bash scripting I often write my prompt and then copy-paste the following to prompt: ``` When making edits to the script, ensure the script remains - Idempotent - Functional after a fresh install of a virtual machine Additionally, keep things stupid simple and avoid: - Unnecessary error checks - Defining colors and custom logging functions - Bells and wistles - Backups - Branching Paths - Script Arguments ``` I find it helps cull back the LLM 's overenthusiasm for abstractions.

SOLAR_FIELDS 1y ago
In general I usually toss “follow KISS principles” into nearly every plan prompt. If you tell it that, it helps cut out a lot of the noise and only focuses on the core functionality
dotancohen 1y ago
I'd love to see some more of that recipe book. If you don't want to share here, my Gmail username is the same as my HN username. Thank you!
- mattmanser 1y ago
  Try this one, it works 100% of the time: X. Don't write stupid code. Replace X with your prompt.