Developer · vibecoder · from Ruse, Bulgaria

Hi,I’mAnton.
Ithink,Claudetypes.

Developer from Ruse. I’ve been writing code for a living for about ten years, and these days Claude does most of the typing. This site is just here to say hi.

See what I made
01

Developer, technically

I write code for a living. Well — these days I mostly tell Claude what to write and then check its homework.

02

Vibecoder, no shame

Claude and I are basically brothers at this point. Different parents, same bugs.

03

Runs in the park

An easy 10 km in the park or around the stadium, plus football every now and then. Cheaper than therapy, better view.

04

Calisthenics, strongly said

30 pull-ups, or 20 in a 20 kg vest. Plus a bit of boxing — for tone. And for humility.

Toolbox

Stuff I’ve worked with. Ugh, there’s a lot.

React, Vue, Nuxt, Next, Laravel, Node… I tried to make a neat list and gave up halfway through. Honest summary: I’ve always cared more about how the data moves and how the whole thing is built than about which framework does the moving.

0

my age when I ran my first server

0

pull-ups (20 with a 20 kg vest)

0 km

an easy run in the park

How I work

Roughly three steps

  1. 1

    Data and architecture first

    Where the data comes from, who touches it, where it ends up — and how the pieces fit together. Get that right and the app behaves like a living system. Get it wrong and it behaves like my first WoW server.

  2. 2

    Let Claude type

    The syntax used to eat my twelve-hour days. Now Claude writes it, in whatever language the project needs, and I get to do the fun part.

  3. 3

    Check its homework

    Claude is fast and very sure of itself. Somebody has to actually read what it wrote. That somebody is me.

The path

It all started with a buggy server

Short version: first SQL at twelve, a very long detour, about ten years of writing code for a living, and now an AI that does the typing. The long version is below.

  1. 01

    Age 12: my own WoW server

    Back then you could download a ready-made World of Warcraft server emulator. Mine was very buggy. I put it online anyway and 30–40 people played on it. I fixed quests, poked at the database, ran the website — and accidentally learned what a real IP, MySQL, HTML and JavaScript are.

  2. 02

    The scenic route

    Then ten to fifteen years of side quests: footballer, a furniture company, bartender in restaurants. The little websites never stopped. I just didn’t call it a career yet.

  3. 03

    First dev job: suspiciously good

    Python and Django. Nice people, good pay, everything rosy. So rosy that I got suspicious and quit. Most people leave bad jobs. I left a good one. Still not sure who won.

  4. 04

    The long nights

    No AI back then. Twelve, fourteen hours on tiny bugs or on the “right” architecture. Twenty solutions, delete, twenty more, pick one. Painful — and secretly the best training I ever got.

  5. 05

    Now

    A job or two later, I’m somewhere I actually like. Claude does the syntax, I do the thinking, and nobody has to fix quests in the middle of the night.

app.example.com

Stories

Things that actually happened

At twelve I was the admin of a World of Warcraft server with 30–40 players. The emulator was so buggy that half my job was fixing the quests it broke. The other half was fixing my fixes.
AaAdmin, age 12Private WoW server
My first developer job was great. Good team, good money, zero drama. My brain looked at all that and said: “something’s off here.” So I quit. Ten out of ten decision-making.
TgToo good to be trueFirst dev job
One feature. Twenty solutions. Delete them all. Twenty more. Pick one. That was a normal Tuesday before AI.
TTTwenty-solution TuesdayBefore AI
An AI once decided to restart my dev server and run a “quick production build, just to test.” The build was quick. My afternoon wasn’t. New rule: the servers are mine.
ToThe overly helpful AIVibecoding, early days
Footballer, furniture, bartender — then developer. Not your typical CV. Then again, not many developers can also make you a decent drink.
TsThe scenic routeTen-plus years
Thirty pull-ups, or twenty in a 20 kg vest. An easy 10 km in the park. I’d call it calisthenics, but that would be strongly said.
SsStrongly saidAway from the keyboard

House rules

A few house rules

Data and architecture first, code second

If I don’t know where the data goes and how the pieces fit together, I don’t write the code. Yet.

No duct tape

Fix the problem where it lives, not where it happened to show up.

Language? Whatever.

The logic is the same in every language. Only the syntax changes, and the AI handles that bit.

Trust, then verify

Mostly verify. The AI writes fast, I read slowly. It works out.

Hands off my server

An AI restarted my dev server once. Once.

Twenty drafts, one winner

Old habit from the pre-AI days. The difference: now the twenty drafts take minutes.

FAQ

Questions nobody asked

Depends who’s asking. The typing was never the hard part — knowing what to build was. That part didn’t go anywhere.

Mostly JavaScript and TypeScript — Vue, Nuxt, React, Node, NestJS — plus Laravel, a bit of Python, C++ and C#. I started listing the rest and got tired.

I started at twelve. Then I took a ten-to-fifteen-year detour through football, furniture and bartending. Not late. Scenic.

Yes. Somebody has to. Claude doesn’t mind.

Nope. I’m happy where I am. This site is just here to say hi.

Just for fun

Make yourself a token

Absolutely no reason. Pick a symbol, a colour and a finish, then throw it around. It always comes back — just like bugs.

star · metal · 220px

Symbol

Colour

Finish

Size 220px