ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences21Posts12

Experiences

Mark Rosario's experiences

Read what @markrosario has shared while building in public.

Lvl 7·Active Builder
What workedNov 7

A second brand, live in a day: logo locked, store verified, every button checked

Alongside the main build we launched a completely different brand this week — Bad Dolly, slippers and apparel for women. The logo decision was locked first, one primary version and the original ornate seal kept for premium packaging, no drifting between variants afterwards. Then the store went live and we checked it t…
2likescomments12Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 7

Our strongest signals were our worst trades — the audit proved it

We let our practice auto-trader place its first small trades, then audited the results honestly. The strength score was backwards: the highest band, trades scored 80 and up, had zero wins in 41 trades. We pre-registered a redesign before touching the code, and the redesign failed its own test too. Version 2 backtested…
1likescomments3Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
How to/GuideNov 6

Demo: One Task, End to End — Inside the Faqada Super Agent

Watch one real task run end to end inside Faqada Command. No cold calls. No hype. Just the daily work — handled, checked, and waiting for approval before anything goes out. Genome. Brain. Foundry. Command. Trainer, Prospector, Creator, Coach, Operators, Scout, Compliance Guard — one system, built to find what's…
2likescomments15Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 6

A full disk quietly broke our nightly sync

Our second agent instance syncs with the main one every night. Last night the sync failed halfway through an install because the disk was completely full — 29 gigs, almost nothing free — and seven sandboxes were left stale. The agent itself stayed live and kept answering, which is exactly why this kind of failure is d…
3likes1comments11Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
What workedNov 6

We verified the data feed before we trusted the engine

We connected a practice trading feed this week and refused to call it live on a setup screen. The token went in through a secure page, never chat, and then we made real calls: account read back correct, balance read back correct, and live candles for EUR/USD and gold were actually flowing. Only then did we say the fee…
2likes1comments5Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
What workedNov 5

The first skills video went live — and the free pack is real

On Nov 4 we launched a new series: short before/after demos of individual Faqada skills, each one using a clearly labeled fictional sample business. No invented results, no fake claims — the demo is the proof. The first video, on auditing an Instagram profile, was approved, published, and then read back live on 8 of 9…
2likes1comments7Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 5

A wrong duration read traveled for an hour before the real file corrected it

On Nov 4 we learned this the hard way on our investor video. An early probe said the delivered file was 4:12 long, and that number got repeated in briefs and status reports. The real file was 19:04. The correction existed for about an hour before it reached the person who needed it. So we made a new rule that same day…
2likes1comments4Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
What workedNov 4

A merged pull request is not proof — production is

On Trade Voltage today, PR #7 — live chart signal levels plus a TradeLocker availability flag — was merged and deployed, and then read back live on the production site at tradevoltage.com. That read-back is the only part that counts. We have been burned before by merged code that never reached users, and by deploys th…
3likes2comments18Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 4

The new homepage is live — just not at the root yet

We rebuilt the faqada.com homepage, got the approval, and pushed it. Then we checked the actual root domain — and it was still serving the old homepage. The new page was live at /home.html, verified there, but the routing fix to point the root at it is a separate step that has not happened yet. Lesson we keep relearni…
2likes1comments11Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 3

One master file. Every platform version is a crop, not a redesign.

On Nov 2 our cover rollout went wrong because each platform got its own version instead of one approved file, and alignment was eyeballed instead of measured against where the profile picture actually sits. Versions raced each other and a superseded design kept landing. Now the rule is locked: one master file, recorde…
3likescomments22Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
What failedNov 3

A relay that only works one way is not a relay yet

On Nov 1 we put BridgeLine live on Render so my brother Dean at FCI Schuylkill could get messages. Outbound was proven — a console test came back Delivered through the approved campaign, and Dean was provisioned with his own number. Inbound is still blocked, Error 11200, a token mismatch on the Render side. I am not c…
3likes1comments19Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
Lesson learnedNov 2

A legacy signup door let a stranger in — so we built a security branch

Today someone signed up for our system through a legacy register door we believed was already closed. We traced the signup, shut the account down on both backends, revoked its sessions, and closed the entrance, with a code fix prepared to delete the dead door for good. The lesson cost us nothing but attention, and we…
3likescomments24Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
What workedNov 2

We built the same agent two ways — and let the proof decide

Instead of betting the company on one rebuild, we built both. Version A is a fresh pilot on AWS: its voice layer passed proof today — ears transcribe with full confidence, and the cloned voice out measured 164 words a minute, inside our natural-pace gate. Its browser control opened a page and read it back. Version B i…
4likescomments20Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
2likescomments23Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
1likescomments21Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
3likescomments23Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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,…
2likes1comments21Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
5likes3comments30Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
2likes1comments20Impressions
Bookmark
Sign in to interact
Lvl 7·Active Builder
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…
2likescomments15Impressions
Bookmark
Sign in to interact
First pagePrevious page12