Software Engineering · Distributed Systems · Cloud & SDLC

Engineering notes on distributed systems, cloud, and SDLC quality.

I build and sustain enterprise systems where architecture, process quality, and business context matter. My production work is mostly C#/.NET, Angular, messaging, Azure, AWS-connected environments, and technical documentation. This site is my owned place for technical writing about software architecture, cloud, SDLC Kaizen, and knowledge systems.

Production core

Distributed enterprise systems

C#/.NET, Angular, messaging, production support, and technical documentation across education, financial services, insurance, and consortium contexts.

Cloud direction

AWS, Azure, and platform thinking

AWS certified, working with Azure in production, and building toward Kubernetes, Terraform, Ansible, GitOps, observability, and serverless architecture.

Differentiator

SDLC and knowledge systems

I care about requirements, traceability, decision records, onboarding, and how teams preserve context so software stays maintainable after the first delivery.

Core Tech Stack

AWS Azure .NET Node.js Terraform Ansible Kubernetes PostgreSQL SQL Server Agile UML BPMN

Latest posts

Cognitive Offload: An Engineering Manifesto About LLMs, People, Company Reorganisation, and Linguistics

EN

Documenting my experience with Obsidian + OpenCode through a knowledge management lens.

Society's attention is collapsing while knowledge production accelerates. Organisations burn cognitive hours on toil — meetings, context switching, knowledge retention. LLMs are not chatbots or oracles; they are linguistic processors, and linguistics is the science that partly explains them. When the language gap between teams starts to dissolve, value shifts from knowledge scattered across people, meetings, and handovers, toward systems that centralise context between business, people, and code — making the team less dependent on intermediaries for decision-making. This manifesto proposes Knowledge-Based Systems (KBS) with LLMs as the organisational layer that closes the gap. Not prophecy — trajectory.