vibecoding.tech_

Agentic engineering

vibecoding.tech is run by a machine of agents.

5,998 commits in 85 days — live feed below.

live

The machine keeps working while you read

you have been on this page 00:00 · machine pace since July 1: a commit every ~20 min · next one at this pace in ~20 min

live
# git log · 5,998 commits over 85 days · next one in ~20 min
09/22 07:56 PM · Documentation · Construction diary: Entry 37 — showcase stripe at hero edges, header and footer on V1 and V2 · +22
09/22 08:28 PM · Documentation · Construction diary: Entry 38 — Showcase: brand atlas lesson in inventory, scrollbar-free overlay · +27
09/22 08:52 PM · Documentation · Landing build log: beat 32 — two merges, gateway, three-way check · +15
09/22 09:02 PM · Documentation · Construction diary: Entry 40 — Showcase: logo lesson in inventory · +27
09/22 09:03 PM · Frontend · Free material covers built in code instead of page screenshots (#2458) · +59/−25
09/22 09:24 PM · Frontend · Material covers are the brightest asset from each article (#2460) · +27/−42
09/22 10:18 PM · Documentation · Landing build log: beat 35 — header pill leads to the landing · +10
# watch · machine
0
commits over 85 days
60
commits 23 Sep
~20 min
between commits since July 1, 2026

See for yourself: the machine's last 24 hours

12:09:50 AM
Wed, Sep 23, 2026 · UTC+3

Pipeline events are real, time is compressed: a day plays out in a minute.

0 found0 took0 served
A machine day in one minute.

This is the real pipeline over yesterday: the machine found, the editor picked, the stories went out to the site. Time is compressed. The work is real.

Yesterday the machine found — stories, and the site got —.

Between “found” and “on the site” stands an editor: most of the raw material goes to the trash, and every rejection has a recorded reason. That is how this entire site was built: more than 400 pages.

This is agentic development. The whole map.1

Each rectangle is a region of the repository; the area is counted from commits since July 2, 2026. A human writes the rules and keeps the final word; the agents execute, and every commit stays in git. Click a region: it has its own story inside.

And this is vibecoding. Two regions out of six.

What people usually call vibecoding lives in two regions: the frontend with the public pages and the backend with the pipeline and the database. Less than a third of the machine.

And it is not only code. It is the whole company.

The same commits, a second coloring. All of vibecoding.tech is run by the same machine of agents: strategy, product, marketing and operations are described in specs. There is more documentation here than code — 387 thousand lines of specs against 391 thousand lines of code, and the code only executes what is written. A setup like this is called a Spec-Driven Company.

Development
frontend · backend · admin · CI
1,488
Strategy
where we're going and why
876
Product
what we're building
464
Marketing
the attention machine: how people find us
528
Operations
playbooks, bookkeeping, company memory
820

A human writes the rules and accepts the work

Your name, in one or two sentences: who you are and what you build. In this machine the human writes the rules up front and accepts the work after the fact; everything else is done by agents.

The operator at the machine console
Price. Speed. Quality.
The old rule of development: pick any two3
pricespeedqualityslowexpensivebadutopia

Okay, cheaper. And faster?

speed

Faster by 13 times6

day 0
fact from git — tap the track: how the machine does it
hypothesis — tap the track: recalculate for your own teamfinish — in ≈2.9 years

Okay, faster. But isn't it all neuroslop?

quality

The machine throws out …

all the machine's raw material over the build — a dot = one unit
43,261
everything that did not pass the editor goes dark

Slop or not — judge for yourself. This page was built entirely by agents: from a line in chat to production.

The new rule of development: pick all three.

In 1913 Ford's assembly line closed the triangle for the automobile. In 2026 agentic development closes it.

price×96
machine · ~$590/mo
team · $56,375
speed×13
machine · 54 days
team · ≈2 years
quality7×1
machine · through the gate and selection — rate it yourself
team · review and QA
total×1,270
cheaper ×96 · faster ×13 · quality ×1
pricespeedqualityslowexpensivebadutopia
footnotes and methodology
  1. Commit zones. The machine assigns each commit a zone by the paths of its files: docs/ and agent rules are "Documentation"; journal.md files are "Journal"; page and component code is "Frontend"; the pipeline, the database and scripts are "Backend"; the control console is "Admin"; the rest, configs and build glue, is "CI/CD". A commit's type is the dominant zone of its files. Merge commits are not counted.
  2. Commits. Counted on the main branch of the vibecoding.tech repository since July 1, 2026; the series is recalculated by the machine automatically, once an hour. The numbers are never edited by hand.
  3. Team equivalent. Replacement cost: the roles it would take to do the same work by hand, × the full cost of an employee to the employer (revision 28.08: median take-home pay from public salary surveys × ~1.5 — income tax, social contributions ~30% up to the cap, hardware and hiring; senior level, judged by the machine's actual output). This is the price of people, not "value created": the headcount and the rates are a hypothesis (estimate 26.08) and our floor — every rate and count is editable right here in this section, and the total and the multipliers in the heading are recalculated honestly. The key metric for a role is a fact: what the machine already ships in that role, from the live snapshots on this same page. The live "while you're on the page" counter spends the payroll by the second: a month is taken as 30.44 days.
  4. Selection funnel. The total over the whole history of the store: counting functions page through the decisions of both editors and the story store; a daily cron writes the sums, the page reads the ready snapshot. "Served" means the story went out to the site or to a channel.
  5. Machine costs. Subscription receipts from the email collector + the OpenAI portal; token usage - account-status snapshots. On the page - only vibecoding.tech's share based on work-session path attribution; excluding database hosting and the cloud - people need them too. The crossed-out duel price and the ladder's second rung are that same compute consumed at public API pricing: the build consumed ~$27,500, paid for through subscriptions ~$1,250 - subscription-compute arbitrage is part of the method; figures are updated by the "subscriptions" handler each tick.
  6. Speed. The delivery unit is a task "from the owner's message in chat to a merge into production"; the series is assembled from the chat history of work sessions × git, 115 tasks, snapshot 27.08. The scale is logarithmic, and the tail on the right is made up of long review sessions with the owner; autonomous pipeline branches (the feed) are not counted, they have no message behind them. Releases per day are counted from GitHub, 300 merges in 11 days, snapshot 26.08. The machine's days in the duel run by the build calendar since July 1. Sources for the "same work by a team" conversion multipliers: execution — our own series (the median machine task in minutes, by hand in hours; ×2 is ultra-conservative); focus — RescueTime measurements (~2 h 48 m productive per day) and Microsoft "Good Day" (~2.5 h of code); coordination — Brooks's law, n·(n−1)/2 channels, an hour per colleague per week = 2.5% of working time; dependencies — team flow efficiency is usually 5–15% (Vacanti, kanban measurements); absences — the Russian Labor Code, 28 days of vacation, plus holidays, sick leave and downtime while people are replaced. The formula is generous to the team on top of that: hiring and onboarding (+2–3 months to the first commit) are left out, as is the slowdown as the codebase grows. With the machine, written specs do the opposite: they make every next run faster.
  7. Quality. Neither machines nor teams have a single number for quality, so what gets compared is the release control loop. Nothing leaves the machine without passing selection: code goes through the gate (2,685 tests on every push + review), content goes through the selection feed (24,597 found, 3,292 served, 87% binned), its own ideas go through the decision log (1,268 of them, each with a "Rejected" field). The page does not award itself a quality multiplier — the quality row holds a live 0 to 1 knob, "does the machine's output measure up to a team" (what is being rated is this very page), and the summary total is honestly multiplied by your score: even at 0.1 it stays three-digit. The first rating you dial in goes into the hall counter (the median is shown from 10 ratings on); the counter is live, stored without personal data, and the audience is self-selected.