386: One Year of Podscan: Reflecting on Tech & Business Decisions

What It Covers

Arvid Kahl reviews one year of building PodScan, analyzing technical choices including PHP Laravel framework, MySQL database, MileySearch integration, and business services like Paddle payments that enabled reaching profitability with 10k monthly recurring revenue.

Key Questions Answered

• •PHP Laravel Framework: Choosing PHP Laravel over newer languages provides decades of community solutions, extensive AI training data for code generation, and plug-and-play ecosystem products like Forge, Spark, and Jetstream that accelerate development without long-term maintenance issues.
• •Database Migration Costs: MySQL schema changes on large tables require AWS blue-green deployments costing hundreds of dollars per index addition due to table locking issues. PostgreSQL would have provided better full-text search and vector embedding support for the five-plus terabyte database.
• •Payment Provider Economics: Using Paddle as merchant of record costs approximately 500 dollars monthly in fees but eliminates building renewal systems, failed payment recovery, multi-currency support, invoicing, and tax compliance, making the tradeoff worthwhile for a 10k MRR business.
• •Technology Longevity Strategy: Apply the Lindy Effect when selecting tech stack—technologies existing twenty years will likely persist twenty more years, while two-month-old frameworks may disappear quickly. Mature ecosystems provide expert availability, comprehensive documentation, and battle-tested libraries for real-world problems.