mechero

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?

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.

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.

Can you share your experience using the no-code tools and how they are connected to make your website/service work?

Otherwise, this submission looks like clickbait.

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.

Looks good! I don't like the popup style that much, but I guess it could be extended to show the article on the same page.

Good idea, congrats! Can the people who post a message also ask for a refund, or is this only limited to the account owner?

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.

Good idea! Are you considering implementing browser plugins?

Good idea! As a suggestion, I think your website could use some extra documentation and examples.

For example, could I create a panel in Grafana showing the busy vs. free ratio over the last three months? That kind of things.

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.

Thanks! Yes, we have plans to add some features like player profiles and custom badges.

Thanks! We created some templates for popular tools to make that easier. For example, for JIRA we have these https://zapier.com/apps/quboo/integrations/jira-software.

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.

Hi,

My name is Moises and I am the founder of Quboo, a gamification platform that helps increase motivation of software development teams by spicing up the boring processes.

In Quboo, developers and teams can climb the leader board by following the good practices that you want to promote.

Out of the box integrations:

- Sonarqube: You can promote removing technical debt, getting rid of security vulnerabilities, or writing unit tests for legacy code. - Slack: Colleagues can reward each other with some points just by reacting with certain emoji to their message. Kudos for completing some paperwork or boring stuff.

Custom integrations:

- Zapier: Create your own game in this automation tool. For example grant some points for finishing a task in Trello. - API: Create any game you want.

Here you can see the leader boards of a demo account: https://quboo.io/jXoRnjewkUhz/players (logged-in users can manage campaigns, teams, settings and more).

I would love to hear your feedback about this project!

Nice idea. One recommendation: include real snapshots in the GitHub's Readme file, or a link to a live demo, there seems to be only a mockup. If you do that, people don't need to set up everything to have a better idea of how it works.

Good idea, congrats! Have you considered building a platform for remote workers connected to these features? I mean, offices could rent out their spare desks for other people not in their organization, and remote workers could book them for a limited time.

Not the same use case, but I think it's not far from what you offer.

Indeed, but I'd link the GitHub code sources below each picture and provide good alt descriptions. JS plugins like Highlight or Prism end up building massive HTML making e.g. google's pagespeed tools complain about DOM sizes.

And, anyway, most people would rather clone the public repo or use GitHub for copy/paste purposes.

Say I have code snippets I want to include in a Jekyll blog for example. I could call your API from a pipeline process, store the images and link them from the posts. A plugin would be deeper integration, but an API would just work and would be great already.

I guess a similar process could work for other blogging platforms.

Really nice project! This could be very useful for technical / programming blogs. Are you planning to offer a REST API?