Engineering notes
Ideas worth carrying into the next build.
Notes on backend design, maintainable systems, technical decisions, and the human side of engineering work.
Designing a Redacted Provenance Ledger for Laravel AI Agents
How to track which user, retrieval, tool, and application inputs entered an agent invocation without turning observability into a second store of sensitive content.
Backporting Meilisearch Dynamic Search Rules Without Dropping PHP 7.4
A field note on moving a modern Meilisearch PHP feature onto v1.x while preserving its public conventions, PHP 7.4 support, and a green integration suite.
Designing CI-Safe Evaluation Baselines for Laravel AI Agents
How to persist redacted security-evaluation baselines, preserve distinct failure categories, and emit safe GitHub Actions annotations from Laravel.
Building Big Software That Stays Small
How narrow contracts, explicit ownership, and evidence-driven boundaries keep PHP systems changeable as their responsibilities grow.
Choosing a Startup Stack by Constraints, Not Hype
A practical framework for choosing a product stack from team, delivery, data, and operational constraints—without pretending technology can predict business success.
When Leading Feels Lonely
Decision isolation is a structural risk in engineering leadership. These practices create support without leaking trust or pushing uncertainty onto the team.
Leading When You’re Not the Loudest in the Room
A practical approach to engineering leadership through written context, precise questions, visible decisions, and consistent follow-through.