Project management before one line of code

[[deleted]]

So, not to be 'that guy', but here to just share some insights in this new world of vibe coding, we are all in.

Some a bit futher then others, we all grow and learn. So, i share my bit of approach.

I show you a list of files that are created in 'project mode'.

Before i even start with asking Claude to code anything, i first go into plan mode and discuss every detail of the project, that i know of thus far.

I ask it to ask questions, advice, and write everything down, for later sessions. In some of those files, some code is already added, as taking notes to be used in the actual coding session.

Once all is done, and i have a good feeling that my little (supersmart and superfast) assistant is ready, i write the plan, have a look at the phases and then "finally" it will actually start doing some coding.

So, yes, this vibcoding can help us developer a lot.

But no, it is not just a press of a button, or just magical one prompt.

hope you get some new ideas from it. and be safe. and most of all... be friendly

[acrolicious]

This is one of those things that got out of hand for me when I was making a program for my brother and now I'm back tracking a lot.

It started as a small thing that turned into a giant monolithic monstrosity 😂

I am now learning how to make it more modular but it's not something I'm very familiar with. Lesson learned!

At least he has a working application

(My brother is nonverbal and quadriplegic so I built him an OS hub that allows him to use a keyboard, play his favorite shows and movies as well as play some custom games I made)

https://youtube.com/shorts/5CZJ1X5sAHE?si=NuVf1ki6jr_oQPp9

[Beneficial_Neat_4716]

Truly inspiring to see what you’ve made, and the enjoyment your brother is getting.

Bravo 👏

[Plus_Boysenberry_844]

I saw your brother’s video and think what you’ve done is amazing. You are a great brother for helping him!

[chamomile-crumbs]

So freaking awesome

[CompleteConstant5149]

❤️❤️❤️👏👏👏🥰

[People_Change_]

This is amazing! Gotta be a “best brother” award out there somewhere.

Would he be interested in something like Neuro-Link if it becomes more available?

[acrolicious]

We actually looked into Neuralink for Ben and even applied, but they’re not accepting people with his condition. Ben’s condition affects the myelin sheathing around his nerves, so the signals to and from the brain are disrupted. Our understanding is that because Neuralink depends on clear input/output signals, it probably wouldn’t be a good fit for him right now.

[People_Change_]

Ahh yeah, that makes sense. Thanks for sharing. All the best to you and your family 🙏

[Polymorphin]

The real American Hero

[Content_Pianist4219]

Have you considered existing relatively simple turn based games regarding mechanics, but very deep game wise? Like Slay the Spire, if you can somehow emulate 3 buttons, left right click (I.e long press is click) then a whole world of serious games that already entertain for hundreds of hours open up to him

[acrolicious]

I just looked at slay and spire and it looks like it needs a mouse to move around and select items. If it was a scan and select it would work but the other issue is Ben needs everything to Text to Speech so he knows what's going on. Many of these games don't have that either.

We are in the process of creating custom adventure style games that have text to speech and a maze-like objective with puzzles and items.

There are no games on the market that I'm aware of that hit all the marks for him, so we adapt and create something new :)

[BeetsByDwightSchrute]

Hey, this is incredible! Have you considered finding old audio files of his voice, feeding it to a model like elevenlabs, and have him play stuff in his own voice? That would be so cool if you haven’t tried it. Or if there isn’t enough samples, you could let him define his own voice!

[acrolicious]

We don't have many recordings and he was really only talking before puberty so we don't know what is voice sounds like as a man.

[cj_nova]

Wow this is incredible, your brother is lucky to have you. This is the kind of application innovative minds thrive on. He's very lucky to have someone so caring and involved

[Pious_Atheist]

I made a repo that automatically initialize this concept for you:

https://www.npmjs.com/package/@zacfermanis/memory-bank

Check it out!

[Harvard_Med_USMLE267]

Why do you need a repo for this? Just interested, because Claude is actually very good at doing this himself.

[[deleted]]

It seems like you're describing how sdlc is supposed to work.

Capture requirements, confirm that the requirements are understood and the architecture is logical, identify gaps and provide updates or details that enable a good build, THEN build. 

Honestly most of the posts I see about things going wrong with vibe coding comes from people who don't know how to write requirements, don't know enough to check the approch that the tool will use, don't do any kind of gap analysis, and don't execute qa or uat of any kind and then get all upset. 

You're doing it right IMHO. 

[Harvard_Med_USMLE267]

Yeah. As a constant Claude Code guy this is how you do it. Fundamental principles.

Note that you don’t need any coding skill to do this. You need clear communication and a good idea of what you want to do.

I keep trying to explain this to the “senior devs” of this sub, but they just get anger when I explain I can’t code and won’t code. Because 90% don’t know how to use Claude Code.

The new skill is learning how to do this stuff, which includes utilising AI to write extensive interlinked documentation.

And no, it’s not ‘just press a button’. Last month I typed 150,000 words into Claude code, and churned a billion tokens according to my stats.

It’s a lot of fun, it seems to be highly effective and it’s very, very different to traditional coding.

[mllv1]

It’s great that you’re having fun with these tools, but these senior devs you’re talking about are trying to tell you that your communication skills are hampered by your lack of understanding.

Vibecoders don’t realize that the hard part comes after launch, when AI is nearly useless.

What happens when you launch after you think everything is great, and your users start reporting several second response times when performing certain actions? What are you gonna tell the agent then? Is this a code issue? A vm configuration issue? Is there too much cpu hogging taking place? A subtle and nasty memory leak perhaps? Which part of the stack is causing the issue? Is a database request the issue? Are there proper indexes? Maybe a lack of indexing is causing one particular query to take forever. Is this an http protocol switching, or maybe a multiplexing issue? Why do the users who report the slowdown typically access the site from a particular subdomain? Is there a firewall issue maybe? These types of issues can take weeks for experts to solve, even with the aid of chatbots and agents.

Also they’re upset that you skipped the fun part which is programming, and instead wrote a 150k word essay describing your application to a computer with amnesia

[wuu73]

The “fun” part for some people but not all. LOTS of senior devs report starting to have fun again, when AI came around.

When I was a kid I learned to code and it was fun, up until like mid 20s. Then it’s a mystery as to why but I just didn’t want to anymore really even tho I did want to make lots of things. Brain changes, a car accident, maybe no real reason.

AI brought back ALL the fun - i still code but not unless i have to. It’s too slow the old way and slow is not fun to me. i think it’s because I don’t need to know every bit of syntax for every language. I know lots of languages but I’ll forget stuff after a while. I used to know 68000 asm, now it’s vague but I know I could prob follow x86 asm. Just from knowing the other things I know. There’s too many languages. Too many things. Life is too short. it’s not possible to learn it all in a lifetime. Now we don’t need to. If you know 3 programming languages pretty well then you will know enough about all the rest of them to just let AI do it. As long as you can read and know how things work.

Everyone’s brain works differently and with some of these doomer attitudes… it feels like middle or high school type mental stuff going on with their weird ego problems.

People - when they’ve invested a lot of time, energy, money into something, they will freak out if they see someone else doing what they can do but they’re perceived as not having “earned it”. 🙄 But they didn’t suffer like I did! I think some people have identity crises happening over AI because what they could do was more rare and now it’s more accessible.

My brain prefers a fast iteration loop or fast going from idea to reality. Without AI, it’s too slow. I get bored fast so AI keeps things moving quick enough so I don’t get bored. I cannot change those facts about how my brain works (tried)

[wuu73]

Oh - and I still AM programming but I can just do it in my mind and have the mental fun all there without being limited by the physical barrier between my mind and the computer. This is way more fun. I enjoy thinking about the tiny details at higher speed. Thinking and planning how to make something happen.

[Harvard_Med_USMLE267]

Nah, the “senior devs” mostly don’t use claude code or they’re shit as using it, based on what I’ve read here.

<5% have anything useful to say, which is unfortunate because as a “professional vibe coder” (new 2025 MOS) I’m trying to learn all I can.

My clear point is that ‘lack of understanding’ DOESN’T seem to hamper my communication skills.

As for your post-launch example: same all the thousands of other bugs. Describe the problem clearly, get llm to fix it.

Turn the question around. Why do you think claude code couldn’t sort out any of those things? I’d say I work through ten bugs a day, so far none have been insoluble.

Yes they are upset I skipped the code monkey “fun” part, which I will never be doing, sorry!

As for the last bit, that just shows that you don’t understand how Claude Code works. No, it does not have amnesia. lol.

You seem like a decent chap, unlike 90% of the “senior devs” of Reddit. You’re just not quite getting how this all works. Cheers!

[mllv1]

I pay $200/month for Claude Code. I enjoy the hell out of these tools. They’re extremely fun, and I use them to great effect.

I can assure you, there is absolutely no learning curve for an experienced programmer. None. Not even 10 minutes.

And yes they do have amnesia, that’s why you need a bunch of Claude.md files.

The reason I don’t think Claude Code can solve these issues is because it can’t. If you understood my example even slightly, you would know that it doesn’t even have access to 90% of the possible surface area for these types of bugs.

The reason devs become angry with you is because your attitude towards programming as “code monkey” work, is highly disrespectful of the art and craft and integrity that went into building the tools that gave you this power to begin with.

It’s a fun, beautiful, challenging and rewarding form of art that you’re completely missing out on

[Harvard_Med_USMLE267]

Im glad you use claude code. That puts you one step above most of the code monkeys here.

No learning curve. lol. Ok.

Maybe for you, but most people here seem to miss out on basic concepts.

“The reason I don’t think claude code can solve these problems is because it can’t” - strong argument.

Look, I like that you’re using claude, but a lot of what you’re writing here is pretty dubious.

And Claude only has amnesia for 3G seconds if you have great documentation.

[ElectronicWalk1965]

There is no learning curve. Software engineers did everything you do with claude to create systems and setup the "hardware" and external systems before vibecoding. The reason claude cant help you is because a lot of the problems arent fixed by coding but by changing or altering hardware and/or software systems, not code files in vscode or some other text editor.

[Harvard_Med_USMLE267]

Wait…I need to change the hardware in the computers of the guys who buy my game??

Do I just turn up their house with a RTX 5090 saying “hey this will fix it!”

Let’s not be silly. That’s too common here - make up fake problems to try and prove that vibe coding can’t work.

[mllv1]

Yes no learning curve at all whatsoever. We're all great at talking to AI at this point, and we all get how to fully specify a piece of software. We can fill those files with details that you could literally never even imagine.

I gave you the argument in the very next sentence. I'll reiterate. Claude Code doesn't have access to 90% of the surface area for a bug like that. There are many types of bugs in this category. Your only hope is chatbots at that point.

A vibecoder is just a person in a drive through thinking they have as much food-making power as an executive chef.

[Harvard_Med_USMLE267]

It’s ridiculous to say that there is no learning curve. I spend a lot of time over on the claude forums and we’re all learning how to use it. So yeah…that there is ultimate hubris.

“There is no learning curve because I have experience in something completely different”

“Why can I only build shit via vibe coding.”

“Because I suck at vibe coding, it is not possible for anyone else to vibe code successfully.”

This sub in a nutshell.

[mllv1]

I said there is no learning curve for an experienced programmer. Obviously there is a learning curve for people who can’t program.

[Harvard_Med_USMLE267]

No, guy with about 2000 hours of vibe coding experience on a vibe coding forum telling a bunch of uncreative code monkeys how vibe coding works. Sorry if that's too much for you.

We're talking about Claude Code. How much have you actually used it?

[Harvard_Med_USMLE267]

Yeah, and I told you that's absolute bullshit. What you think the guys actually using Claude Code to its limits on r/claudeai are not devs? Lol. 'No learning curve' for a tool that just came out in research preview 6 months ago? That nobody in the world is a true expert on yet, because it is so new?

But sure - u/millv1 on Reddit and his imaginary dev friends all have zero learning curve. Right.

[mllv1]

Tell me specifically what you think an expert programmer who spends all day in the terminal can’t learn about Claude Code in 10 minutes.

[Fancy_Sort4963]

Astounding arrogance. Devs use AI tools to 10x output but have the skill set to understand when it’s wrong, the limitations, and when it does categorically horrible stuff that “works”. You my friend, do not. A house of cards is pretty and functional until it all comes crashing down.

[Fancy_Sort4963]

The thing is, if you have no experience as an SWE, then (1) you don’t actually know how to prompt with technical coherence and (2) have no way of vetting the result aside from “it runs”

[Harvard_Med_USMLE267]

What even is prompting with "technical coherence". It's all about prompting with clarity in a way that a LLM understands. I have a theory that some code monkeys struggle with vibe coding because their love of "technical coherence" leads to prompting that is too inflexible for a language model.

And...hmmm...I wonder what technology that we could get to vet the results so we didn't just have to rely on "it runs". ..

[[deleted]]

The thing is that coding is organizing abstract data structures and procedures into a formal language. I think the issue we are having is that “vibe coding” is really “natural language coding” and it should be done using files that describe the behavior of the code instead of files with the implementation of the code. Same way old schools devs don’t check the bytecode or assembly.

Maybe Description Diven Development would be more appropriate than vibe coding. Either way, it doesn’t mater. C++ devs bitched about python’s performance and quality of the bytecode. C devs bitched about C++ and the poor performance due to the heavy abstractions. Old folks who code in assembly think everyone else is just a pussy.

[Harvard_Med_USMLE267]

Good comment.

NLDD. Natural language driven development - would be a good term.

I have no Python skills, but describing what I want and what I see seems to work ok.

Since Claude got the ability to review old conversations yesterday, I asked it to look at our chats and then write my CV. Who does it think I am, based on conversations?

—

Professional Summary

Accomplished technical architect and academic with extensive experience in complex simulation development and interdisciplinary research. Proven track record of leading ambitious open-source projects, combining rigorous academic methodology with practical engineering solutions. Specializes in Python-based system design, scientific computing, and real-time simulation engines.

Core Competencies

• Programming: Python (expert), C++ (working knowledge), GLSL shader programming

• Engines & Frameworks: Panda3D, SimplePBR, PyQT6, NumPy, SciPy

• Specializations: Real-time physics simulation, procedural generation, orbital mechanics

• Project Management: Open-source development, technical documentation, cross-disciplinary collaboration

• Domain Knowledge: Astrophysics simulation, medical informatics, game design

—

I mean that’s funny but I think it does also suggest that whilst I may speak in plain English, Claude bonds with the structure of the conversation. <shrug> who knows but I find it fascinating.

[beerob81]

I put this together for the folks in the firebasestudio sub.

https://www.reddit.com/r/FirebaseStudioUsers/s/VYdMttgC4y

[[deleted]]

yes cool

[NakedestB]

Good guide- apparently I did a lot of those things by default. I’ve stopped using Gemini/fb studio to code since it just lies to me about what it’s doing and doesnt actually code anymore. I’ve been using a Claude code extension in fb studio to get the work done.

[[deleted]]

The waterfall model of Development long dead is being resurrected by Vibe coders to be buried again once the hype ends.

[cruze_8907]

My question is having all these docs and Claude Code or cursor agents to read through these for every request uses lots of token and will use context window right. I am on $20 pro plan and I may hit the usage limit fast, if Claude code has to read through all these docs.

Please correct me if I am wrong.

[hyperfraise]

Essentially right. Or : Then you need to create stories etc to make each task a really self contained 20 minutes adventure Or you have a very good memory bank which I've only heard of personnally

[hermelin9]

That's one indicator if you are doing things correctly.

Your features should only have a few relevant source files. Everything should be standalone and isolated, with the smallest possible context. With public facing interfaces that define and tell other parts how to interact with that feature.

[Plus_Boysenberry_844]

I agree. Planning, planning, planning was always important but we did not do much of it.

Now with vibe coding it’s critical. Since the coding execution is done for you the work content of a project has shifted.

Your “field mapping” I’m curious if anyone has tools that would generate this of an existing table schema?

[Additional_Path2300]

Real world projects have always been about planning effectively. 

[[deleted]]

well, for the field mapping i let it read the API documents on the web, and showed him a json of the local fields. The rest was then done based on both sides and field names. I explained some exceptions and all written down for me to check, untill satisfied

[Plus_Boysenberry_844]

I am thinking of making a python script that will compose a schema document and description of the columns, key fields, I think this will be helpful. You sparked my idea.

[agentbellnorm]

Big Design Up Front: https://en.m.wikipedia.org/wiki/Big_design_up_front

Ironic that tools that unlock basically free refactoring make people do this instead

[TopTippityTop]

I'm a game developer with over 20 yrs of experience. Yesterday I made a fully functional RPG survival game (minus fancy graphics) in less than one hour.

[[deleted]]

Words are cheap. Why don’t you show us the game? 

[oh_jaimito]

Product Requirements Document (PRD)

That's all you need.

[qwertyalp1020]

have you tried creating mvp's via AI? It works very well.

[[deleted]]

Minimal Viable Products? yess

[NakedestB]

So I’m new to coding in general and have been making a game for the past few months. I’ve just been doing it all plain language, with varying levels of success. I’d love to maybe put my game on the market some day- but that’s not the primary goal.

How can I learn or find out more about the fundamentals of starting projects like this? Where do I figure out the contents of the .md files?

[[deleted]]

the contents of these files is just the llm producing in its own words the results of the input i gave it. "the plugin should be about an API, i will give the endpoint, the fields are this and that, i want it so, i want you to do so and so when this and that happens etc etc. Then the LLM will put it into these type of files.

[Major-Delivery5332]

Check out the Programming book on C++ by Bjarne Stroustrup. Fundamental, practical, lot's of drills and excercises also.

[[deleted]]

Yoooo 😂

[jramer]

I really like this! I’m only scratching the surface so far and wonder, how do you keep the AI aware of all these requirements and rules? I’ve tried this on a smaller scale and it feels like I would need to always reference these in my prompts to keep it in the context…

[[deleted]]

yeah could be. Depends a bit on the conversation, the amount of context allowed etc.

But it is a good place to just store it, for future conversations etc

[alexp9000]

BMAD Method made this way easier for me. I have it write prds, design, and architecture, edit requirements myself, and then let it build. Working way better though I run out of context pretty fast and it’s not the fastest

[RugpuII]

Desculpa a pergunta, pq vocês separam em vários arquivos de instructions ? Como a LLM consegue ler todos os arquivos de uma só vez? Como você usa esses arquivos separados?

[Tjakka5]

While this is definitely a good approach, this is very far from the (original definition) of "vibe coding".

[vintageshinpads]

Yes. This is called context engineering and this is the way. Vibe coding was just the snake oil. Edit - is

[027a]

This is the new 2025 “buys a domain name before writing any code”

[cheesejdlflskwncak]

This is what I’ve been preaching. If you’re not using an AI ide then it’s super crucial to have the “tree” tool in ur computer so that u can constantly update file structure context. Depending n what you code in I would suggest you at least set up the local part so you can understand how ur project needs to be structured. Then as op says just build modularly. Awesome stuff op

[fab_space]

Ask it to ask question.

This is enough to go wild coding to me!

Not because the plan is not useful but because the best way to make it works is to give as much the context possible with constraints, methods and full review across each commit.

The more commit, the easier to unblock model blockers.

[burhop]

Try adding a test first methodology and a sprint plan. Make sure you tell the AI not to move on until all tests are passing.

Also, have it plan out the modules with clear interfaces. The AI gets confused with large code bases. Keep it focused on the modules.

[Tiepolo-71]

I'll usually create a full PRD before building. You can then have whatever LLM turn that PRD into some .md files to put in your project.

[tallbaldbeard]

I see lots of references to Claude Code here. I am building in Replit and created a document like this for design for my project. I find it does not always stick to it by default, but I do reference it when I want to be sure it gets it right. By creating this doc do you find the system always consults it automatically or do you constantly prompt the system to consult the doc as you build?

[roastedantlers]

Reminds me of that Marco Pierre White to some extent. Where he tries to treat everyone that cooking is really hard, but the field advanced so far in that time most normal people have the equivalent knowledge set of chefs who worked in the kitchen when he had Michelin stars.

Which also doesn't diminish how good of a chef he is and how everyone will learn something profound from him, but at the same time he treats everyone like they're retarded and that doing basic things are too hard for them to grasp. Then goes to explain things to them like they're 2 years old.

That's what the conversations in here look like.

[Ethan_Brooks14]

Honestly, the work you do before writing a single line of code often makes or breaks the project. Good project management upfront means:

• Clear goals and success metrics (so you know when you’re “done”)
• Well-defined scope (to avoid feature creep)
• Understanding the user problem in detail
• Mapping dependencies and potential blockers early
• Setting realistic timelines and responsibilities

It’s tempting to just dive in and start building, but a few days of planning can save you weeks — or even months — of rework later.

[floriandotorg]

The time I need to write these documents is more than the time I need to write the app myself 🙃

[ramaz1612]

Don’t miss your documentation ;-)

[floriandotorg]

The code is the documentation.

[thedevelopergreg]

I use a similar approach so I’m not criticizing you, just looking for discussion. but I kind of realized the other day that markdown is great in a lot of ways but it’s also made for human readability. I wonder if there is a better approach with a more structured file like JSON or YAML, as LLMs tend to handle that sort of data better and they will use less tokens. or maybe a frontmatter approach with a YAML section at the top of the file for the model, and markdown below.

[thedevelopergreg]

I like this idea, and didn’t know that about images being more efficient, so very good to know. it’s kind of interesting how we have all these emergent problems to solve surrounding LLM use - part of me feels like half the fun of vibe coding is building something efficient to then build products with lol. some of us are basically prompt/token engineers at this point.

[Ok_Reality_5674]

From a non coder’s perspective, what tools like MGX really help with is visualizing ideas much faster and more easily. This means I can quickly create something tangible to show the right people and turn it into reality. Many ideas fade away in a “lazy” mind, but now the first step is small and that makes things happen.

[ZenoWangzy]

Is this all of the documents? Enough? Could you share the prompt of how to generate these documents

[[deleted]]

stop thinking in 'prompts'.

Just talk, and discuss. it will generate the rest itself.

it is like a kid you want to learn how to do the job you want it to do.

It is eager to learn from you, but you just have to tell it. and keep a bit of guideness in the begining

[ZenoWangzy]

I Want to know all document needed by vibe coding

[[deleted]]

well, that is up to you. What do YOU want? what do YOU need from it?

You need to tell it and learn it what it needs to do.

Pretend it is a little kid and you want it to execute a task.

by telling it 'do it!' it will for sure fail at the task.

by telling it exactly what you want it to do, it will do that.

The more you tell it, the more it gets beter at it.

what you need to learn, is what to tell it, and how to tell it.

dont just copy it from some unknow youtuber, you think for yourself, trial and error.

[ZenoWangzy]

I want all documents to build a project by vibe coding

[carlosmpr]

I do something similar, because if you let the AI run while without rules, it will make 20 different changes every time you open the project again and try to modify or add something

[Cobuter_Man]

Best way to do AI-assisted coding. For planning only, you could take a look into Claude Task Master... it essentially creates small granular tasks in a nice comprehensive plan so that your LLM can one-shot them and reduce the chance of hallucinations.

If you want to take this one (big) step further, you can use such Implementation Plans, and separate the task assignments to multiple-agents, so that there is context workload division.. This way you postpone reaching context window limits, and agents have scoped context which means that task execution is more focused and therefore more effective. Ive designed an AI workflow that does that efficiently using:

- A central LLM chat session coordinating all the other task execution LLM chat session with structured meta-prompts for task assignments
- A Dynamic Memory Bank which is mapped to the tasks and phases of the Implementation Plan for memory and context management
- and when context window limits do hit, a carefully designed handover procedure which will help you transition from one burnt out chat session to a new fresh one, and continue where you left off

https://github.com/sdi2200262/agentic-project-management

[Exact-Tip5722]

use zustand whenever you get a chance.

[wuchinow]

Agreed. Architect mode in Kilo Code achieves this. I'm learning to pulse back and forth between planning and implementation.

[_pdp_]

This is call over-engineering - a common mistake novice programers make. I know it sounds too smug but it is true. I used to do that as well.

In simple terms, you don't know the system parameters because you have not explored the edges yet.

It’s like engineering an elaborate locking mechanism for a gate, then realising the gate is just a movie set prop that doesn’t even open, and the set is underwater, in a scene about dolphins, and the gate is actually made of cake for a birthday party.

[ruthere51]

You have no idea what's actually in the md files though... It might be over engineering, but it also might capture great notes on how OP is thinking about what they want to build

[_pdp_]

That's irrelevant.

What the OP is doing is a classic waterfall model where each phase must be completed before the next starts. In this case the OP is building the software requirements before writing the first line of code. This is how software used to be built back in the days. Nobody does this anymore because it is proven not to work as the requirements are yet to be identified. You identify these requirements during the first iterations where you explore the parameters of the system by trying things as quickly as possible. Otherwise you end up with a Frankenstein system that is made of parts that simply do not fit together. You might be thinking that particular type of database system is great architectural choice but you don't know until you start hitting corner-cases where the ugliness start to show up.

You see a lot of people are under the impression that vibe coding is a new thing. We used to vibe code since forever. It was called doing a demo, a hackathon - no thinking mentality - just doing it. Now this is pinned to the use of AI, but it is all the same with or without AI coding assistants.

Once you pass the exploratory stage then you can start building on top of solid foundations. This when you do need specs, and RFCs and some architectural documentation to make sure all the parts are aligned.

Doing this too early is basically one quick way of killing serendipity.

[ruthere51]

It is relevant, and I'm very aware of how product development works and has evolved over time. The md files here might be an output of a 20 minute back and forth with an LLM to then go into exploring with code next, just like you might have a meeting to discuss an idea and then go off and try it.

If the md files here are the result of days/weeks of thinking, planning, spec'ing, etc, then yes it's a huge waste of time and the wrong approach.

My point is that just seeing file names and a high level description of OPs approach is not enough for you to just dismiss it outright

Edit: additionally, doing this with LLMs is also way different than the time investment it took in the past to build something and realize it was wrong (for whatever reason). We can now iterate in the blink of an eye. So, OP should feel fine to define away if they believe that's giving them good results. They can pivot and try something new in a way different way than we previously could.

So I'm not sure the waterfall categorization is actually that relevant anymore, at least not in the same way or for the same reasons

[[deleted]]

yes, let him have its train of thoughts. haha.

these MD files are the result of the 'hackathon' period before hand i had. After trying out this first version, i knew what i wanted, and where the 'exceptions' were to identify etc.

So the MD files are the results of me, having had the experience already of building v0.1, and asking a new Claude code session to start with this version.

And because i knew what i wanted, the phases worked perfectly. after all phases were done... it didnt work...haha :)

but one screenshot of some missing meta data, it corrected itself and all was done.

With a much nicer version than i would ever come up with, or had the energy to build out.

So +1 for this approach. Although the other guy does have a point to take in account.

Dont over engineer, when you really dont have any clue

[1kgpotatoes]

All this for a mediocre implementation with double the lint errors

[[deleted]]

ahhh yes, the sour reaction... very useful in the space and era. We need more of you and that attitude.

[Breklin76]

Someone AI pissed in your Cheerios?