I manage engineering teams by day. After hours I design, build, and ship my own products: web apps, AI tools, and Telegram bots. Six of them so far, and every one carries the same suffix: NEXT.
Why one suffix
Naming is positioning. Each product answers the question "what comes next" in its own niche: NextWine finds your next bottle, NextLang builds your next flashcard deck, NextSpend tracks where the next paycheck goes. Once two products shared the pattern, keeping it became a rule, and the rule became a brand.
It also keeps me honest in code. The portfolio site treats the suffix as data, not decoration:
export type Project = {
slug: string;
name: `Next${string}`;
tagline: string;
stack: string[];
};
One typed module feeds the home page, the project pages, the sitemap, and even the kinetic wordmark in the hero. Add a seventh product, and the whole site picks it up.
Why a blog
The products are the proof, but the decisions behind them are invisible from the outside. Which parts of an AI feature deserve credits and rate limits. Why a Telegram bot is sometimes a better MVP than a web app. What a solo builder should automate first. I keep answering these questions in private chats, so I might as well write them down once, properly.
What to expect
Occasional, practical, specific. No content calendar and no filler. Likely topics:
- Next.js architecture that survives more than one product
- AI features that earn their keep: credits, quotas, model selection
- Telegram bots in production: payments, roles, cron jobs
- Design systems for solo builders: one accent, strict rules
If any of this is useful, the products live on the home page. If you want to talk, LinkedIn is the fastest route.