Author here. The AI coding space is semantically chaotic: "vibe coding," "AI-assisted," "context engineering," "augmented coding," "spec-driven", etc. Everyone's using different terms for overlapping concepts. Sometimes people

This article introduces what I call "the vibe coding trap" and attempts to bring clarity by proposing a standard classification: 4 distinct phases of AI adoption in software development.

- Phase 1: No AI (baseline)

- Phase 2: Autocomplete (Copilot-style)

- Phase 3: Conversational/Vibe Coding (for MVP/prototypes, otherwise painful)

- Phase 4: Structured AI (context engineering, specs-driven)

The terminology mapping alone might be helpful for teams trying to figure out "where are we?" and "where should we go?"

Curious: Are there any other initiatives to bring clarity about these terms?

Nicely written! Including also the pricing, licensing, and ethics perspectives made it even better. Thanks for sharing.

Congrats, all these icons and illustrations look great! I have a question, what's the difference for example between "UI Icons Line - Free" and "UI Icons Line - Pro" when using them for free? I think I'm not understanding the license, I could download icons from both and put the attribution the same way, couldn't I?

Great question! UI Icons Line - Free is licensed under Licensed under the Creative Commons - CC BY 4.0.

UI Icons Line - Pro has more icons than the free counterpart. You can only download low-res PNGs for free, actually. See the part about free license limitations here: https://intercom.help/streamlinehq/en/articles/5354376-strea....

Looks great! Do you consider adding a plain-text input/output format? Would be great to keep these diagrams in a VCS.

Good idea! It'd be nice if you share some screenshots of how it looks like and its main features (visual) without needing to create an account.

Hey this is great! It even checks if answers have the checkmark so it's not just a random code block.

I think it would be even better if you insert also a comment line with the link to StackOverflow, so devs can check it to get the full context.

Great idea. I'll add it

This is awesome, excellent work! Like some others here, I feel like the otters over-engineered the entire thing using fancy glass balls and partitioning a river where a categorized bulleting board would have been good enough.

But then I realized that that's what makes it a realistic story ;)

Jokes aside, the best explanation I've ever seen. It should be a must-do for people who want a quick and understandable introduction to the concepts.

A video summary of my book. The video is not the piece of work I'm most proud of, but I think it serves the purpose of explaining the book contents in detail. There is also a sample chapter available on Amazon (https://www.amazon.com/dp/1484261305/).

I would love to get feedback from the community about the book contents and the approach (although comments about the video are also welcome).

Hey good idea, let me give you some constructive feedback.

I think people need a conversation to define how to build a software project, not a simple Q&A mechanism. Maybe you can add some possibilities to contact devs for further explanation.

Besides, to make it more realistic, your examples could use some basic requirements. Otherwise, people may get the wrong answer, based on a pile of assumptions.

This is really helpful! I've logged it, thank you

Nice tool, congrats! One suggestion from my side: add a video showing the main features and how it compares with other (more rudimentary) tools. The GIFs are too short to get an idea of what is exactly the problem that the tool solves.

People who are familiar with mindmaps probably understand the concept, but you might lose others in the signup screen.

Thank you! I really like the video idea - I'm actually writing the script for an intro video so hopefully I can get that out soon. Were you able to understand the video clips at the bottom of the page? I'm thinking of zooming in a little more on the features they are trying to showcase