First bug of the day: TS2717.
I typed request.user as my AuthUser, but @fastify/jwt had already claimed that property.
Fix: augment the library’s own FastifyJWT interface instead of Fastify’s. Typed everywhere, no collision.
(Originally on LinkedIn)
Wireframes done, now the backend.
Goal: never double-send, never text someone who opted out, never block the API during a big send.
Stack: Fastify, Prisma, Postgres, BullMQ workers on a separate service. Every query scoped to the church.
(Originally posted on LinkedIn)
New client project: a church that needs to SMS 1,000+ members.
I’m building a broadcast + contact manager with credit tracking, DND/opt-out handling and campaign history.
First wireframes below
(Originally posted on LinkedIn, cross-posting my progress here)
Hey @x algorithm 👋
I’m trying to #connect with people building and learning in:
• Vibe coding
• Web3
• Software
• SaaS
If you’re building something, learning something, or just obsessed with tech...
Let’s connect 🤝