TECH MEETUP #43

DEVS WILL
HAVE NOTHING
TO EAT

// „A vývojáři nebudou mít co žrát“

Jan Mikeš
act 1 · hook

SPOILER ALERT

Q: Will developers be jobless?

YES

act 1 · hook

BUT...

NOT ALL
OF THEM

that's the whole talk — you can go for a beer now

act 1 · hook

WHERE WE ACTUALLY ARE

Remember
6 months ago?

we called this "the future"

act 2 · evidence

WHERE WE ARE TODAY

You give it a task.
Not a prompt.

it plans · writes · tests · opens the merge request

it runs unattended — your own hardware, or someone's cloud

it wakes itself up, and asks you when it is stuck

→ Devin · Codex · Jules · Copilot Agent · Factory · Replit · OpenClaw · and a new one every week

act 2 · evidence

THE RECEIPTS

NOV 2022ChatGPT — public, free, and very stupid
NOV 2025OpenClaw — one developer, a side project
MAR 2026Replit Agent 4 — parallel task forking
APR 2026Factory raises $150M Series C
ALL 2026Devin · Codex · Jules · Copilot Agent — shipping PRs
Three years from a stupid chatbot
to "it opened the merge request".
act 2 · evidence

[ MY OPINION — YOU MAY BOO ]

Traditional
engineering,
as we knew it,

HAS ENDED.

act 2 · evidence

THIS IS NOT THE DOT-COM BUBBLE

~100years  — industrial revolution
~40years  — electricity
~10years  — dot-com
~5years  — mobile
18months — this

→ Same shape. Wrong speed.

act 2 · CUT IF LONG

Who does not adapt, dies.
That is why I am not afraid.

And now the honest part:

I have NO IDEA where this leads.
Maybe trouble. Maybe not. Maybe it pops.

self-hosted models? hardware? energy?
→ different talk. no time. sorry.

→ happy to argue about it over a beer

act 2 · evidence

So we built
another one...

yes. the world needed one more of these. hear me out.

act 3 · build

IT STARTED AS AN EXPERIMENT

cadence

June 2026 · github.com/JanMikes/Cadence

"your backlog, in flow"

local · single user · SQLite · no cloud, no docker

capture tasks all day → press PLAY →
plan · implement · verify · deliver

→ It worked. That was the problem.

act 3 · build

THE FLOW — MODELLED ON A REAL TEAM

  TICKET
    ↓
 REFINE  ──→  ARCHITECT  ──→  IMPLEMENT  ──→  CI
    ↑             ↑               ↑           │
    └─────────────┴─── return ────┴───────────┤
                                              ↓
 RETRO  ←──  MERGE  ←──  HUMAN  ←──  REVIEW  ←┘
   ↓
 KNOWLEDGE BASE  ─→  every future task

→ Every stage is a role, not a prompt. A return is normal, not a failure.

act 3 · build

IT DOES NOT LIVE IN A CHAT WINDOW

JIRA      picks the ticket up, asks, moves it
GITLAB    branch · draft MR · review threads · CI
SENTRY    reads the stack trace before planning a fix
LOKI      queries your logs around the incident
SLACK     asks you a question — and waits

→ It works where you already work. 24/7. And it remembers.

act 3 · build

WHY YOU ACTUALLY WANT ONE

RUNNING claude BY HAND
PLATFORM
context in your head
curated knowledge base
you are the process
pipeline, gates, returns
one task, while you watch
N tasks, unattended, 24/7
cost on the invoice
cost per run / stage / task
no audit trail
every prompt replayable
it forgets
it learns

→ memory · process · governance · throughput

act 3 · build

AND NOW THE PART NOBODY PUTS ON A SLIDE

New toys,
new problems.

Who reviews 40 merge requests a day?

AI slop in production:
plausible, tested, reviewed — and wrong.

When an agent misjudges its own work,
75.8% of the time it claims success.

arxiv.org/abs/2605.29442

act 3 · build

OPEN SOURCE · SELF-HOSTED

github.com/
gtfo-ai/platform

Apache-2.0  ·  self-hosted  ·  built in public

knowledge = markdown, in YOUR git repo
delete the platform → the knowledge stays

→ Status: implementation just started. Come break it.

act 3 · build

THE ADAPTATION

EXPERIENCED ENGINEER
OPERATOR
less:   typing the solution

more:   building the CONTEXT
        framing the PROBLEM
        knowing when it is LYING
act 4 · you

A FRIEND ASKED ME

"Could I build myspeedpuzzling.com
 with Claude, exactly like you did?"

My honest answer: YES.

act 4 · you

You know nothing, Jon Snow

Ygritte to Jon Snow: "You know nothing, Jon Snow."
— experience, to everyone with a fast agent
act 4 · you

BUT —
you would need enough time
to step in every single shit I did.

ANYONE can iterate to the same solution.

The real question is how many iterations —
and whether you notice you are wrong.
act 4 · you

MEANWHILE, FOR JUNIORS

−20%employment, devs aged 22–25, from the 2022 peak
15→7%  — junior share of tech hiring (reported)
I am thrilled about what I can do with Claude Code
BECAUSE of 20 years of scar tissue.

A junior does not have that yet.
Software can replace them. Easily.

source: Stanford Digital Economy Lab

act 4 · you

[ MY OPINION — AGAIN ]

Healthy companies with the budget
should invest in juniors.

Not charity. Compound interest.

In 15 years there will be no seniors
if nobody grows any.
act 4 · you

BACK TO THE SPOILER

Will developers
be jobless?

YES. But not you.

— assuming you are already uncomfortable

act 4 · you

HOW FAR IS
YOUR COMPANY?

  1. 1.What tools are you actually using?
  2. 2.What have you built yourself?
  3. 3.How satisfied are you, honestly?
QR code to these slides
techmeetup-43-2
.janmikes.cz

github.com/gtfo-ai/platform · janmikes.cz

I genuinely want to know. Find me — there will be beer.
act 4 · you
Speaker notes — press N to hide

Jump to slide — press O to close

    → / space next slide

    previous slide

    N speaker notes

    O jump to slide

    T light / dark theme

    F fullscreen

    Home / End first / last slide

    ? close this help