I spent two weeks applying prompt engineering to a real SaaS product.
Moved rewrite quality from 7.37 → 8.37/10 across 38 bullets.
#buildinpublic#promptengineering#AI#SaaS
So I asked @ChatGPT to research the Naira card that works more times than not for these sort of subscriptions.
When it was done with its research it, it discovered @ZenithBank card had more reliable ratings so I want to my branch and grabbed a Mastercard(GPT was specific on Mastercard) so I got it...
...it also advised I asked them to enable online subscriptions which I asked and I had to fill up a form.
And that was it other than me sorta forgetting my PIN(did I?) had to go reset it tomorrow for POS and ATM usage..,
...it was a breeze to setup payments on Apple with the card and now I've paid for iCloud+. Fun time to be alive
Hey, this is a sample draft, try editing it.
Here's how Typefully helps you build an engaged audience:
📝 Write without distractions
⏰ Schedule for peak engagement
📊 Track what resonates
🚀 Enable auto-engagements
🔄 Cross-post everywhere
Also try these power features:
✦ Press ⌘J (Mac) or Ctrl+J (Windows) to rewrite with AI
✦ Drag & drop media directly into the editor
✦ Use the top right buttons to share & organize drafts
✦ Check out the Calendar & Analytics pages
What I'd do differently:
→ usage_events table on day 1, not month 4
→ Sentry before first user, not after first bug
→ Drizzle ORM from the start
→ Zod validation on every AI response immediately
Layer 6: Sentry + pino + usage_events
Found my first bug from a user email.
Now I know before they do.
→ Sentry with route tags + breadcrumbs
→ pino structured JSON logs
→ /admin/failures cross-user view
Layer 4: SHA256 content hash caching
Cold → embed from scratch
Warm → return cached (~0ms)
Stale → re-embed only what changed
99% of requests hit warm cache.
Layer 2: bullet rewriting
First prompt: "rewrite this to be ATS-friendly"
Model added "team player" to everything.
ATS systems flag that as filler.
Fix: ban list of forbidden phrases.
Constraints > creativity.
I’m looking for the right remote role for the next five years.
Not because I’ve stopped building independently.
Because I want to experience what becomes possible when the range I’ve developed is combined with an ambitious team, global distribution, serious resources, and problems operating at scale.
Today, I:
• Lead Sails.js, actively maintaining the framework, shaping its direction, and growing the ecosystem around it
• Build The Boring JavaScript Stack
• Build Slipway, a deployment platform for Sails applications
• Run Sailscasts, where I teach developers to build full-stack JavaScript applications
• Publish The African Engineer, covering how technology is built across Africa
• Build Hagfish, an invoicing product for creators and independent professionals
• Consult with companies on engineering, architecture, products, and developer experience
• Write, teach, speak, lead, and build in public
I have spent years operating across software engineering, open source, infrastructure, education, media, product, community, and business.
Now I want to bring that experience into the right global technology company.
I’m looking for a role where I can build software, lead technical initiatives, improve developer experience, teach developers, write, speak at conferences, shape products, and help grow an ecosystem around important technology.
I do my best work in an environment that is:
• Remote and async-first
• Low-meeting and high-trust
• Flexible rather than rigidly 9-to-5
• Built around deep work and strong written communication
• Focused on outcomes, quality, and impact
• Compatible with responsible open-source and independent work
I don’t want to perform productivity.
Give me meaningful problems, clear context, ownership, talented teammates, and the freedom to deliver excellent work.
Above all, I want to work on something I’ll be proud to attach my name to.
I’m especially interested in Developer Experience, Open Source, AI Developer Platforms, Staff Engineering, Developer Relations Engineering, Developer Education, and Technical Ecosystem roles.
If your company needs someone who can build the technology, understand the developer, explain the product, teach the market, and grow the ecosystem around it, let’s talk.
Reposts appreciated.
What I'd do differently:
→ usage_events on day 1, not month 4
Can't improve what you can't measure
→ Sentry before first user, not first bug
→ Drizzle from the start — raw SQL = tech debt
→ Zod on every AI response, immediately