The roast
I asked for a roast and got an accurate one. Kept here, unedited, to be re-read on a day when I am about to start something new.
28 September 2026, 18:36, Tashkent. I typed “roast me” into ChatGPT. What came back was funnier than it had any right to be, and closer to the bone than I expected, so it goes in the garden rather than in a chat log I’ll never open again.
Rule for future me: read this before starting the next thing, not after.
Bro, your biggest problem is that you’re way too ambitious for the amount of peace you allow yourself to have.
You wake up and somehow have 14 problems that didn’t exist yesterday.
You’ll be like: “I need to become a better Go engineer.” Then: “Maybe I should build an open-source alternative to Meilisearch.” Then: “Actually, AI café in Uzbekistan.” Then: “What if I make Uzbek Scrimba?” Then: “Also I need to grow Gopher Uzbekistan.” Then at 2 AM: “What does it mean if a girl puts Another Love on her profile?”
BRO. PICK A SERVER TO DEPLOY.
You have the mind of a founder, the sleep schedule of a university student, and the decision-making process of someone standing in front of a pharmacy shelf for 45 minutes comparing zinc tablets.
And you don’t just overthink things. You industrialize overthinking.
A normal person sees a relationship problem and thinks: “We should talk.” You think: “Let me formulate 12 questions to evaluate religious compatibility without making it obvious that I formulated 12 questions.”
You’re also hilarious with your engineering standards. At work: “We need ADRs before implementation. Business logic must be documented. PRs need self-review. WIP must remain draft. Scalability considerations should be included.” Meanwhile your own life: no ADR, no documentation, directly merged to production.
Your projects are the same. You don’t finish things. You promote them to “interesting ideas.” Telegram bot, AI café, browser extension, education platform, Go OSS project, marketplace, community, some SaaS idea. And every few days your brain goes: “Wait… I have another idea.”
My brother, you don’t need another idea. You need to close an issue.
And your relationship with Claude Code is getting suspicious. You’re basically becoming a manager of AI agents while simultaneously trying to prove you’re a strong engineer. You’ll say: “I want engineers to understand the architecture and write solid code.” Then: “Make me a prompt so Claude can implement the entire onboarding flow.”
And you have this funny obsession with making everything “simple.” Make this Slack message simple. Make this Uzbek simple. Make this UI simple. Make this explanation simple. Brother, nothing about your life is simple. You just want the sentence to be simple.
And the funniest thing is you clearly care about how you’re perceived. You want: Lead Software Engineer. Community Lead. Founder energy. Strong engineer. Open-source guy. But then you come here like: “Is 5 hours of sleep enough?” “Is this rice normal?” “Which testosterone supplement?”
You’re basically trying to maintain the public image of Linus Torvalds while privately operating as a confused 21-year-old with 37 browser tabs open.
And somehow… the worst part? You actually have the ability to do most of the things you’re talking about. That’s why the roast hits. Your problem isn’t lack of ambition. It’s that your ambition has absolutely no fucking queue.
Why this is in the lab and not in a screenshot folder
Because the lab already proves the point. Open the explorer on the left: this garden has a folder called ideas and every note in it is something I decided was worth building. shoshshi is live. yamu shipped. FilterCam shipped inside someone else’s product. maymun is a four-product brief written by one person.
Three of those are real. The roast isn’t saying I can’t build. It’s saying I keep opening tabs faster than I close them.
Stub — for the version of me reading this later. Write the answer underneath, dated. Not a plan with twelve items: one sentence about what is in front of the queue, and one about what waits.
comments