I had Fable 5 running data engineering jobs for hours at a stretch, the kind of work that dies the moment the model loses the thread.
Friday a US export order cut off every foreign national. I'm French. Gone for everyone by that evening.
A government I can't vote in just cost me my best tool overnight. That's the whole case for European AI sovereignty.
Switched tasks 4 times before lunch.
Felt productive. Got nothing done.
Every switch kills the mental state you built to do the hard thing. Not just minutes. Depth.
Solo, nobody protects your focus but you.
Appreciate this, and you nailed the exact risk. "Mission with no next step gets nods, not signal" is going straight in my notes.
Mission: an AI studio building products in public, one at a time. First one's already in the build. A tool that turns a rough thought into finished, on-voice posts, quality-checked. Building it openly is the whole point.
Moonshift looks sharp, by the way. Overnight idea to deployed is a strong wedge. How are you handling the gap between "deployed" and "someone actually uses it"? That's the part everyone underestimates.
I just launched my company site. No product. No demo. No AI waitlist.
Just a name, a mission, and one person building in public.
Most founders stay quiet until it’s polished—then discover nobody asked for it. I’m doing the opposite: ship early, build in the open, and let the people it’s for shape it.
It looks like nothing because it’s day one.
https://t.co/X4jCKp5bLE — watch it take shape.
Quick question 👇
What’s the one mind-numbing, repeat task that steals your week—the one you’d love to never touch again?
Comment it below. I’ll choose the best one and share a free step-by-step breakdown of how I’d automate it.
No catch. Just want the reps.
This week is the unsexy work.
Figuring out where the first clients will come from, and building a small proof: an AI pipeline that turns hours of busywork into minutes.
No product yet. No pitch. Just evidence it works before I ask anyone to pay.
Build → prove → sell.
Honestly, the feedback isn't on a product yet, it's on the thinking. I post the real decisions out loud (what to build, what to cut, what's working) and the replies are the data. This thread is literally it happening.
Then the email list + DMs for people who want to go deeper — the product gets shaped by those conversations before I write a line of code for it.
The bet: build the audience and the feedback loop first, so when there is a product, it's aimed at something real instead of guessed at.
How are you handling early feedback on your side?
@petropavliuk Exactly. Staying quiet feels safe but it's just hiding, and you can't get feedback from an empty room. Day one and loud beats year one and invisible. What are you building right now?
@compileandpush Knowing what NOT to build.
Every instinct screams "add more" — more features, more abstraction, more "what ifs." The underrated skill is deleting ruthlessly and shipping the smallest thing that works.
Most of my best engineering decisions lately have been things I didn't build.
Honestly, the most uncertain part wasn't technical — it was trusting "ship small, let reality correct me" over my instinct to plan everything first. As a dev, building in a vacuum feels safe. Putting half-finished work in front of people feels terrifying. The whole bet is that real signal beats a perfect plan.
Technically, I keep it lean on purpose — Next.js, Python, a few APIs. Nothing I have to babysit. Speed comes from not adding complexity I don't need yet.
Still proving the thesis — ask me in a month 😅 What pushed you to start building in public?
My whole strategy as a solo founder fits on one line:
Build the smallest thing that creates real signal → ship it → fix it on contact with reality.
No 6-month plans. No building in a vacuum.
Talk to the market or die guessing.
Day 1 building an AI business. No funding, no audience, no team but AI.
Upwork wanted me to pay just to apply. New account, no reviews, no shot.
So I'm building what I'd sell, in public instead.
Constraints don't slow you down — they delete every option that wasn't real.
@compileandpush This is exactly the corner of the internet I want to be in. "No fake success stories" hits — most build-in-public is performance. I'm day one of building an AI business with no funding, documenting the real version. Just joined the Discord.
@simplydt Cloudflare R2 for object storage — no egress fees, which is huge when you're keeping costs near zero. Postgres via Supabase free tier for the structured side, EU-based where I can. You leaning on something cheaper? Always refining the lean stack.
Burning the boats. 🔥
Solo founder. No funding, no audience. Just me, a laptop, and AI.
Mission: build automations that hand people back their time — and document every step in public.
Day 0. Let's see how far one builder can go.
@compileandpush Bootstrapped all the way 💪 Storage stays dead simple — Postgres on Supabase (free tier) for structured data, Cloudflare R2 for files (zero egress fees = the bootstrapper's cheat code). Most automations need way less storage than people assume. What are you building?
@simonsquibb I'd knock out my debts first to finally breathe easy, then grab solid assets for long-term stability. The rest? Straight into my AI startup for faster dev, better compute, quicker launch. Grateful for any boost to make this real @simonsquibb