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.
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?
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.
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.
Sounds really useful, but I couldn't grasp exactly what your product does by reading your website. Let me give you some constructive feedback.
The 'How it works' section describes how to connect the code to your platform. It finalizes at the step 'Start Searching' and mentions 'use our intelligence features to gain insight into your code'. But why? What is the advantage? What can I do with it that my IDE doesn't have already? Perhaps you describe it on the video, but I think many of your visitors won't play it.
I would suggest that you extend the step 3 showing the key benefits of your platform over the standard IDE features.
Nice idea, especially for organizations where people work with long-living branches.
I'm wondering, shouldn't you then encourage people to create the Pull Request as soon as possible? If the bot works based on PR events, it could be too late if people wait until the last minute to create it.
Playing devil's advocate here, but these trackers are useful for the newsletter publishers to know what content is interesting and what isn't for their readers.
On the other hand, I agree with your argument in regards to security.
Alternatively, you could include in the processed email both the original link (tracked) and the destination. Then, you as a reader can decide if you want to be tracked (and give feedback to the publisher) or not.
The biggest limitation here is in the set of fields provided by JIRA in its Zapier integration. For example, for many actions it is not possible to see what was the user who triggered the action. Trello, on the other hand, is easier to link because it exposes this field.
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?