ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences8Posts4

Experiences

Mark Rosario's experiences

Read what @markrosario has shared while building in public.

Lvl 6·Maker
Lesson learnedNov 1

Five failed reviews before the pass that let us ship

Our backend migration failed independent review five times in one night. Each round found something real: a workspace isolation hole, a fix that proved nothing, children stranded when a record was first stamped, a concurrency race, then a snapshot race on top of it. Each fix had to come with a test that failed on the…
1likescomments2Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
What workedNov 1

Shipping to 12 surfaces at once — with a read-back on every single one

When we publish now, it goes everywhere at once — two Instagram accounts, Threads, Facebook page and personal profile, two TikToks, LinkedIn personal and page, Google Business, X, and YouTube — and then every surface is read back live with its link before we call it published. On Oct 27 a new video format launched 12…
1likescommentsImpressions
Bookmark
Sign in to interact
Lvl 6·Maker
How to/GuideOct 31

How we verify anything before we call it done

Our standing rule, set after a website we thought was deployed wasn't: inspect the actual thing before accepting it. A success message, a finished build, a merged pull request, a worker's report — all of those are claims. The proof is the live surface, read back and compared against what was asked for. It costs a few…
2likescomments16Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
What workedOct 31

One core, four businesses: replicating our agent system for partners

Instead of building a new tool for every client, we built one core — it learns a business from its founder: their offers, people, voice, and rules — then tailored it. In one week that core became four working systems: our own company, a hair-making school in Nigeria that reached a 100% founder profile and activation,…
1likescomments13Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
Lesson learnedOct 30

A browser can carry a lot of things. An API key is not one of them.

We burned hours installing production API keys through a browser agent. Three keys went in and none of them ever authenticated — copying a one-time-displayed secret through a screen distorts characters, and the install reports success anyway. The provider's own "last used" stamp told the truth: blank. The fix was bori…
3likes2comments16Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
Lesson learnedOct 30

A second engine reviewed our code — and caught a live security hole in it

We build with more than one AI engine, and no engine checks its own work. On Oct 28, our reviewer reproduced a real SSRF hole in a tool our agent uses — the safety check resolved a domain one way, the actual connection resolved it another way, and the gap was exploitable. The build failed review, we accepted the verdi…
2likescomments13Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
What failedOct 29

A “failed” post that had actually published — and the duplicate it caused

On Oct 26 we shipped a film to 12 surfaces. One platform returned a generic failure error, so the post was retried — and landed twice on the same account. The failure message was wrong; the first post had gone live. Now the rule in our shop is simple: a failure banner is a claim, not a fact. Before any retry, we read…
2likescomments9Impressions
Bookmark
Sign in to interact
Lvl 6·Maker
Lesson learnedOct 29

Day 1: The Night the Company Got Its Rooms

Day 1 of the public record. Today Faqada stopped being a solo build — my first team member's AI came online and joined the company. I'm keeping a daily public record of building Faqada from here: what ships, what breaks, and what we learn.
2likescomments8Impressions
Bookmark
Sign in to interact