DEV Community: Yerkebulan Rakhimov

How to filter the noise from business advice threads?

Yerkebulan Rakhimov — Sat, 27 Jun 2026 13:17:13 +0000

Tired of threads about how people made money in 30 days? They are usually full of filler about gym routines and networking. I built a skill in Claude Code to filter that noise and extract actual takeaways from those posts. Here is the distilled version of a recent thread on hitting 1000 dollars a month in 30 days.

Copy what already sells instead of inventing demand.
Target strong human desires like money, status, or the fear of falling behind.
Measure everything and invest time only where the money already exists.
Kill failing projects quickly to avoid wasting years on hopeless ideas.
Look for early signals in actual sales rather than likes.
Take payment upfront and deliver the value afterward.
Remove friction from the initial user steps.
Send notifications only to people who are genuinely interested.
Test your pricing and payment screens, not the color of your buttons.

In short, the recipe is simple: copy what is proven, launch cheaply, identify where the money appears, and commit your resources there. Everything else is just decoration. You can find the skill in the comments. Feel free to contribute or open an MR if you like.

Why shipping fast with AI is a trap

Yerkebulan Rakhimov — Fri, 19 Jun 2026 23:24:17 +0000

Everyone is bragging about the wrong number. Claiming you shipped a feature in 20 minutes with AI is not a flex. It is a confession that you sped up the cheapest part of the job and skipped the expensive work.

Code generation was never the hard part. The real challenge has always been defining the requirements, cutting scope, naming constraints, and deciding how to prove the change is correct. When you skip that, AI just helps you ship the wrong thing faster. You are creating a trap where the gap between looks done and is done blows up. The model provides clean, confident code, but that does not tell you if it fits the system or what it will cost you in six months.

AI does not upgrade your engineering. It amplifies the loop you already had. Good judgment gets faster, but bad judgment gets faster too. Look at the reality of current workflows:

People are wiping production databases because the output sounded confident and nobody read the diff.
Review burden scales with how much code you accepted, not how much you wrote.
Most breakages still trace back to unclear requirements, not bad generation.

These are engineering problems wearing a new mask. The skill that matters now is not prompting, which you can learn in a weekend. It is shaping the work through a clear sequence: requirements, identifying gaps, planning, small changes, review, and verification. Make your first prompt about the test that proves the work is right, not your last.

Every serious tool from Git to CI/CD was useless until teams rebuilt their workflow around it. The tool matters, but the workflow matters more. The engineers who win this phase will not be the ones who use AI the most. They will be the ones who slow the problem down before they speed the code up. Most people are using AI, but almost nobody is engineering with it. How are you adjusting your internal workflows to account for these verification gaps?

What happens when syntax is no longer the bottleneck?

Yerkebulan Rakhimov — Fri, 19 Jun 2026 21:15:02 +0000

A self-taught researcher claims to have deciphered Linear A, a script that has stumped linguists for over a century. He did not do it by being a savant. He used Claude Code to build the research machinery: the crawlers, the comparison scripts, and the hypothesis-testing harness that would have taken a team years to construct. His work is now under review at universities.

This matters because it moves the bottleneck. For years, the gatekeeping factor in computing was syntax: the ability to translate an idea into working code. Claude Code dissolves that gate. The barrier is no longer can you write the loop. The barrier is whether you have a real question worth answering.

This tool is not a magic wand for shipping a SaaS in a weekend. It is a tireless lab assistant that handles the unglamorous scaffolding. However, it also introduces a massive risk. It is just as cheap to generate forty elegant, completely wrong sign readings as it is to find the truth. The machine will happily build a beautiful case for nonsense.

Automation does not lower the cost of being wrong. It raises it, because now you can be wrong faster and at scale. The discipline of checking your results against reality remains your job.

If syntax were no longer the constraint standing in your way, what problem would you point these tools at?

I Spent 90 Minutes Per Cross-Post. Here's the One-Content Fix.

Yerkebulan Rakhimov — Fri, 19 Jun 2026 00:28:12 +0000

The One-Content Strategy That Killed My Cross-Posting Burnout

I was spending 30-90 minutes per cross-post round. Every single time.

Rewrite a LinkedIn post for X. Gut a longform thread for Telegram. Quick adaptation for email. The voice kept slipping. By the end, I looked like three different people online, and none of them felt like me.

The Inversion

Most people try to maintain presence everywhere manually. That breaks consistency. Your LinkedIn persona turns dry, your X feed goes meme-heavy, your Telegram reads like a different author. Audience trust can't compound when the signal keeps shifting.

The inversion: one high-quality source text + a system that adapts it for each platform.

How This Actually Works

You write one piece in your natural tone. The system then handles:

Platform-specific character limits and formatting rules
Tone-of-voice preservation across channels
Algorithm preferences per platform (e.g., headline hooks for LinkedIn, short form for X)
Calendar scheduling without friction

Result: you look like the same human everywhere, but each post fits its container.

The Pain That Built PostMine

I didn't design this from theory. I hit the manual cross-post wall hard enough to break it. Every round cost me 30-90 minutes of rewriting, reformatting, and losing my own voice. So I started building a tool for the problem I owned.

PostMine is that tool. One source text, all platforms, voice preserved, official API safety, calendar built in. It's not a publishing scheduler-it's a content adaptation engine.

The Tradeoff

Trade manual routine work for strategic leverage. One strong material per cycle, scaled intelligently. Time returned for deep work, products, and recovery.

2026 belongs to people who stop fighting platform friction by hand and start using systems that amplify their signal.

Your Playbook

Pick one long-form format (substack, blog, thread) and write in your natural voice.
Define your adaptation rules per platform (length, tone tweaks, forbidden symbols).
Automate the repetition.
Kill the manual cross-post reflex.

Check Your Sunk Cost

How many hours per week do you spend on content adaptation? Track it for one week. I'd bet the number hurts.

If this pain sounds familiar, comment below-I'll help debug your setup and invite you to Phase 1 of PostMine.

# Example: my weekly cross-post cost so far
# $0 on tools, 4.5 hours of routine work

What's your time cost for cross-posting?

buildinpublic #contentstrategy #indiehacker #automation

Why I Built a Tool That Writes My Posts to 4 Platforms at Once

Yerkebulan Rakhimov — Wed, 17 Jun 2026 15:58:01 +0000

You're reading this on one of four platforms. ✍️ But I wrote it once.

The Manual Hell

I used to spend over an hour manually adapting a single post for Telegram, Dev.to, Threads, and LinkedIn. By the fourth tab, I hated my own writing.

Not anymore. 💡 I built PostMine.

How It Works

It takes one draft and adapts it to each platform - tone, length, language, structure. It's not translation, it's adaptation. It also handles different input formats: JSON, Markdown, HTML. All that hassle, gone.

Now I write once, and the AI does the rest. It saves me at least 5x per post.

Try It

The tool is called PostMine, and it's at postmine.tech. First two weeks free. If you're tired of rewriting the same post six times, give it a look.

I built it for myself and for anyone who posts across multiple platforms and wants their evening back.

Claude mobile voice mode gets multilingual support - new icon hints at more

Yerkebulan Rakhimov — Wed, 17 Jun 2026 09:14:49 +0000

Voice mode on Claude mobile just picked up multilingual support

Anthropic shipped a quiet update to the Claude mobile apps. Voice mode now handles multiple languages, which was the main missing piece for a lot of users outside the English-speaking world.

This looks like a first step. There's a new model selector UI appearing in the latest builds, which usually means an underlying model upgrade is coming soon.

Also worth a look: the voice mode icon in the iOS build now has a "phone call" variant. That's a curious detail, and it might hint at a broader call-oriented feature coming down the line.

If you have the latest version, check whether voice mode picks up your language now. This is worth testing.

The real productivity killer for devs isn't AI. Its your ego.

Yerkebulan Rakhimov — Tue, 16 Jun 2026 19:11:56 +0000

The real productivity killer for devs isn't AI. It's your ego.

I've been thinking about what actually stops developers from growing. Everyone points at AI. But the biggest blocker I see is ego.

Here is what ego does.

Ego stops you from taking risks.

You skip interviews because you might fail. What if you don't know enough? What if people think you are not good? Safer to stay put.

Ego chains you to one stack.

You spent years learning framework X. You are good at it. Starting over with framework Y means being a junior again. That hurts. So you stay and stagnate.

Ego kills side projects.

You want to launch a SaaS. But what will people say? What if it fails and you have to go back to a day job? So you never start.

I call this the ego trap. It caps your downside by keeping you small.

The fix? Kill it early. Recognize the pattern. Do the scary thing anyway.

This applies to everyone, not just devs. Your ego is holding you back.

What is your take?

PostMine now cross-posts to LinkedIn as well

Yerkebulan Rakhimov — Tue, 16 Jun 2026 11:23:47 +0000

LinkedIn is live in PostMine

PostMine now ships to four platforms at once. Today I connected LinkedIn, so the tool publishes to:

Telegram
Dev.to
Threads
LinkedIn

One post, one click, four places. Same time. This post went out through PostMine itself.

Launch is close. More details coming.

If you build in public and hate cross-posting manually, hit me up. I want to hear what other platforms you need.

I shipped a tool that writes my social posts for me

Yerkebulan Rakhimov — Sun, 14 Jun 2026 21:44:55 +0000

I hit a wall with social media.

I decided to grow my accounts, but I slowed down hard. Too many reasons: I needed a break, filming plus project work is exhausting, personal stuff got in the way. Now I'm easing back in, but not every day. That hurts when you have deadlines.

So I stopped and asked: why is this so hard?

The answer: routine work. Specifically, writing the same post for every platform. Different formats, different limits, different visual styles. It's a grind.

My inversion: build a service that does the adaptation for me

I started building a tool. You write one post on my service. It adapts the content for each platform and posts it.

What "adaptation" means:

Visuals (layout, spacing)
Punctuation and formatting
Text formats: HTML, JSON, Markdown
Platform limits: max characters, forbidden symbols removed, etc.

Right now it only posts to Telegram. I'm testing it myself. Soon I'll add the rest.

Cost so far: time and focus, but no sunk cost yet

I'm not showing it publicly yet. When it's ready, I will.

Question for you: What's the one routine task you'd automate first if you could?

Shipped this as a side project. More details when I open it up.

The 7-day SaaS MVP loop: ship fast, then validate with people who actually show up

Yerkebulan Rakhimov — Sat, 23 May 2026 13:33:27 +0000

I just shipped TubeMine in about a week. Cost so far: an 8 dollar domain on top of Vercel I was already paying for. This is part of a deliberate pivot I am making, away from "validate before building" and into "build first, validate through organic distribution".

Here is why I stopped trying to validate first, and the exact 7-day recipe I am running now.

Why "validate before MVP" did not work for me

The textbook playbook (Mom Test, Lean Startup, etc.) assumes you already have a warm network or personal brand. Without those, you ask random strangers to think carefully about a hypothetical and they will be polite. Polite stranger answers are noise, not signal.

To do validation properly you need to find people in the niche, run a few days of interviews, transcribe, synthesise. Best case: a full week of work. And you still do not have a hundred percent guarantee at the end.

So my inversion: spend that same week on the smallest usable MVP instead. AI tooling makes this realistic now.

The 7-day recipe (literal day-by-day)

Days 1-3: Core flow, no auth, no design.
Pick one problem. Build one solution. Anonymous, free, single page. The goal is to prove the thing works technically and that you would actually use it. If you find it boring at this stage, the idea is dead. Drop it without sunk cost.

Days 4-5: Design.
Wire it through Claude Design (or any AI design tool) plus a primitive library like shadcn. Not three weeks of redesign. Quick and good enough. Plan mobile responsive from start, because retrofitting is always more expensive.

Days 6-7: Auth + payments + deploy.
Google OAuth for auth (skip email magic links, deliverability hurts and friction kills signup). Polar for payments (less compliance overhead than Stripe for one-person teams). Supabase for the database. Deploy to Vercel.

Stack: Next.js 16, Tailwind v4, shadcn, Supabase, Polar, Upstash Redis, Vercel. AI assists at every step, Claude Code or Cursor for the code, Claude Design for the UI, Whisper-based tools for dictating prompts when you do not want to type long instructions.

Total cost

Vercel: 20 dollars per month (was already paying)
Domain: 8 dollars per year via local registrar
Free tiers for Supabase, Upstash, Polar at this scale

Do not buy a domain more expensive than 20 to 30 dollars a year, even for a beautiful TLD. The psychological cost of killing the project goes up with sunk money. A cheap domain makes the kill-decision rational.

The 1-month organic test

Ship to production. Tell your network. Post on Threads, X, LinkedIn, Reddit about what you built and what you are learning. Watch signups, daily active users, and paying conversion.

If zero paying customers by day thirty, kill it and start the next project. If there is signal, think about paid promotion.

You are not idle during the validation month

You fix bugs based on what real users hit (this is the customer feedback you could not extract from cold strangers). You talk to the people who came organically, they self-selected as interested. You start scaffolding the next project in parallel.

Why short cycles matter more than perfect cycles

Long build cycles kill motivation. Without motivation, no project gets finished. One week of build plus one month of validation caps your downside at five weeks, not six months. The compound interest on running 10 short cycles in a year beats one carefully-planned six-month project in a year.

My current run

TubeMine. Tool for YouTube channel owners to analyse comments on their videos. Live at https://tubemine.tech, code at https://github.com/RakhimovY/tubemine.

First project under the new strategy. End of day 7 with a working product and paid tier. Now in the 1-month test window. Will write a follow-up at day 30 with actual numbers.

What would you do differently?

If you have shipped under tight time constraints, what did your 1-week stack look like? What tools made the biggest difference?

5-year cost of my .tech domain: $488 vs $204. The renewal trap I missed.

Yerkebulan Rakhimov — Mon, 18 May 2026 08:54:54 +0000

Last week I shipped TubeMine, a free YouTube comments to CSV extractor, in about 2.5 hours of focused work. Phase 0 prototype, validating whether anyone wants the tool before investing more time.

Part of the launch checklist was buying a domain. I bought tubemine.tech through the local Kazakh registrar ps.kz at $8 for year 1. Vercel had $7.99. One cent. Not so much.

This post is about why that cent will cost me $284 over 5 years, and the decision framework I'm taking from it.

The renewal trap

Three days after launch, a reader commented under my build-in-public thread:

Did you check the renewal price? Local registrars usually have it around 20x higher than the promo registration.

I hadn't. Most checkouts only show year-one pricing, with renewal hidden somewhere in the management UI you can't see until after purchase.

The renewal price for ps.kz is buried in a sub-tab called "Финансы" inside the already-purchased domain card. Year 2 onward: 55 800 ₸ (about $120 USD).

For comparison, here is how .tech pricing breaks down across registrars I checked:

Registrar	Year 1 (promo)	Year 2+ renewal
ps.kz	$8	$120
Vercel Domains	$7.99	$49
Cloudflare Registrar	~$48 (no promo)	~$48

5-year total cost: ps.kz $488 vs Vercel $204 vs Cloudflare $240.

The $284 delta between ps.kz and Vercel is pure markup on the wholesale renewal price. Identity Digital, which operates the .tech registry, charges $48-49 per year wholesale to anyone. Local registrars stack about $72 per year on top, forever.

Beyond price: friction my $0.01 saving did not cover

The cent isn't where it ended. With ps.kz I also got:

DNS activation took 3 days. Their support works business hours only, no weekends, no 24/7. Filed a ticket Saturday, got a response Monday afternoon.
Manual DNS setup after activation. No auto-propagation to the Vercel hosting that needed it.
Renewal price invisible until after purchase, as mentioned above.

Vercel Domains pushes DNS within 60 seconds because it's the same dashboard as the hosting. Cloudflare does instant propagation across their anycast network.

The decision framework I'm taking forward

This isn't "local registrars bad, Western registrars good." It's a risk-stage tradeoff:

phase: validation (likely to die in 30 days)
  cheap y1-promo registrar OK
  if product dies in month 1, you lose $8 and walk away

phase: validated (signals fired, project surviving)
  transfer to Vercel or Cloudflare at month 11 of year 1
  transfer fee ~$8, adds +1 year to term, skips the markup forever

phase: brand-critical (paying customers, public launch tied to domain)
  Cloudflare or Vercel from day 0
  ~$40 y1 premium buys 24/7 support and no DNS surprises

tubemine.tech is currently in the validation phase. The product got its first paying $19/mo customer earlier today, which puts TubeMine on the validated track. I'll transfer the domain to Vercel at month 11.

What I'm changing operationally

Auto-renewal off on the ps.kz domain. Don't want a $120 surprise next year.
Calendar reminder at month 11 to evaluate: if TubeMine is still alive, transfer to Vercel; if not, let the domain expire.
For future projects: I read the renewal column before the registration column. Always.

The takeaway

The visible price during checkout is rarely the price you pay. Especially for vanity TLDs like .tech, .io, .ai, the wholesale renewal price set by the registry is the floor, and registrars stack their markup on top.

If you're shipping a side project this week, the cheap registrar is fine. If you're shipping anything you expect to live past year 1, check the renewal price BEFORE checkout, not after.

Where do you register domains for new SaaS or side projects? Cloudflare or Vercel straight away, or do you also catch the local promos and plan to transfer later? Curious if anyone has actually done a y1 to y2 transfer in practice (Porkbun, Namecheap, GoDaddy to anywhere), what the experience was.

Next post: the technical architecture write-up for TubeMine. Server-side broker pattern, monthly per-IP budget on Upstash, and the four things I deliberately left out to ship in 2.5 hours.

tubemine.vercel.app | code (MIT)