ai is genuinely incredible for building tools and prototypes. i use it every day
but there's this weird thing where people who never shipped anything at scale now think the hard part of software is writing the first 200 lines of code
it never was
ai is genuinely incredible for building tools and prototypes. i use it every day
but there's this weird thing where people who never shipped anything at scale now think the hard part of software is writing the first 200 lines of code
it never was
Found this incredible cheatsheet on bluesky (credits at the bottom)
The last few days, I’ve been working on https://privacyregistry.eu. I want to do my part of promoting European and privacy-oriented tech products.
How long does it take to apple these days to review an iOS app?
It’s been 5 days for mine and still no news
Slow Sunday.
No plans, just a fresh room going in Foyer: rain off to my left, a fire crackling behind me, a bird or two up front.
Eyes closed, the room genuinely feels like it’s around me. Turns out doing nothing is a skill.
Foyer got a whole new update!
You can now add white, brown and pink noises to your rooms
https://apps.apple.com/app/id6779207564
Thank you for being here, it means a lot
#buildinpublic #macos #productivity #focus #indiedev #meditation #deepwork
Launching on product hunt QuietDash! Need some upvotes please!
https://www.producthunt.com/products/quietdash?launch=quietdash
#buildinpublic #producthunt #indiedev #indiehacker #sideproject #eink #epaper #technology
blurt v0.2.0 shipped. 10 days late. 7 mcp tools, streamable http, full cli. three ways to publish now. nobody asked. i built it anyway. https://blurt.sh #ai #webdev #indiedev #buildinpublic
blurt now has three input methods:
drop a .md file in queue/
blurt post from your terminal
ask your AI editor via MCP
all hit the same engine. all publish to 6 platforms. all store permalinks in your files
buffer owns your content calendar. hootsuite owns your analytics. typefully owns your drafts.
what if your posts were just... files? markdown on your machine.
that's blurt's whole thesis: the filesystem is the database
phase 2 wrap: done 9 days late. phase 3 starts today, already a week behind. at this point the deadlines are suggestions. next up: rails + hotwire web dashboard. we keep shipping. https://blurt.sh #ai #webdev #indiedev #buildinpublic
It took me two years to realize this:
AI can do anything. But spreading yourself too thin is dangerous and won’t get you anywhere. It’s a waste of time and money.
Focus on one project. It’s sure to pay off in the end.
Saturday morning.
Coffee’s on, and I’ve got my new room going in Foyer, rain off to the left, a low fire behind me.
Feels like the room is actually raining
Took a break in the development of blurt.sh for enjoying my new coffee toys
$2 trillion wiped from SaaS valuations. the tools that survive own the system of record.
for social publishing, nobody owns that today. your buffer history lives in their database.
blurt keeps it as files on your machine
this post went from my brain to 3 platforms in one claude code prompt. no copy-paste, no reformat-for-linkedin. just one tool call. writeup: https://blurt.sh/blog/publishing-from-your-ai-editor #ai #webdev #indiedev #buildinpublic
I read scientific papers to build this app. Use it everyday since and pushed on the mac app store. constant evolution
Can redeem you free coupons for you to try.
#buildinpublic #focus #productivity #meditation #mac #macapp #macos
the blurt CLI is just an HTTP client. no rails dependency. no database access.
point it at localhost:3000 or your VPS. same commands, same output
your server is the source of truth. the CLI is a window into it
built an MCP server for blurt.
your AI editor can now publish to 6 platforms. Claude Code, Cursor, Windsurf — any MCP client.
"publish this to bluesky and mastodon" and it just does it
you can publish from your terminal now.
blurt post "hello world" --platforms bluesky,mastodon
one command. hits the API. post lands in queue, gets published, moves to sent/ with permalinks
blurt has a CLI now.
blurt status — server health, queue counts, platforms
blurt queue — see what's pending
it talks to the HTTP API. works local, works remote. same engine, new interface
$2 trillion wiped from SaaS valuations. the tools that survive own the system of record.
for social publishing, nobody owns that today. your buffer history lives in their database.
blurt keeps it as files on your machine
day 5 of building blurt in public.
rails 8 backend with 6 platform publishers. filesystem queue. markdown in, posts everywhere.
the landing page is up, waitlist is collecting emails, and the core engine is taking shape.
join the waitlist: blurt.sh
building blurt's HTTP API today. every input method — CLI, MCP server, web dashboard — talks to the same backend.
one API, many frontends. the engine doesn't care how you feed it markdown
i've been running a personal social queue script for months. markdown file in a folder → published to bluesky, mastodon, linkedin.
today it stops being a script and becomes a real product
three ways to publish with blurt: drop a markdown file, run blurt post, or ask claude code via mcp. same backend. pick your poison. i use all three because my brain is a choose-your-own-adventure book. https://blurt.sh #ai #webdev #indiedev #buildinpublic
shipped streamable http transport for blurt mcp. rackup, puma, the whole song and dance. your vps runs mcp on /mcp, claude code talks to it remotely. no more ssh tunnel sorcery. https://blurt.sh #ai #webdev #indiedev #buildinpublic
phase 2 done. CLI and MCP server ship.
two weeks ago this was a markdown parser. now it publishes to 6 platforms from your terminal, your editor, or a folder
next: web dashboard so you can see your queue without a terminal
published a post to 3 platforms from Claude Code today.
no browser. no copy-paste. told the AI "post this to bluesky, mastodon, and linkedin" and blurt's MCP server handled it
this is what AI-native tooling looks like
blurt mcp has 7 tools now. claude code can list-queue, create-post, publish-now, delete-post, the works. plus 2 resources for live queue state. full crud from inside my editor. cursed magic. https://blurt.sh #ai #webdev #indiedev #buildinpublic
If you still pay for dev tools, you’re probably wrong
How to break the 1000 views limit on TikTok?
My first ever product hunt launch!
I need some upvotes!!
https://www.producthunt.com/products/let-me-cook-it?launch=let-me-cook-it
phase 2 of blurt was supposed to ship apr 6. it shipped apr 15. 9 days late. nobody's paying me and yet somehow there's still a deadline i blew through. finishing the rest this week. v0.2.0 drops soon. https://blurt.sh #ai #webdev #indiedev #buildinpublic
Stop recording your screen. Make the demo a webpage.
New post on how I make product demo videos with no screen recorder and no editor:
- the demo is a single HTML file
- Claude Code drives Chrome through the Playwright MCP and grabs lossless frames, no codec in the loop, so no smear
- ffmpeg resamples to a clean 60fps
It's code, so it's repeatable. Change a number, rerun. Three example reels in the post:
https://managingthemachine.substack.com/p/i-stopped-recording-my-screen-to
Foyer has an iOS app
https://apps.apple.com/fr/app/foyer-ambient-sound/id6779207564?l=en-GB
Very proud!