ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences47Posts37

Experiences

Mark Rosario's experiences

Read what @markrosario has shared while building in public.

Lvl 9·Dedicated
What worked19 hrs ago

A care watch that finished what a failing watch could not

After my father passed, hundreds of people left comments across the posts about him. A watch that had been failing recovered, checked 237 comments, added care reactions, and sent funeral details in my own words — then re-checked 499 comments across 14 posts to make sure nobody was missed. Some work is systems work. Th
1likescomments27Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learned19 hrs ago

Inventory first, upload only what is missing

When we set out to move everything to our own infrastructure, the first instinct was to re-upload the whole thing. That would have wasted days moving files that were already there. The smarter call was to inventory what had actually landed, verify it class by class, and push only the gaps. The move is still not done,
1likescomments27Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 19

Recording a quiet day at its real size

Some days nothing ships. On Nov 17 the build stood still — no deploy, no new completion — while family matters took the day. Our documentary entry for that day says exactly that, with no progress invented to fill the space. A record that only shows wins is marketing. Writing the quiet days honestly is what makes the g
2likes1comments84Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 19

A restarted process is not a fixed system

Our Genome Scan sender had failed for days. The daemon was restarted and the process checked out — new process, fresh heartbeat, running clean. Every queue read after that still failed on authentication. Restarted is not fixed. We verify by the outcome the system exists to produce — a readout actually sent — not by wh
2likescomments56Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 18

A sync that fails silently is worse than one that fails loudly

Our pilot sync had a transport with zero retries and a nightly step that staged files in a place too small to hold them. It could fail and look fine. We fixed it in layers and proved it the hard way: unit tests, a live probe, two delta runs read back clean, and hashes matched on every file checked. If a system can fai
1likescomments57Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 18

We built the lead hub before we sent a single message

Instead of blasting messages from a spreadsheet, we built the hub first. On Nov 16 our Lead Hub CRM went live with the first sweep leads loaded, each one researched before any draft was written. Three outreach sends went out that morning and each one was read back live to prove it landed. Research first, draft second,
1likescomments18Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 17

Our knowledge registry passed 400 assets — and every one is read back

Our internal registry of what we have learned and built passed 400 assets this week — 416 rows, each one captured, classified, and verified by an independent read-back of the actual file, with zero formula errors. The point is not the number. It is that nothing enters the registry on a builder's say-so: a capture only
2likescomments34Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 17

A scary indexing email was mostly noise — the real defect was hiding underneath

Search Console sent us a "pages not indexed" warning for our old domain, and it looked bad. Reading the actual reports changed the picture: most flags were legacy URLs and correct redirect behavior from our domain move. The real defect was on the new domain — every route's static page carried the homepage title and po
2likes1comments21Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 16

We built our own film studio instead of installing someone else's

We looked at an open film tool and scored it 73 out of 100. Good ideas in there, but installing the whole thing would have meant taking on someone else's system. So we adapted the ideas instead and built a clean-room thin slice of our own Film Studio. The proof film was probed on the delivered file itself: 12 seconds,
2likes1comments19Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 16

When the launch post stalls, the founder posts it himself

On Nov 13 we rebuilt the Faqada Team group — renamed it, cleared out 13 stale items, and removed the welcome automation. Then the launch post sat on Facebook's Posting spinner for over 35 minutes, fully built and ready to go. So I took the file and posted it myself. The read-back checked out: the full text, all the li
2likes1comments17Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 15

The cut we rejected made the cut we approved

Our first live cut of our intro film had gaps and scenes that did not hold up, so we rejected it even though it was already live. The rebuild used only fresh renders, no reused pieces, and the voices were cleaned up across the whole film. Then we watched the new cut end to end before anyone else saw it. That version w
3likescomments27Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 15

Moving the front door without breaking the address people trust

We moved our primary home to a new domain this week and kept the old one forwarding permanently to it. The move itself was the easy part. The real work was everything that points at the door: canonical tags, the sitemap, search console, analytics, and every social link had to be read back on the new address before we
2likescomments17Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 14

A token that dies with the session is not a token for a standing service

Our Genome Scan sender went down because its login token lived in session storage that vanished. The readouts were safe in the queue, but nothing could send. The rule we set from that failure is simple: every token for a service we always use gets the longest life the provider offers, and its storage has to survive a
3likes2comments27Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 14

Our domain moved home — and every redirect was checked

We made faqada.tech our primary home this week and pointed faqada.com at it permanently. The move itself was the easy part. The work was the follow-through: fixing the Genome API for the new origin, then reading back Datadog, meta, the sitemap, and Search Console until each one matched the new home. A redirect you hav
3likes3comments23Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What failedNov 13

A login token vanished from the keyring — and the queue held

Our Genome Scan sender stopped delivering readouts this week, and nothing announced it. A direct probe found the real cause: the Supabase CLI login token was simply gone from the machine's keyring, so every queue read failed auth while the daemon kept trying. The good news is the design held — scans still land and sto
3likes2comments21Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 13

Lead with what you are now, not everything you have been

When we built my speaker kit this week, the first drafts of my bio listed everything I had ever done. It read like a history file, not a reason to book me. So we cut it down to what is true and current: I lead with developer — an accomplished developer backed by 23 verified certifications, with over 14 years in digita
2likes1comments5Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 12

One feed, three destinations: we built our own multistream relay

We needed one live show to reach every platform at once, in landscape and vertical at the same time. Instead of renting another tool, we built the relay ourselves from free open-source parts. One feed in, three destinations out — two landscape copies and one vertical re-encode — and the master recording kept rolling e
2likescomments3Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 12

We shipped a video without watching it end to end — never again

Our Season 1 film came back with frozen frames, lips that were not moving, and an ending that was off. The honest part: nobody on our side had watched the finished cut from beginning to end before it was presented as checked. A build report is not a watch-through. Now the rule is simple and it has no exceptions — no v
2likescomments5Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
What workedNov 11

We gave our agent a face and a voice — and locked both

On Nov 10 we turned our agent into the face of the system. The first look was blue armor with a white Y face plate, then Mark pushed it to a glowing cyan Y, a solid glowing cyan F on the chest, and light in the joints and seams — then rejected the animated look and made us render it photoreal. The same day he audition
2likes1comments8Impressions
Bookmark
Sign in to interact
Lvl 9·Dedicated
Lesson learnedNov 11

The rule was in the spec and the backtest — everywhere except the code

Our NG-7 paper system had a 4-hour signal expiry rule. It was in the spec and in the backtest, but it was never put into the live code. Day one filled in about 3 minutes and went 9 for 9. The next batch sat unfilled for 67 hours over a weekend, filled at the Sunday reopen off a stale snapshot, and went 1 for 9. Every
2likescomments3Impressions
Bookmark
Sign in to interact
First pagePrevious page123