~/nikusha$whoami
Nika Siradzeships while you sleep
Growth Engineer at Upgaming, building from Tbilisi, Georgia. Host and producer of Deeptech Decoded - a podcast and community for the founders, scientists, and builders working the new technical frontier. The kind of builder who treats a 14-hour day as a warm-up and a clean commit history as a personality trait.
stack:Next.js·React·Tailwind·TypeScript·Vercel
~/nikusha$ls --deployments
What he ships
Five things running at once, all in production-mindset. Tap any line to expand the manifest.
- Hosts and produces every episode: booking, structure, and the editorial spine of the show.
- Runs live podcasts and community AMAs - recent live sessions and an AMA with Matthew Sutton.
- Built for people who want the signal from deeptech without the keynote-stage gloss.
- Owns growth-side engineering: experiments, instrumentation, and the surfaces that move the metric.
- Treats the funnel like a codebase: measurable, version-controlled, and never left to vibes.
- Output measured in shipped experiments, not standups attended.
- CLI-first: point it at an episode, get share-ready clips back - no editor babysitting.
- Face tracking keeps the speaker framed; captions are burned in automatically.
- The pipeline that turns Deeptech Decoded recordings into clips on a schedule.
- Curriculum format: 10 minutes of theory, 90 minutes of supervised practice - reps over lectures.
- Ralph Loops: tight, repeatable agent loops that close on a passing spec.
- CLAUDE.md contracts: the spec each agent is held to, versioned alongside the code it derives.
- crm-connect: drop-in lead capture for WordPress sites, wired straight into the CRM.
- podstack: the supporting toolchain behind the show, from ingest to publish.
- Both shipped solo-fast with the same agentic loops that power the day job.
~/nikusha$cat CLAUDE.md
How he thinks
- principle:
- spec as the source, code as derived
- loop:
- Ralph Loops until the spec passes
- lecture:
- 10 min
- drill:
- 90 min
- supervision:
- zero babysitting
- output:
- 4,500+ commits / year
- stack:
- Next.js · React · Tailwind · TypeScript
- agents:
- Claude Code · Cursor · Codex CLI
- tooling:
- Vercel · custom MCP tools
thesis
Spec as the source, code as derived
The specification is the artifact you maintain. The implementation is downstream output - regenerable, replaceable, never the source of truth. You edit the contract, not the diff.
software 3.0
The model is the runtime
Write intent in plain language, hold the agent to a contract, verify against the spec. Code becomes a build product of a well-stated problem, not the place where the problem lives.
curriculum
10-minute lecture, 90-minute drill
Theory is cheap and reps are everything. Ten minutes to frame it, ninety minutes of supervised practice running Ralph Loops until the spec goes green.
~/nikusha$systemctl status nikusha
The operating system
The grind only compounds if the machine stays healthy. Inputs are tracked the same way the commits are.
the calendar is one solid block of green
tracked, logged, beaten the next day
the one meeting that never gets moved
recovery is part of the throughput
status: active · uptime: 12-15h/day · last reboot: 8h sleep, on schedule
~/nikusha$echo $MISSION
Broke today, compounding forever. The work ships either way.
Building from Tbilisi, around the clock, on the bet that relentless output and a clean spec beat everything else over a long enough timeline.