A subdomain of vibe engineering

vibeswe

Build. Ship. Learn.

A Vibe SWE is a software engineer who is AI-native from day one — orchestrating models as senior collaborators while staying the human in the loop who owns the intent, the review, and the ship.

READ THE SHIP LOOP ADD A SHIP CARD
01What is a Vibe SWE

Farming didn't end with the tractor. Seafaring didn't end with the engine. The craft evolved — and so does software engineering.

What always mattered still matters: taste, judgment, ownership, being accountable for what goes out. What's new is the load — juggling several AI tools, a queue of stakeholder requests, and security expectations, all while shipping something real this week. Vibe SWE is the practice of doing that well, on purpose, without pretending the model is in charge.

Past craft — still load-bearing

  • Taste — knowing which version is actually good
  • Judgment — choosing the tradeoff, not just the option
  • Ownership — your name is on the ship
  • Clear communication — with humans, first

Future stack — new every quarter

  • Multi-tool orchestration across agents and editors
  • Stakeholder clarity — translating asks into intent
  • Security awareness as a default, not a phase
  • Proof of ship — evidence, not vibes
02Where we sit

Three words get used interchangeably. They shouldn't be.

Prompt & hope

Vibe coding

Describe it, accept whatever comes back, move on. Great for throwaways and demos. No accountability attached.

You are here

Vibe SWE

Human-in-the-loop builders. AI-native from day one, but the human sets intent, reviews the diff, and owns the ship.

Senior accountable practice

Vibe engineering

The full discipline: systems, evals, security, on-call, org-level responsibility for AI-assisted software.

Vibe SWE is a subdomain of vibe engineering — not a competitor to it. It's the practitioner's entry point: the day-to-day habits that make you trustworthy at that scale later.

Sibling practice for research and data work: vibescientist.com.

03The Ship Loop — v0.1

Build. Ship. Learn.

Three steps you can say out loud in a standup, and three deeper notes for when the work gets serious. Cite it, argue with it, fork it.

  1. 01

    BUILD

    Set intent, then let the model draft.

    Deeper — Intent

    Write the outcome and the constraints before you prompt. Models are senior collaborators — brief them like one. If you can't state what 'done' looks like, you're not ready to build.

    Test: can you say what 'done' looks like in one sentence?

  2. 02

    SHIP

    Put it in front of reality.

    Deeper — Prove

    Small, reversible, visible. Show evidence it works: a test, an eval, a screenshot, a user. Security is part of shipping, not a later ticket.

    Test: what is your evidence, and who else can see it?

  3. 03

    LEARN

    Read what happened, change your defaults.

    Deeper — Own

    You own the outcome, including the parts the model wrote. Keep what worked, retire the tool that didn't, and write down the judgment call so the next loop is faster.

    Test: what default did you change because of this ship?

build → ship → learn → build → ship → learn …

Read the long version: What is a Vibe SWE
04Ship Wall

Real ships from humans in the loop.

3 cards

2026-09-06ship-001

vibeswe.com in an afternoon

Joe Cox — Builder / PM

A static manifesto site defining Vibe SWE, the Ship Loop, and an open Ship Wall anyone can PR into.

Lovable
Claude
Tailwind
Cloudflare Pages

Reviewed & owned

Wrote the positioning myself, reviewed every line of copy, checked mobile layout and contrast before shipping.

JOEWCOX.COM
2026-08-22ship-002

Eval harness for a support triage model

Placeholder Builder — New grad SWE

A 200-case eval set plus a scoring script that gates deploys when accuracy drops below the agreed bar.

Cursor
GPT-5
Python
Hugging Face Datasets

Reviewed & owned

Chose the failure taxonomy, hand-labelled the golden set, rejected two model-written test cases as ambiguous.

HUGGING FACE
2026-07-14ship-003

Legacy billing job, rewritten and de-risked

Placeholder Builder — PM turned SWE

Replaced a nightly cron with an idempotent queue worker, behind a flag, with a rollback path documented first.

Claude Code
Postgres
GitHub Actions

Reviewed & owned

Read the diff end to end, wrote the rollback runbook, insisted on a dry-run week before cutover.

GITHUB

Seed cards are placeholders — replace them with your own by opening a pull request.

05Contribute

Add a Ship Card in four steps.

  1. 01

    Fork the repo

    vibe-swe on GitHub (coming soon). No issue required — small PRs welcome.

  2. 02

    Open SHIP.md

    Copy the template on the right and paste it at the bottom of the file.

  3. 03

    Fill in what you owned

    The 'owned' line matters most: what you reviewed, rejected, or decided. A card with no human judgment in it gets sent back.

  4. 04

    Open the pull request

    Title it 'ship: <your title>'. Merged cards appear on the wall on the next deploy.

SHIP.md — templatemarkdown
### <Ship title>
- builder: <name>
- role: <new grad SWE / PM / staff eng / founder>
- shipped: <one sentence: what exists now that didn't before>
- tools: <Cursor, Claude Code, GPT-5, Tailwind, ...>
- owned: <what you personally reviewed, rejected, or decided>
- link: <optional GitHub or Hugging Face URL>
- date: <YYYY-MM-DD>