Joined October 2022
- Tweets 164
- Following 6
- Followers 16
- Likes 358
25 Photos and videos
Pinned Tweet
Apr 10
I build SaaS tools and backend systems (MERN, NestJS, Postgres, MySQL)
Currently building @merngenie & @symplaxhq
I share:
• SaaS building journey
• Dev mistakes & lessons
• Real backend insights
• Dev humor 😅
Follow if you build too.
4
139
Jun 13
Techies 💜
Day 4/15 of the @collan_devs Build in Public Challenge
Building: Symplax, VPS management for devs who hate babysitting servers
Day 4: pre-launch fixes, breaking it intentionally with different test cases
#CollanChallenge
2
5
61
Jun 11
Biodun built his SaaS for 11 months.
347 paying users. $2,100 MRR.
One corrupted database later, all of it was gone.
1
4
54
Jun 11
The worst part?
His hosting provider offered automated backups.
It was $4 extra per month.
He had unchecked that box during setup to save money.
$4 a month cost him $2,100 MRR and 11 months of work.
1
1
26
Jun 11
Before your SaaS goes live:
👉🏿 Enable automated daily backups
👉🏿 Store backups separate from your main server
👉🏿 Test your restore before you need it
👉🏿 Supabase and Railway handle this by default
Your database is your product.
Back it up or you own nothing.
1
2
29
Apr 28
Emeka worked on a feature for 3 weeks straight.
No commits. Just local files.
His laptop died on a Sunday night.
All of it. Gone.
2
4
57
Apr 28
The saddest part?
A single git push would have saved everything.
Not a fancy CI/CD pipeline.
Not a cloud backup system.
Just git push origin main before closing the laptop.
1
38
Apr 28
What Emeka should have been doing daily:
👉🏿 Commit every meaningful change, not just "finished" 👉🏿 Push to remote at the end of every session
👉🏿 Use branches so work in progress is still saved
Your local machine is not a backup. Git is not optional. It is your safety net.
25
Apr 25
Just shipped MetaPulse for @wemakedevs x @openmetadata
Built solo in 9 days:
👉🏿 Detects pipeline failures generates AI incident reports automatically
👉🏿 Onboarding copilot that knows your entire data catalog
Powered by OpenMetadata
#OpenMetadata #WeMakeDevs #BuildInPublic
1
4
60
Apr 23
Kola built a food delivery API in 3 months.
Launched on a Tuesday. By Wednesday morning, 2 million requests had hit his server.
He had zero customers.
1
4
60
Apr 23
Every public API without rate limiting is an open invite.
Not if someone will abuse it.
When.
1
24
Apr 23
What Kola needed before going live:
👉🏿 express-rate-limit to cap requests per IP
👉🏿 Redis to track and enforce limits at scale
👉🏿 API keys on every public route
👉🏿 Alerts for unusual traffic spikes
Your API is a door. Put a lock on it.
23
Apr 20
Chidi spent 8 months building his SaaS.
ProductHunt launch day came.
He hit #3 of the day.
500 signups in 2 hours.
Then the emails stopped sending.
1
2
34
Apr 20
60% of those 500 users never came back.
Not because the product was bad.
Because their first experience was silence.
In SaaS, silence after signup kills trust before it even starts.
1
1
18
Apr 20
What Chidi needed before launch:
👉🏿 Resend or Postmark, not a free tier
👉🏿 BullMQ to queue emails in batches
👉🏿 Load test your email flow before go-live
If onboarding breaks on day one, users assume everything is broken.
Fix the pipes before you open the tap.
1
24