Engineering notes

Ideas worth carrying into the next build.

Notes on backend design, maintainable systems, technical decisions, and the human side of engineering work.

01

Let PostgreSQL Enforce Your Time Windows

A practical way to prevent overlapping reservations and uncovered entitlements with PostgreSQL 18 temporal constraints, plus the migration limits to plan for.

02

Migrating Remote MCP Servers Without Sticky Sessions

A practical migration plan for MCP 2026-07-28 across stateless HTTP, explicit workflow state, gateway routing, caching, multi-step tools, and OAuth validation.

03

Adopting Free-Threaded Python Without Guessing About Performance

A practical way to evaluate Python 3.14 free threading across dependency compatibility, shared-state correctness, throughput, memory, and production rollback.

04

Migrating to TypeScript 7 Without Breaking Your Toolchain

A staged plan for adopting TypeScript’s native compiler while keeping configuration changes, framework compatibility, CI capacity, and rollback risk visible.

05

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.

06

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.

07

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.

08

Building Big Software That Stays Small

How narrow contracts, explicit ownership, and evidence-driven boundaries keep PHP systems changeable as their responsibilities grow.

09

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.

10

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.

11

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.