Technical series

Modern systems.
Practical engineering.

Explore the technologies changing how we build software—and the design decisions that make them useful. Architecture, implementation, and developer practices for teams working with cloud systems and AI.

  • System architecture
  • AI models & retrieval
  • Agents & MCP
  • APIs & integration
  • Developer practices
  • Delivery & observability

Read & apply

A question, a design,
and a way to verify it.

Written guides with runnable C#, Python and TypeScript examples. Each code companion includes beginner setup, debugging instructions and tests. Start with the decision your team is facing.

Models & agentsPython

AI in application systems

Choose the right shape for an AI feature

Compare a model call, a retrieval workflow, and a tool-using agent. Make cost, evidence, and control part of the design from the start.

  • Match the design to the decisions the task needs.
  • Separate model output from authorized actions.
  • Evaluate quality, latency, and cost together.
Read the guide & explore the code
Architecture & designC# · .NET · SQLite

Systems & solution architecture

Design modules before distributing services

Work through boundaries, data ownership, and deployment choices using an illustrative booking system. Extract a service when the trade-off is justified.

  • Start with business responsibilities and invariants.
  • Choose what needs to change independently.
  • Plan migration and recovery alongside the design.
Read the guide & explore the code
AI-assisted engineeringC# · ASP.NET Core

Developer practice & delivery

Use AI through development, review, and release

A practical developer workflow for giving AI useful context, reviewing changes, evaluating model behaviour, and releasing with evidence.

  • Make a small change with clear acceptance criteria.
  • Verify behaviour independently of generated code.
  • Trace failures and control AI usage after release.
Read the guide & explore the code
APIs & reliabilityC# · .NET

Reliable .NET integrations

Handling API failures without duplicate actions

A practical walkthrough of rate limits, account-access errors, and retry decisions in a modular .NET integration layer.

  • Distinguish a rejected request from an uncertain result.
  • Keep retry policy separate from the API client.
  • Test the failure paths that affect your business workflow.
Read the guide & explore the code
Workflows & architectureC# · .NET · SQLite

Architecture for business software

Designing approvals that preserve the original record

How to separate a preview, a reviewed decision, and a posted result in business software, using an anonymized workforce workflow example.

  • Pin the inputs and rules behind a reviewed result.
  • Treat correction as a new, linked business operation.
  • Design retries and concurrent changes into the workflow.
Read the guide & explore the code

On the recording list

Next, from design to code.

Planned video topics. The written guides above are available now; these recordings are not yet published.

  1. 01 / Applied AI

    Build a knowledge assistant with retrieval and citations

    Source access, missing evidence, model selection, and an evaluation set.

  2. 02 / Agents & tools

    Design and test a small MCP tool

    Typed inputs, authorization, tool results, and a controlled write operation.

  3. 03 / Reliable delivery

    Trace a request from API to background work

    Correlation, retries, OpenTelemetry, and deployment checks for a .NET service.

From learning to delivery

Need help applying this?

Bring an integration problem, an AI use case, or an architecture decision your team needs to resolve.

Discuss a technical review