I tried building a SaaS with 4 different AI models.
200+ tasks.
Zero supervision.
3 straight days of agentic coding.
No chance this could work, right?!
But why even do this kind of stunt?
I have a pretty good reason.
After shipping 15+ apps over the past years I noticed 1 thing:
👉 90% of people never ship anything because they end up spending months doing password resets, complex billing, email templates and so on.
Getting a full MVP that works end to end is a HUGE value and completely underestimated by the "builder" community.
That is because most are devs and they think they can build those quickly. But the longer you drag it the lesser the chance you'll ever ship.
IMO this is a huge unlock, but YMMV.
Besides that, this shows the model's capability to deal with the complexity of a real system, and not just one-shotting a 3D demo or a LP.
Anyhow, this video took me almost 1 month, hope you find it interesting!
Clobbr retweeted
Kimi K3 is the best performing model on nextjs.org/evals, ahead of Fable, reaching a comparable success rate in less time.
This is the first time that an open model is ahead of all proprietary ones for this comprehensive web engineering benchmark.
Notes:
▪️ Benchmarks don’t always tell the full story, although this is important signal, adding to mounting evidence that this could be a breakthrough moment for open models
▪️ No model as of yet has reached 100% completion on this set of evals. The top performer peaks at 92% and 96% “with help”
Clobbr retweeted
I was using Claude Code wrong 🤦♂️
Here's everything I learned and how to get most out of Claude Code
👇 Thread time
Clobbr retweeted
The team at Cursor is about to change how you code again
Vibe Keyboard just dropped 🔥
- mechanical hot swap switches
- USB-C 4K 120W
- accept lock toggle
- all day battery
👇 Pre-order below
Now out 🎉
The biggest Clobbr release ever!
- adds the ability to cancel runs
- shows charts real-time as requests come in
- shows request progress
- allows saving & inspecting response data (via settings)
- allow showing value scale (via Y-axis settings)
and…
yeah I am probably a terrible business person 😔
why?
I rewrote the internals of clobbr.app because I got a combo of bad Setapp review + support email concerning the same issue.
I couldn't leave it be.
So I slept 6 hours in the past 3 days to fix this.
I want to stand by what I built and support my apps for as long as I can.
So why is this BAD for business?
I'll tell you in a second.
But first, it's time for Realtalk™
Many people in the community advocate for shipping things fast and fixing things as you go. But I think quite a lot stop at shipping fast and never do the other part.
There is an insane amount of buggy indie software that never gets patches.
I think long-term this will hurt you, either slowly or with a wrath when e.g. someone discovers a huge flaw in your apps.
👉 A polished can be a huge moat in a sea of buggy products
IMO you ship fast and either:
- kill the app; it failed. Refund everybody
- commit to maintaining the app and your image as an indie dev
(optionally, pivot and choose again)
Medium to long term this will create a user base and you will be able to get sales on new products by leveraging your brand.
🤔 But I just said this is a terrible business decision?
Well, the truth is I probably chose the wrong thing long ago. I should have pivoted or killed the app.
It's in a niche of a niche and I have built it purely on a hunch.
I stopped marketing efforts for Clobbr a while ago and sales have been going down.
So choosing to work on this vs a new product that can bring a lot more revenue (or existing one that does it) is probably a STUPID IDEA.
I don't care though, I want those 2 people that wrote to me to like the app.
I hope it's not just my ego, but a principle that I will manage to stand by for decades.
> Will I make less money?
Sure.
> Will I sleep better at night?
Absolutely.
And I do need sleep right about now 😂
Debugging just got a lot easier 👀
OKAY
I am sold on AI agents.
This is INSANE. So I open up this exception, then:
- AI tries to find a quick cause
- ❌ not the cause
- AI convinces itself that's not the root cause
- ✅ AI finds the actual root causes
- 🤯 AI suggests fixes
- I guide the fix
- implements the entire thing by looking at my code
- 🔂 AI makes a PR
- the PR actually fixes the issue???
Mac dev stats in 2024 💡
💻 ~60% of are either actively working on / have implemented AI models in their apps
📉 Only 20% distribute their apps exclusively via the Mac App Store.
🥽 20% are planning to develop for visionOS in 2024 / are already in the dev process
and 👇
tons of more insights in the full report made by the friends at Setapp here: stpp.co/49vJz6N
Clobbr retweeted
I am not bragging
but don't even try to compete with me for Debug December, I am absolutely crushing it 😂
those prizes are MINE
Seeing what happened before an exception is OP 🫡
OK this is cool.
how many times have you wanted to just see what the user is doing when something went wrong? I know I have.
well, this is basically it.
a way to see *exactly* what the user was doing before something crashed.
Sentry can do this for Flutter, React Native, iOS, and Android 🤯
You can also see network and tracing, which means you can debug something end to end. WHAT
Clobbr retweeted
fonts, themes and so many demos you'll scrollwheel is gonna break :D
check it out 👇
shipixen.com/component-explo…













