Discussion about this post

User's avatar
Godwhacker's avatar

10 Top Vibe Coding Tips for Humanities Graduates (from an actual programmer):

1. Use Claude Opus because it's considerably less likely to go off the rails than any other model out there. You have to pay for it, but it's a choice between paying for something that works and paying for something that doesn't.

2. Understand the pricing. You get a certain number of 'tokens', and every action- planning, asking, writing code- costs tokens based on how much thinking is required. Typically, writing code costs the most; asking and planning cost less, but it can be a bit fuzzy.

3. Use the different modes so you're not wasting time and money or destroying the planet for nothing. Always start in "plan" mode, tell it what you want, then review the plan. If you don't understand something, switch to "ask" mode, then modify the plan as required. Only switch to 'agent' mode when you've got a plan, you understand the plan, and the plan looks like it will give you what you want.

4. Be as specific as possible. Tell it exactly what you want in as an exhaustive manner as you can.

The more you leave unspecified, the more it will fill in the blanks with guff. If you're not sure what you want then get it to plan and build a *very simple* prototype, review that, and then make modifications accordingly. Switch back to plan mode if it goes off the rails. Once the prototype is to your liking, you may want to start again fresh so there's no incidental weirdness hanging around. Vibe coding has a tendency towards entropy- the chance of it going off the rails increases as time goes on and complexity increases.

5. When giving it prompts, focus on the implementation as much as possible- how it should look, how it should behave, what sections, etc. Don't tell it about your brand identity or how users should feel when they see Horse Uber or whatever you're asking it for, it can't actually do anything with that.

6. After every three or four prompts, get it to compress its context down. Context is basically memory. It will compress automatically when the context gets full, but it's better that you get it to do it between tasks.

7. Get the right tools- if you're on Mac you'll have a terminal already, but if you're on PC you will want to download something like Cmder which is a lot nicer than PowerShell. Use Git or don't bother doing the project- you will want to save progress and be able to revert back in case of madness. If you don't know about Git, go and learn about Git. GitKraken is a very good Git client. You'll also want to get something like VSCode because you don't want to start trying to view code in Word.

8. Manage your expectations- you are not going to get your peer-to-peer dogging app up and running in an afternoon, doubly so if you don't know what you're doing. These tools are about 100 times more effective for people with actual programming experience because they can give the AI better instructions, keep it on a tighter leash, and spot where it's gone wrong.

9. If you want to do anything unusual or weird, it'll probably screw up. If you want to build something that's been built a thousand times before, it'll probably do it in one go. So, try and keep it simple.

10. If you're doing anything even vaguely related to taking payment, go and get a proper programmer to do it, or all your money will end up in Russia. There's a chance that will happen even if you *do* hire a programmer, but at least you'll have someone to sue.

Hope that helps. I've changed my mind about these tools since Claude Opus. I still kind of hate them, but they do enable some pretty amazing stuff.

They're crap at writing though. I typed all of that in a Teams call I'd been pointlessly added to.

David's avatar

Not sure where I heard it (The News Quiz?) but I particularly like: The Andrew formerly known as Prince.

40 more comments...

No posts

Ready for more?