RE: LeoThread 2026-02-04 21-13

avatar

You are viewing a single comment's thread:

Many people reshared this as the one-year anniversary of vibe coding. Some retrospective —

leofinance
0
0
0.000
13 comments
avatar

An account has been active for 17 years now (omg) and tweet engagement remains basically unpredictable.

0
0
0.000
Reply
avatar

This started as a shower-of-thoughts throwaway tweet that was fired off without much thought, yet somehow it coined the right name at the right moment for something many were feeling.

0
0
0.000
Reply
avatar

As a result, vibe coding now appears on Wikipedia as a notable memetic "contribution" and its article has grown. lol

0
0
0.000
Reply
avatar

One addition: at the time, LLM capability was low enough that vibe coding was mostly for fun throwaway projects, demos, and explorations — it was good fun and it almost worked.

0
0
0.000
Reply
avatar

Today, programming via LLM agents is increasingly becoming a default professional workflow, but with more oversight and scrutiny. The goal is to capture the leverage from agents without compromising software quality.

0
0
0.000
Reply
avatar

A popular alternative name is "agentic engineering":

0
0
0.000
Reply
avatar
  • "agentic" since the default now is orchestrating agents to write code most of the time, while humans act as oversight
  • "engineering" to emphasize that this is an art and a science, a discipline that can be learned and deepened
0
0
0.000
Reply
avatar

In 2026, continued improvements are likely on both the model layer and the agent layer. There's real excitement about what the two together will produce over the next year

0
0
0.000
Reply
avatar

A new kind of coding called "vibe coding" surrenders to the vibes, embraces exponentials, and almost forgets that the code exists

0
0
0.000
Reply
avatar

LLMs (e.g. Cursor Composer with Sonnet) have become good enough that interaction can be mostly voice (using SuperWhisper) and minimal typing

0
0
0.000
Reply
avatar

Requests are often tiny, like "decrease the padding on the sidebar by half," because it's easier than hunting through code

0
0
0.000
Reply
avatar

Changes get accepted without reading diffs, and error messages are pasted back with no comment, which often fixes things
The code can outgrow easy comprehension; bugs sometimes get worked around or chased away by random changes

0
0
0.000
Reply
avatar

It's serviceable for throwaway weekend projects — the process is more about seeing, saying, running, and copying than direct coding, and it mostly works

0
0
0.000
Reply