Part 9 of the Musaned series: the technical companion to the one-week launch story — how memos, circulation, voting, and permanent decision records are modeled in Laravel and Filament.
Part 6 of the Musaned series: the architecture that kept countless integrations manageable — one service class per external system, carefully ordered queues, and Redis as the cache store.
Part 5 of the Musaned series: fiber customer information lived in Microsoft SQL Server, and getting PHP to talk to it reliably was its own dependency saga — with different traps than Oracle.
Part 3 of the Musaned series: why the first real feature was invisible — syncing employees from the corporate directory and building role-based access control that decides everything users can see and do.
Part 2 of the Musaned series: why Laravel 10 and Filament v3 let a single engineer ship enterprise features at a pace that made the build-vs-buy decision look obvious in hindsight.
