Pablo audited.
Solid account. Best of it, you punch well above your follower count. Worst of it, not enough people react per view.
Ranked 8 of 45 on the public leaderboard, top 18%
Where @pfernan95dev sits on the board
#8 of 45
Yusuke@yusukelp · 1.6K followers60.46PabloThis account@pfernan95dev · 657 followers59.79
Marcus Brathwaite@marcus_b1973 · 1K followers58.580.67 points behind #7. See the full board
Where this score comes from
Out of 100, weighted. Follower count is not a factor, but actually reaching people is. A small account with real conversation can beat a big one that broadcasts, and an account that reaches thousands still gets credit for it.
What this engagement is made of
All 1K reactions across the posts Chad read. Bookmarks are not counted, here or anywhere else in this audit.
Golden hours
When @pfernan95dev's posts actually get seen, scored on this account's own data. Times in PT. Slots marked playbook are defaults, used where there are not enough posts at that hour to judge it.
The reply game
Replies are the most under-used lever on X. A good one is worth roughly 27x a like, so this is measured, not assumed. Chad reads the most recent page of replies, so the count is a floor, not a lifetime total.
How this compares
Against the median of 44 other accounts Chad has audited. Same measurements, same method.
Voice, according to Chad
You're a straight-shooting solo builder who talks shop without guru fluff. Technical breakdowns, open connection asks, and real shipping receipts are your rhythm. Reads like a dev in the trenches, not a stage talk.
What this account is about
The 3 strongest posts, and why they worked
Monday morning 👋 Free tiers that actually got my side projects off the ground 🧵 🔐 Clerk: auth. Drop-in components, generous free tier (50k MAU). Shipped login in an afternoon instead of a weekend. 🗄️ Neon: serverless Postgres. 512MB free, unlimited projects, and compute
ChadThe free-tiers thread hit 187k impressions with 14 bookmarks and 11 reposts because it was pure save-worthy utility: Clerk and Neon with concrete free limits, not vague advice.
0 to 282 followers in 4 days. I'm sharing my analytics. Replies did the job, not posts. Almost all impressions came from replies. Keep connecting together. Still looking for people building actual products, especially small accounts. What are you working on? https://t.co/2l7g9
Chad0 to 282 followers pulled 52 replies on only 1468 impressions. Real analytics plus a direct 'what are you working on' turned a small post into a full conversation room.
Looking to connect with people who actually ship. - iOS / Android apps - indie games - backend & distributed systems - SaaS - anything you build after your day job Drop what you're working on and I'll take a look 👇
ChadThe 'people who actually ship' invite got 45 replies the same way: clear niche tags, zero pitch, and an open door. You asked the room instead of broadcasting at it.
Chad's moves for @pfernan95dev
- Cut the firehose. You're at ~41 posts a week vs the cohort median of 21.8, and engagement sits at 0.2% against their 2.2%. Run 1 crafted post plus 1-2 short reply-bait lines a day and let the good ones breathe.
- Drop one 20-30s screen recording this week of Camp Raiders or Respira, a quick feature demo or before/after. Your text utility already works; short video is the leverage play you're not using.
- You already reply a ton (~849/week floor), so stop spraying wider. Tighten to 5-8 thoughtful outbound replies a day on slightly bigger iOS/indie accounts, then pour the rest into tending your own threads while they're hot.
ChadAt 657 followers with a one-week burst of ~41 posts, you're flooding your own reach. 1 crafted plus 1-2 conversation one-liners a day keeps quality high without burying the posts that actually travel.
One post, rewritten by Chad
An idempotency bug that hides well: the duplicate has a different primary key every time. You consume an event, create an entity, let the database generate the UUID. The ack never lands, the broker retries, and a second row appears with a fresh id. Nothing errors. Both rows are
Idempotency bugs that never throw are the worst kind. You consume an event, create an entity, let the DB mint a UUID. Ack fails. Broker retries. Second row appears with a fresh id. Nothing errors. Both rows look valid. Here's the check I added so it can't hide again:
Leads with the pain in one cold line, then keeps your technical beat while giving the reader a reason to stick for the fix.
Questions about @pfernan95dev's X account
@pfernan95dev's strongest posting hour is 12:00 AM PT, measured from 41 of their own recent posts rather than a general rule. The next strongest are 2:00 AM and 4:00 PM.
@pfernan95dev posts about 41 times a week across the posts Chad read. Chad's recommended cadence for this account is 3 a day.
@pfernan95dev runs a 0.2% engagement rate, meaning that share of the people who see a post react to it. Their average post reaches 11.8K people. Follower count is not part of this measurement.
The single biggest opportunity Chad found on @pfernan95dev is the wrong posting cadence. More is not growth. Two strong posts beat six mediocre ones, and posting too much buries the best work.
Accounts scoring near this one
Closest scores on the board. Same measurements, same method.
Yusuke@yusukelp · 1.6K followers60.46Marcus Brathwaite@marcus_b1973 · 1K followers58.58
Pedro Guitian@pedroguiti · 1.2K followers62.09An audit tells you what happened. Slap Post changes what happens next.
Everything above is one snapshot. Inside Slap Post, Chad rebuilds this every week as your numbers move, rewrites any post before it goes out, and schedules it into your golden hours. Our servers fire them on time even when your phone is off.
Start my 7-day free trial $29/mo after · cancel anytime · or just get a free audit first