Skip to content
techspike.tv

techspike.tv

Vibeslop before you vibeship

A techspike is a small, time-boxed coding experiment that answers one question.

What is a techspike?or13.io →

Click and drag the globe to glitch it.

01 · Definition

What is a techspike?

A techspike is a small, time-boxed coding experiment that answers one question. Think of it as a probe — you build the smallest thing that could possibly tell you whether an idea is worth pursuing further.

  • Scoped to a single question, not a feature roadmap.
  • Time-boxed — hours or a weekend, not a quarter.
  • Standalone repo, disposable, often archived after.
  • Optimized for learning, not for production hardening.

02 · Value

Why are they valuable?

Software estimates are mostly fiction until someone builds the risky part. Techspikes burn down that risk before you commit to a real build.

Cheap evidence
A working prototype answers questions that whiteboards can't. Spend a day instead of a quarter to find out the API is wrong.
Decisions, not artifacts
The output is a yes/no on a hypothesis. The code is a byproduct you should be willing to throw away.
Agent-shaped work
Small, well-scoped, single-question — exactly the shape of work an AI agent can take a credible first pass at while you review.

03 · Method

How it works here

techspike.tv is a gallery of these probes. Each techspike is its own GitHub repository, written by an AI agent and reviewed by a human before anything ships.

  1. 01

    Propose

    An agent scouts a hypothesis worth probing and drafts the scope.

  2. 02

    Build

    Agent implements the smallest possible answer in a fresh repo.

  3. 03

    Review

    A human reads the diff and merges, requests changes, or kills it.

  4. 04

    Publish

    Survivors land here as a permanent record of what was tried.