6 ms·
Vibe coding tips and tricks
- moolcool 1y agoAI is cool and all, but the biggest thing that makes me think that we’re in a bit of a bubble is seeing otherwise conservative organizations take “vibe coding” seriously
- NitpickLawyer 1y ago> otherwise conservative organizations take “vibe coding” seriously Eh, it might be just someone wanting to jump on a trendy term, without understanding it properly. The file actually makes good points about moving from vibes to structure, which is fine. Amazon also has their own clone of vscode (who doesn't these days) that focuses on some things mentioned here as well. They take your prompt and get it through a process of documenting - clarifying - planning, leading to solid results in the end. The problem with their approach is that it's nothing particularly "proprietary" and you can pretty much have the same experience with some slash commands and dedicated prompts in any other code assistant.
- moolcool 1y agoI don't doubt that the tooling and documentation are fine. "Vibe Coding" is a goofy and unserious practice though. The headline reads like "Oracle Best Practices to Hit the Griddy"
- taormina 1y agoThey get paid the more vibe coding occurs on their platform, so of course they have a two-pizza team dedicated to milking the latest trend.
- esafak 1y agoFollowers gonna follow.
- alfalfasprout 1y agoThere is massive financial incentive for them to make it happen for AWS. Between selling more bedrock usage or cutting their own headcount.
- NitpickLawyer 1y agoEven though they are using the wrong term here, the advice throughout the file is solid. I find it funny that it doesn't even mention kiro, which is amazon's take on a vscode clone, that focuses on processes instead of vibes.
- colesantiago 1y ago> "Thoroughly review and understand the generated code" That isn't vibe coding though. Vibe coding means you don't look at the code, you look at the front / back end and accept what you see if it meets your expectations visually, and the code doesn't matter in this case, you "see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works." [1] If the changes are good enough, i.e. the front/backend works well, then it's good and keep prompting. You rely on and give in into the ~vibes~. [1] [1] https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383
- kevindamm 1y agoMaybe the zeroth tip is "never go full vibe coder." It can be tempting, but there's so much impact that even small changes to the code can have, and often in subtle ways, that it should at least be scanned and read carefully in certain critical parts. Especially as you near the point where hosting it on AWS is practical. Even in Karpathy's original quote that you referenced he says "It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding." Maybe it should have been called vibe prompting.
- nzach 1y ago>Provide detailed specifications for the work to be done I've been playing around with vibe coding for a few months and my experience doesn't really match this advice. I used to think this was the correct way and based on that was creating some huge prompts for every feature. It took the form of markdown files with hundred of lines, specifying every single detail about the implementation. It seems to be an effective technique at the start, but when things get more complex it starts to break down. After some time I started cutting down on prompt size and things seem to have improved. But I don't really have any hard data on this. If you want to explore this topic one thing you can do is to ask you LLM to "create a ticket" for some feature you already have, and try to play around with the format it gives you.
- browningstreet 1y agoI have found it better to have stronger scope for 2nd and 3rd iteration feature sets in mind.. refactoring because you didn't think you'd be adding a certain kind of feature or filter or database scope is worse than knowing ahead of time that's where you were going. A little different than "spec", but one-shotting things works great if that's going to get you as far as you want to go. If you're adding neat-o features after that, it can get a little messy because the initial design doesn't bend to the new idea. Even something like adding anti-DDOS libraries towards the end, and then having to scope those down from admin features. Much better to spec that stuff at the outset.
- energy123 1y agoHow does it break down? Is it because the LLM didn't follow what you wrote down?
- nzach 1y agoIt is mostly because it creates code that is way more complex than it needs to. One, admittedly silly, example is Claude trying to put a light/dark theme switcher when you are trying to refactor the style of your small webapp. I'm not against a theme switcher, but it is certainly not a trivial feature to implement. But Claude doesn't seem to understand that. And by having simpler prompts I feel it gets easier to steer the LLM in the right direction.
- asdev 1y agoThis is not vibe coding at all, this is reviewing AI generated code
- arresin 1y agoBro you’re harshing the vibe
- blibble 1y agothe page is an interesting display of a very large bureaucratic institution that is extremely worried about being sued, but is still utterly desperate to get in on the AI bubble before it pops
- francisofascii 1y agoIt's too bad the "vibe coding" definition is so strict. You could have an app that was completely AI generated, but the moment you even peak at the generated code or make a small revision, it is no longer a vibe coded app.
- pinoy420 1y ago[dead]
- Wowfunhappy 1y agoI think that's an overly strict definition. A CGI film is still a CGI film even if artists at the studio hand-paint certain objects in certain frames. A Python program is still a Python program even if it calls out to C code for a handful of key functions. I suspect most people would consider an AI generated image to still constitute AI art even if the creator touched up a few things in Photoshop.
- Sateeshm 1y agoIt has to be a strict definition because that is the main point of vibe coding, it is for people who don't know how to program.
- 1y ago
- the_af 1y ago> "Warning Never blindly trust code generated by AI assistants. Always: - Thoroughly review and understand the generated code - Verify all dependencies - Perform necessary security checks." This of course makes sense, but is not vibe coding. I suppose we'll see an effort to steer people away from vibe coding nonsense by redefining the term, which makes sense.
- oceanhaiyang 1y agoI really don’t see how vibe coding has any place here. It’s just writing bad code without knowing anything it does.
- cowlby 1y agoI'm starting to think of "vibe coding" as "peer/pair programming". How effective it will be depends on how effective I am as the peer reviewer. The driver is the AI who is highly capable but has a 5% chance of doing something psychotic lol. Me, the peer, can either review carefully and catch errors or just relax and "vibe" through it all. Results will of course vary based on that relationship.
- 9rx 1y ago"Vibe coding" was intended to mean where you don't pay attention to the work your partner creates at all. Where you just lean into their "vibe" and run with it, no matter how bad it actually is. What you describe already has a name. You even mentioned it yourself. Also calling it "vibe coding" would be a bit redundant.
- michelsedgh 1y agoNo Vibe Coding is when you dont touch the code yourself and only ask the LLM to make edits for you. You still understand and make sure llm does what you asked, but you dont touch the code yourself.
- 9rx 1y agoThat wasn't the original intent. It was described as "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists". It may have come to mean what you describe to some, but that's more commonly what we call managing a junior engineer. As before, no need for redundancy.
- xyst 1y ago"Vibe coding" used to be a meme and used as a derogatory term. Odd to see it adapted as the norm now.
- DaiPlusPlus 1y agoML pros call it "Semantic Diffusion", with a smirk, I assume. https://simonwillison.net/tags/semantic-diffusion/ https://simonwillison.net/tags/semantic-diffusion/
- dolebirchwood 1y agoLemmings all the way down... I look forward to the day when AI really can do all coding and replace every single human programmer on the face of the Earth, for no other reason than that I will no longer have to see this insidious phrase ever again.
- h4ck_th3_pl4n3t 1y agoOur species is called hu-man for a reason, which means "being that forgets". And this will be the achilles of our future generations.
- zppln 1y agoOn a slightly related note... I'm kind of out of the loop wrt coding with AI. I was trying to find some youtuber working on some interesting project using AI to get a feel for how useful it could be but didn't have much luck (I didn't get past the "top 10 AI tools to use for coding" style videos). I was thinking something in the style of tsoding if you're familiar with his projects.
- mchinen 1y agoI recorded myself trying it out to port some old apps of mine using Claude code as a first time user of it. I'm not even a youtuber and make these to keep myself accountable, so it's not that fun to watch, but it might be in the direction of your query: https://www.youtube.com/watch?v=d9YCkWjD7WQ&list=PLEWSTtjNAwKkjlWwLjVbUVrzcSJKH1ydv&index=5 https://www.youtube.com/watch?v=d9YCkWjD7WQ&list=PLEWSTtjNAw...
- zppln 1y agoLooks promising! Thanks for sharing!
- wahnfrieden 1y agohttps://x.com/steipete https://x.com/steipete https://steipete.me/posts/2025/essential-reading-july-2025 https://steipete.me/posts/2025/essential-reading-july-2025 https://steipete.me/posts/2025/the-future-of-vibe-coding https://steipete.me/posts/2025/the-future-of-vibe-coding
- nonethewiser 1y agoI saw this channel from someone on hackernews if I recall correctly: https://www.youtube.com/playlist?list=PLm7RTomLsZo5PAWk0CpK0og5jsA-igdg_ https://www.youtube.com/playlist?list=PLm7RTomLsZo5PAWk0CpK0... It's what you describe: Someone using LLMs to code stuff. I didnt really end up watching it so I can't really speak to the content but it should be the type of thing you're looking for.
- tectiv3 1y agohttps://www.youtube.com/watch?v=qsTb9Y99qcQ https://www.youtube.com/watch?v=qsTb9Y99qcQ this is what sold me. This guy builds a useful tool for himself and follows you through the process.
- danielvaughn 1y agoThe approach I've taken to "vibe coding" is to just write pseudo-code and then ask the LLM to translate. It's a very nice experience because I remain the driver, instead of sitting back and acting like the director of a movie. And I also don't have to worry about trivial language details. Here's a prompt I'd make for fizz buzz, for instance. Notice the mixing of english, python, and rust. I just write what makes sense to me, and I have a very high degree of confidence that the LLM will produce what I want. fn fizz_buzz(count): loop count and match i: % 3 => "fizz" % 5 => "buzz" both => "fizz buzz"
- jerf 1y agoThat's a really powerful approach because LLMs are very very strong at what is basically "style transfer". Much better than they are at writing code from scratch. One of my most recent big AI wins was going the other way; I had to read some Mulesoft code in its native storage format, which is some fairly nasty XML encoding scheme, mixed with code, mixed with other weird things, but asking the AI to just "turn this into psuedocode" was quite successful. Also very good at language-to-language transfer. Not perfect but much better than doing it by hand. It's still important to validate the transfer, it does get a thing or two wrong per every few dozen lines, but it's still way faster than doing it from scratch and good enough to work with if you've got testing.
- hardwaregeek 1y agoMy mental model for LLMs is that they’re a fuzzy compiler of sorts. Any kind of specification whether that’s BNF or a carefully written prompt will get “translated”. But if you don’t have anything to translate it won’t output anything good.
- danielvaughn 1y agoYep, exactly. "Garbage in, garbage out" still applies.
- gyomu 1y ago> if you don’t have anything to translate it won’t output anything good. One of the greatest quotes in the history of computer science: “On two occasions I have been asked, – "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question"
- qwertytyyuu 1y agoThis is barely vibe coding, reads like just writing specs lol
- 9rx 1y agoIt reads just like regular coding, except using an LLM as the compiler.
- EcommerceFlow 1y agoThe biggest issue I've had with vibe coding, by far, is the lack-of and/or outdated documentation for specific APIs. I now spend time gathering as much documentation as possible and inserting it within the prompt as a <documentation> tag, or as a cursor rule.
- wahnfrieden 1y agoThere are tools like context7. Apple is also starting to put markdown files summarizing/detailing APIs for inclusion in LLM context automatically and have shipped these inside Xcode
- Netaro 1y agoBest vibe coding tip: Don't.
- zb3 1y agoMy list: 1. Don't. 2. Don't do it. 3. Seriously, don't.
- mlhpdx 1y ago> Always: > > Thoroughly review and understand the generated code Rules it out for me; I haven’t felt I thoroughly understood any code after working with C++ and reading the entries in code obfuscation contests. It’s a bit of a catch-22 to say “anyone can code with AI” and then make such statements.
- thewebguyd 1y ago> It’s a bit of a catch-22 to say “anyone can code with AI” and then make such statements. Also makes it very much not "vibe" coding. The term keeps expanding into "any coding activity with AI assistance" but the whole idea of "vibe" coding is that you don't actually understand the generated code, and likely don't know how to program at all, you're just prompting AI to do everything. Once you step into reviewing & understanding, you're no longer vibe coding you're just...coding.
- heyparkerj 1y agoI've expressed this to others as much as is reasonable - but the phrase "vibe coding" shouldn't be used in any serious discourse about agentic tools. We can't control the lens under which a given person first heard the term, but that moment (combined with the mountains of memes they've consumed since) is going to color a lot of folk's personal definition of vibe coding. It's not realistic to expect everyone to have a shared definition of it, despite the inventor of the phrase immediately giving it definition.
- seunosewa 1y agoThe first self-announced vibe coder was a founder of OpenAI. So he had the knowledge. He started to trust the code written by the models to a point where he didn't always read the code. This happens when you you have learned the exact limits of your models. It's like a senior coder who knows the projects the interns can handle without close supervision, and those they can't.
- michelsedgh 1y agoYou are, I think reviewing and understanding the code and the app are very important, but the moment you go in and code yourself you're not vibe coding anymore. I think you break vibe coding when you touch the code yourself and have to manually make edits not when understanding and making sure the llm did what you asked it.
- dismalaf 1y agoMy approach to vibe coding: The chat apps are pretty good at internet searches without all the ads and SEO crap. So I use the chat app, it's okay at context (knows which language and framework I'm using) and can basically get me the same answers as the docs would provide in less time. Still makes mistakes in code examples though, so I'd never trust it to actually change my code.
- __lbracket__ 1y agoI'm probably not explaining this well, but I feel like writing code from scratch has the effect of making us slow down and think more deeply and more globally about what we're writing. Reading vibe code "localizes" our attention to the correctness of the code produced and clogging the processes that otherwise think about connection of this code to other parts of the system.
- tschellenbach 1y agohere's what i use for large projects https://getstream.io/blog/cursor-ai-large-projects/ https://getstream.io/blog/cursor-ai-large-projects/
- levocardia 1y ago"The vibe code with detailed specifications is not the true vibe." - Laozi
- scheisshausDan 1y ago[dead]
- deleted 1y ago[deleted]
- the_doctah 1y ago"vibe coding" is easily my most hated thing I've become aware of recently.
- captainepoch 1y agoThe day people stop inventing stuff like that and they put the same effort in do really good, quality code... That day, we might start having decent software and not Electron or React apps everywhere... God bless old times when programmers cared about quality rather than stuff like this... "vive coding"... My God...
- byryan 1y agoThere are still plenty of programmers that care about quality rather than stuff like vibe coding. Most programmers I know don't take vibe coding (defined as making an app with 100% llm generated code and not looking at the code at all) too seriously. They still care about the quality of the code they write.
- chamomeal 1y agoIt’s so unfortunate that “vibe coding” is the term that stuck. I never want to say “vibe coding” out loud in my life lmao
- h4ch1 1y agoOh this document outlines exactly how Kiro works. No wonder since this doc and the product are from Amazon. I like spec driven development, especially for someone as ADD as me. Keeps me from thinking about a new feature while working and dropping everything to implement it.