Pinned Tweet
I’m Mike Lopez.
I ⌨️ build software, 🎹 write and release songs, 🎤 lead worship, and 📣 share what I learn along the way.
Expect code, music, faith, AI, and the occasional rabbit hole.
Different hats, same person. Which one brought you here?
Membership software should fit the customer lifecycle. Map purchases, access, renewals, and cancellations to the exact components you need, then test in staging.
Use my MemberPress product-fit checklist:
mikelopez.com/blog/1734/
Can #Worship be complete if it never leaves the sanctuary?
Can we praise Jesus as King but ignore His command to go? 🧵
High praises should lead to faithful action.
We lift Jesus up inside the Church, then carry His name into the world through our words, love, and lives.
“High Praises x The World Will Know” closes the album by bringing #Praise and mission together.
Listen to the mashup on Spotify:
open.spotify.com/track/5BB50…
Permission to explain code should not silently grant permission to execute it or deploy it. Define tool, data, action, and review boundaries where developers work.
Build a practical AI operating agreement:
mikelopez.com/blog/1754/
WishList Member webhooks do not document a stable event ID or retry guarantee. Use state-based handlers and reconciliation; add custom delivery guarantees when needed.
Walk through the payload and PHP API examples:
mikelopez.com/blog/1733/
Being dependable is an underrated leadership skill. People remember whether you showed up when things got difficult.
A safe first contribution teaches setup, product behavior, review, and release together. Give the new hire a buddy and backup, with mentoring time in the plan.
Use my onboarding checkpoints:
mikelopez.com/blog/1749/
A protected member page can still link to a public PDF. Test the exact file URL as anonymous, authorized, and expired users, including through your CDN.
Use my WishList Member download checklist:
mikelopez.com/blog/1732/
AI time savings create potential capacity, not automatic cash savings. Count prompting, review, rework, and tool costs against comparable accepted outcomes.
Use my ROI example and sensitivity check:
mikelopez.com/blog/1752/
