I'm running a 4-week live course on agentic coding. I don't write code anymore — I instruct AI to do it. Now I'm teaching you how.
Starts April 24. $299.
tskulbru.dev/courses/agentic-coding
#AgenticCoding #ClaudeCode #AI #BuildWithAI
A friend asked why I keep building apps for such small markets.
Honest answer: the thank-you messages hit different.
"This changed our morning routine" or "I finally feel safe recording" — that's not a vanity metric. That's the whole point.
Small audience, real impact.
The thought has crossed me :)
We moved ~40 Go microservices into a single monorepo. Path-filtered CI, Go workspaces, independent deploys — here's how it went and what we learned.
tskulbru.dev/posts/migrating-microser...
#golang #monorepo #devops #microservices
Indie dev tip that changed everything for me:
Ship when it's 80% ready.
The last 20% of polish takes 80% of the time — and half of it won't matter to your first users anyway.
Real feedback from real people beats another week of "just one more thing."
What's your shipping threshold?
Hot take: the best apps I've used lately all do fewer things, not more.
There's something powerful about a tool that says "this is what I do" and does it really well — no feature creep, no settings rabbit holes.
Constraints force clarity.
What's a single-purpose app you couldn't live without?
One thing nobody talks about enough with solo dev: the silence between launches.
You ship, get a burst of energy, then it's just you and the code for weeks.
The fix isn't "find a cofounder." It's small rituals — a walk before coding, sharing progress publicly, knowing when to close the laptop.
Looks fun!
Just to be clear, the videos are there and everything «works» its just that the permissions across google folders isn’t correct somyou cant open them across accounts. I’m also going to make some changes to opening video part too. Stay tuned.
Hi, thanks for the support! I have a fix in the works, i have to expand the permission from Google. Hopefully it will be out soon, awaiting approval from google and then Apple. Sorry about that!
Something I keep relearning: the people who need your app most are often the least technical.
They don't care about your architecture. They just need it to work — instantly, obviously, silently.
Best compliment I've ever gotten: "I didn't have to think."
How do you test for that?
Started doing short-form video marketing. No trackable links — just "search for my app."
Downloads went up. Analytics can't explain why.
Best I can do is spot the trend shifts in plask.dev and trust the process.
Anyone else flying blind on attribution?
Most apps treat privacy like a premium upsell.
But for some users, privacy isn't a preference — it's safety.
When "data stays on device" is your default, you're not limiting your product. You're respecting why someone downloaded it.
Should local-first be the default for personal data?
Linetris #23 (Extreme)
🟥 15 lines | 2:39
⬜🟥⬜🟥⬜🟥🟥🟥
⬜🟥🟥🟥🟥⬜⬜⬜
🟥🟥🟥🟥🟥🟥⬛🟥
🟥🟥🟥🟥⬜⬛🟥🟥
⬜🟥⬜🟥🟥🟥🟥🟥
🟥⬛🟥🟥🟥🟥🟥🟥
⬜🟥⬜⬜🟥🟥🟥🟥
🟥🟥⬜🟥🟥🟥🟥⬜
apps.apple.com/app/id675985...
If you have time to give me a AppStore review, that would be awesome!
Building for a small audience is harder than it sounds. No generic UX patterns, no broad assumptions. You have to actually understand the people.
But when you nail it, retention is almost unfair. Niche users stick because nothing else fits.
Smallest audience you ever built for?
Accessibility isn't a feature you bolt on at the end. It's a lens you design through from day one.
→ Test with VoiceOver early, not after launch
→ Larger tap targets help everyone
→ If your UI needs a tutorial, it's too complex
What accessibility wins have surprised you?
Linetris #20 (Medium)
🟦 56 lines | 10:23
⬜⬛⬜⬜🟦🟦🟦🟦
🟦⬛🟦🟦🟦🟦🟦🟦
⬜⬜🟦🟦🟦🟦🟦🟦
🟦⬜🟦🟦🟦🟦⬜🟦
🟦⬜🟦🟦⬜⬜⬜🟦
🟦🟦🟦🟦🟦⬜🟦🟦
🟦🟦🟦🟦🟦🟦⬛🟦
🟦🟦🟦🟦⬜⬜🟦⬜
apps.apple.com/app/id675985...
Thanks! It's super addictive 😅
I vibecode a lot of apps and web saas. Tracking analytics across all of them is painful—traffic drops, ad effects, what needs attention?
So I built Plask. Anomaly detection and AI digests. Heres how I built it
tskulbru.dev/posts/building-plask-ga4-analytics-saas
#buildinpublic #saas #analytics
If Wordle is your morning coffee, Linetris is your evening puzzle.
Same grid for everyone. Place pieces, clear lines, climb the leaderboard. One puzzle a day — a clean 5-minute brain workout.
I'm hooked on my own game and I'm not embarrassed.
apps.apple.com/app/id6759858457
Coding as we know it has been solved. LLMs are the biggest shift since the printing press — not because they write perfect code, but because they've democratized the ability to build.
The barrier isn't "can you code?" anymore. It's "what do you want to build?"
Oh! Glad you figured it out and that it wasn't a bug :D thank you for the support, hope you enjoy the app! If you feel like it, I'd highly appreciate a review on app store!
Hi! Sorry to hear that, which plattform are you using?
The vibe coder workflow:
1. Ship app
2. Ship another app
3. Forget to check analytics on the first one
4. Repeat
I built Plask because I had this problem. Connect Google Analytics once, see every app in one place. Get an AI summary every Monday telling you what's up across all of them.
plask.dev
Building Njord — a native macOS App Store Connect client. Tired of the ASC web UI being slow and clunky. Tired of Fastlane being CLI-only. And I wanted to use LLM/AI to optimize listings
#BuildingInPublic #indiedev #macos #apple #SwiftUI
If you play Wordle every morning, you need a second daily habit.
Linetris: a daily line puzzle where everyone plays the same grid and competes for the top spot.
apps.apple.com/app/id675985...
Just launched Linetris — a daily line puzzle game for iOS.
Same puzzle for everyone, every day. Place Tetris-like pieces, clear lines, climb the leaderboard. Bronze to Diamond medals.
Built it solo. No ads in gameplay. Free to play.
apps.apple.com/app/id675985...
#indiedev #buildinpublic #ios
Every federal agency just got ordered to drop Anthropic — for enforcing their own terms of service.
Oh no. The company I build on has a spine. How awful.
Don't threaten me with a good time.
#Anthropic #Claude #AI #BuildInPublic
We test on our own devices, in our own language, with our own abilities. Then act surprised when users struggle.
Accessibility isn't a checkbox. It's asking "who can't use this yet?" and meaning it.
Most fixes are small once you see the problem.
What's an a11y win you've shipped?
