SDD
Engineering PracticeSpecification-driven development for complex software changes
How I make scope, constraints, architecture decisions, acceptance evidence, and handoffs explicit before implementation.
Notes about the decisions, constraints, and evidence involved in designing and evolving backend and business systems.
CURRENT WORK
The current practice extends beyond a framework list: data integrity, concurrency, authorization, system design, and disciplined delivery.
SDD
Engineering PracticeHow I make scope, constraints, architecture decisions, acceptance evidence, and handoffs explicit before implementation.
AI-assisted Engineering
Engineering PracticeI separate planning, implementation, review, and release decisions so complex AI-assisted changes remain inspectable.
PostgreSQL
Engineering PracticeTenant isolation is a system boundary: trusted context, application authorization, database policies, and tests must agree.
EARLIER WORK
The earlier archive remains available for context.
Topic
Architecture, PostgreSQL, concurrency, authorization, SDD, and review practices for systems that must remain understandable as they evolve.
The current practice extends beyond a framework list: data integrity, concurrency, authorization, system design, and disciplined delivery.
Relational constraints, transaction boundaries, tenant isolation, and reliable state changes.
Optimistic concurrency, authorization boundaries, and workflows that remain safe under change.
SDD, architecture reviews, specialized responsibilities, evidence, and release gates.
Durable handoffs, idempotency, and asynchronous patterns considered with explicit trade-offs.
Bounded specialized roles that support analysis and implementation while engineering decisions remain human.