Vibecodr

Starting a Vibe

Official platform journal

Posts filed under Vibecoding in Starting a Vibe, Vibecodr's official platform journal. Read platform notes, trust boundaries, launch decisions, and the tradeoffs behind runnable software.

I don't think the best is over. Cover Story

Featured

I don't think the best is over.

I read The best is over and I have been thinking about it since. Not in a clean “this is my response” kind of way. More like it got stuck somewhere. The article is about the internet feeling like it lost something. The weirdness, mostly. The amateur joy. The feeling that a person made something because they had to get…

Read the full story →
More Dispatches
02 Platform Note

What's the Best AI to Code With? Codex or Claude Code?

The honest answer is a little annoying. The best AI to code with is not automatically the one that writes the most impressive first draft. It is not always the one that feels fastest in a demo. It is not even always the one with the model you personally like best on a given Tuesday. The best AI to code with is the one…

Continue reading →
03 Platform Note

After Vibe Coding: What Happens When Your AI-Coded App Works?

After an AI-coded app works, the next question is not simply where to deploy it. The more important question is what kind of public object it becomes. A running app needs more than a URL. If other people can open it, share it, embed it, remix it, bookmark it, or trust it enough to spend time inside it, then the artifa…

Continue reading →
04 Platform Note

How to start vibe coding.

The safest way to start vibe coding is to build one small artifact, make the desired behavior observable, run it, break it, inspect it, and only publish what you can honestly explain. This guide explains how to choose a first project, write a useful prompt, constrain the AI's output, test the result, avoid secrets, an…

Continue reading →
05 Platform Note

What is Vibecoding?

The beginner is often using AI to cross the blank-page gap. The professional is often using AI to compress mechanical work and keep more mental space for system design. In both cases, the human is not removed. The human moves from typing every token to supervising a living draft. That is why the word "vibe" is better…

Continue reading →