PostgreSQL Monitoring and Schema Linting for Laravel with Vacuum
Vacuum checks PostgreSQL in Laravel apps for bloat, wraparound, and unused indexes, and flags unindexed foreign keys in migrations during CI.
Writing on software design, company building, and the aerospace industry.
All of my long-form thoughts on programming, leadership, product design, and more, collected in chronological order.
Building EasyReply: How We Used Laravel to Unify Customer Support
EasyReply pulls email, Slack, Instagram, and WhatsApp into one AI shared inbox, built on Laravel with Reverb, Inertia, React, and queues.
PayZephyr: One Payment API for Stripe, Paystack, and PayPal
PayZephyr gives Laravel one payment API across Stripe, PayPal, Paystack, Flutterwave, and four more, with failover and double-charge protection.
Bifrost Turns One With AI Builds and New Workflows
Bifrost marks its first year and 10,000 successful builds with an MCP server, automated workflows, managed credentials, and AI build diagnoses.
Preview Blade Templates in macOS Finder with Quick Blade
Quick Blade is a free macOS Quick Look extension that renders .blade.php files in Finder with your layout, compiled CSS, and stand-in data.
Artisan Debugging Commands in Laravel Telescope 5.24.0
Laravel Telescope 5.24.0 adds two Artisan commands for inspecting recorded entries from the terminal and cancels stale dashboard requests during navigation.
Queue totalSize() and JobInterrupted Event in Laravel 13.31
Laravel 13.31 adds Queue::totalSize() to count every job on a connection, a JobInterrupted event, and chaperone support for BelongsToMany pivot models.
Find Unexpected Test Inputs with Fuzz for Pest
Fuzz brings coverage-guided fuzz testing to Pest 5, generating inputs to find failures beyond the cases you write by hand.
Laravel Rulebook: Business Rules That Change by Date
Laravel Rulebook resolves which version of a business rule applied on a given date, returns one winner, and explains why every other rule lost.
Taylor disabled GitHub Issues on most Laravel open-source packages.
If you hit a bug, describe it to a coding agent and open a PR. Even if the code isn't great, that's fine - code can be iterated on. The PR still documents the problem, and a proper fix can follow.