AI decision controls: separating model proposals from authorized actions with evidence, permissions, and verification.
AI feedback isn't learning: separating memory, runbooks, and model updates for safe agent governance.
Why AI can't 'just' replace enterprise apps: the hidden non-functional requirements that make them dependable.
Explains the concept of an 'agent harness' in AI coding agents, covering components like session, environment, memory, and planning.
A quote from Jeremy Morrell about extensible software on the web, highlighting LLMs lowering extension authoring costs and sandbox primitives for secure deployment.
AI accelerates software development, shifting bottleneck from building to deciding which solutions to adopt, risking fragmentation.
Explores how decoupling in software architecture moves complexity rather than removing it, and why it's a spectrum, not a goal.
Explains why edge components like API gateways must be more resilient than backend services to protect platform availability.
Explores five software architecture mistakes that make systems hard to change, emphasizing understanding the domain before choosing tools.
Explores multi-tenancy in SaaS beyond databases, focusing on isolation through boundaries like compute, deployments, and schema changes.
An analysis of AI personas created by Kenneth Reitz, exploring the Digital Ouija Effect and emergent properties of language models.
A technical article about the pitfalls of modular monolith design, focusing on how a clean separation between modules can become irreversible over time.
Explains the key differences between microservices and AI agents, highlighting broken assumptions and security risks.
Talk on challenges of combining Domain-Driven Design with ORMs in web development, presented at Full-Stack NL meetup.
Explains why joining tables across modules in a modular monolith creates hidden database coupling, undermining architecture.
A curated list of 13 newsletters covering .NET, React, system design, AI, frontend, and engineering leadership to help developers improve.
A blog post assembling a reading list and syllabus for a course on engineering architecture, covering computing systems and cyber-physical systems.
Explores architectural theory in computer science, covering internet, software, and hardware design principles like abstraction layers and protocols.
Explores the trade-offs of using Postgres as a message queue compared to dedicated tools like Kafka, Redis, and RabbitMQ.
Explains why testing needs a seam, not an interface, challenging the common practice of creating interfaces solely for testability.
