Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions content/work/generic-user-tasks.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: "User tasks without a screen per task"
summary: "A framework where hundreds of human steps in order workflows share one handler pipeline and one form renderer, so adding a task is mostly configuration."
sector: "Telco"
role: "Lead Developer"
themes: ["workflow-orchestration", "architecture-integration"]
kind: "client"
programme: "telco-service-orchestration"
period: "2025 — now"
date: "2025-06-26"
stack: ["Camunda 8", ".NET", "Vue 3", "Vuetify", "TypeScript"]
---

## Context

Order workflows stop at hundreds of points for a person: confirm technical
details, choose equipment, approve a change. A screen and an endpoint for each
would have meant hundreds of near-identical forms drifting apart.

<Flow
title="Every user task, one pipeline"
steps="Resolve: handler by order and task | Load: fields from metadata | Fill: current values | Render: component by type | Apply: only changed fields"
notes="A task-specific handler exists only when it has to enrich or filter data; everything else falls back to the generic one. | Each field carries its component type, validation, grouping and order. | Repeatable fields expand once per related product, from the order's own relationships. | The UI resolves each component from a registry by its type, so a new field type is one registry entry. | Only fields the user actually changed are written back."
/>

## The pattern

- **Generic by default, specific by exception.** One pipeline for every task; a
dedicated handler only where the data demands it.
- **Forms are data.** The UI renders from field metadata through a component
registry, so screens stay consistent and a fix in the renderer reaches every
task.
- **Adding a task is configuration.** Define its fields; write code only for the
exception.

## My part

I designed and built the framework: handler resolution and the pipeline, the
worklist and task stepper, and the registry-driven form renderer. The team built
the task pool on it and moved the field definitions into a database catalog.
73 changes: 73 additions & 0 deletions content/work/internal-learning-platform.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
---
title: "One engineer, every layer, three months to production"
summary: "An internal training platform built AI-natively: backend, frontend, database, DevOps and operations owned by one engineer, delivered in a governed cycle."
sector: "Corporate learning"
role: "Founder & engineering lead"
themes: ["delivery-operations", "quality-test-strategy"]
kind: "internal"
aiNative: true
period: "2026 — now"
date: "2026-04-06"
stack: [".NET 10", "ASP.NET Core", "EF Core", "PostgreSQL", "Quartz", "Next.js", "React", "Entra ID", "GitLab CI", "Docker", "nginx", "Playwright"]
outcomes:
- { value: "3", label: "months to production", countTo: 3 }
- { value: "400", label: "people using it", countTo: 400 }
- { value: "2000+", label: "automated tests", countTo: 2000 }
featured: true
---

## Context

An organization needed one place for its training: a programme catalogue,
sessions, requests, approvals, attendance and certificates, replacing an older
system whose data was migrated in. A product owner shaped the requirements and
the screen mockups. Every engineering role was mine.

<Compare
beforeTitle="What this usually takes"
before="Backend developer | Frontend developer | Database administrator | DevOps engineer | Someone to run it after go-live"
afterTitle="How it was delivered"
after="One engineer owning every layer | A product owner for requirements and mockups | A governed cycle where AI writes and the cycle decides what is done"
/>

## The system

- **Application:** .NET 10 Clean Architecture with CQRS on PostgreSQL, a
separate worker for scheduled jobs, and a Next.js front end behind a BFF, so
tokens never reach the browser.
- **Integration:** single sign-on with Entra ID, user sync from the HR system,
an email queue with retries.
- **Delivery:** a self-hosted GitLab with its own runner, CI/CD to separate
development, test and production environments, tagged releases with
generated notes.
- **Operations:** structured logs kept in the database and archived on a
schedule; tiered backups with a stated recovery point and restores that are
rehearsed; a daily read-only health check of production.
- **Rules:** every domain rule written as a numbered invariant, each tied to a
test, with the reasoning recorded as a decision record.

## How a task moves

Speed came from the cycle, not from skipping steps. Every change passes the
same gates, with a review between each.

<Flow
title="One task, end to end"
steps="Issue: read from the tracker | Decide: approach and trade-off | Red: a failing test first | Docs: updated with the code | Green: built until suites pass | Edges: integration tests, real database | Browser: E2E in a real browser | Ship: MR with evidence"
notes="The agent reads the issue from the tracker through MCP, so the work starts from the ticket itself. | A bug starts by proving the cause; a feature starts by agreeing the approach before any code. | The failing test is the bug or the acceptance criterion, written as code. A test that passes without the change is rewritten. | Domain docs, the feature map and decision records change in the same commit, so documentation never drifts from the code. | The change is built until unit, integration and end-to-end suites are green. | Integration tests run against a real PostgreSQL in a container and cover the edge cases, not only the happy path. | Because the rules are written down, the agent can drive the feature in a browser with Playwright and check it against them. | The merge request carries the proof, then moves through development, test and production."
/>

<Timeline items="Month 1: Foundation, single sign-on, CI/CD, first environments | Month 2: Domain modules, approval chain, notifications | Month 3: Load and security testing, migration, go-live | Since: in daily use, changes limited to fixes and polish" />

## Proof before go-live

Load- and stress-tested up to 300 concurrent users with no server errors and a
95th percentile under 400 ms. Scanned with SonarQube, OWASP ZAP and a
dependency audit.

## Outcome

In production since the third month and used by around 400 people, with
nothing since go-live beyond bug fixes and cosmetic changes. More than 2,000
automated tests guard it, and when something does go wrong it ends as a rule, a
test and a decision record.
42 changes: 42 additions & 0 deletions content/work/order-orchestration.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: "One process per order"
summary: "How a submitted quote becomes product orders, each running as its own workflow, with downstream systems answering asynchronously and orders that can still be cancelled mid-flight."
sector: "Telco"
role: "Lead Developer"
themes: ["workflow-orchestration"]
kind: "client"
programme: "telco-service-orchestration"
period: "2025 — now"
date: "2025-05-06"
stack: ["Camunda 8", ".NET", "ASP.NET Core", "Refit", "PostgreSQL"]
---

## Context

An order for a business customer touches network inventory, work orders,
billing and people who confirm technical details, and some of those systems
answer days later. Every order needed an explicit state, a way to survive slow
downstream systems, and a precise answer to "can this still be cancelled?".

<Demo id="workflow-stepper" />

## The pattern

- **The process is chosen by data.** A decomposition table, keyed by service and
change type, says which workflow each product order runs. A new scenario is a
row and a process model, not new code.
- **One workflow per product order.** Each runs as its own Camunda 8 instance and
calls back into the services for the business logic, so the model stays about
the flow.
- **Late answers find their order.** Outbound requests carry a message id; a
downstream callback is correlated to the waiting process by it, however late
it arrives.
- **Change is allowed up to a milestone.** The process marks the points after
which cancelling or changing is no longer safe. Before them a request is
applied to the running order; after them it is refused with a reason.

## My part

I built the layer the platform uses to talk to Camunda 8: typed clients over its
REST API for process instances, messages, user tasks, jobs, incidents and
deployments. The team built the process models and scenarios on top of it.
50 changes: 50 additions & 0 deletions content/work/order-platform-foundation.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
title: "A foundation a whole team builds on"
summary: "The service template, shared building blocks, gateway and one-command local environment that every module of a telco order platform starts from."
sector: "Telco"
role: "Lead Developer"
themes: ["architecture-integration", "delivery-operations"]
kind: "client"
programme: "telco-service-orchestration"
period: "2024 — now"
date: "2024-10-02"
stack: [".NET", "ASP.NET Core", ".NET Aspire", "YARP", "Kafka", "Serilog", "PostgreSQL", "Docker"]
---

## Context

A legacy ordering platform was being replaced by .NET microservices, with a team
that would grow past ten engineers. Before the first feature, every module
needed the same answers: how a service is laid out, how it logs, caches, calls
other systems and runs background work, how requests reach it, and how a
developer runs everything on a laptop.

<LayerStack title="What every module starts from">
<Layer label="Gateway" detail="YARP" note="Routes by module through service discovery. Nothing else." />
<Layer label="Template" detail="Clean Architecture" note="API, application, domain and infrastructure, the same in every service." />
<Layer label="Building blocks" detail="shared library" note="Logging, cache invalidation, typed clients, background jobs." />
<Layer label="Environment" detail=".NET Aspire" note="The whole system and its dependencies, one command." />
</LayerStack>

## The decisions

- **One layout for every service.** A developer moving between modules already
knows where everything lives.
- **Logs go to Kafka first,** then to the database in batches, so logging never
slows a request down.
- **Cache invalidation is an event.** A service that changes cached data
publishes it, and every pod clears its copy. Scaling out never serves stale
data.
- **The gateway stays thin.** It routes by module and does nothing else;
authentication stays where it already was during the transition, so the new
platform could grow without first rebuilding security.
- **One command for the whole system.** An Aspire app host brings up Kafka,
PostgreSQL, the legacy Oracle database, the workflow engine, a mock server for
the downstream systems, the UI and every module, with profiles per product and
environment.

## Outcome

A new module starts from a working skeleton, and a new developer runs the full
system locally on day one. I set up the foundation; the team has extended it
since.
3 changes: 2 additions & 1 deletion content/work/telco-service-orchestration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ title: "Order management transformation in the telco domain"
summary: "A legacy B2B ordering stack rebuilt as .NET microservices, one service line at a time, with both systems running side by side and live orders never disrupted."
sector: "Telco"
role: "Lead Developer"
themes: ["legacy-modernization", "architecture-integration"]
kind: "client"
period: "2024 — now"
date: "2026-09-01"
stack: [".NET", "ASP.NET Core", ".NET Aspire", "Camunda", "Kafka", "PostgreSQL", "Vue 3", "OpenShift", "Conceptwave (legacy)"]
Expand Down Expand Up @@ -36,7 +38,6 @@ integrated with the operator's downstream systems.
notes="The product catalog defines what can be sold, aligned with TM Forum. | A quote is built from the catalog and validated; submitting it is the commitment to the customer. | The submitted quote is decomposed into product orders, one per product being delivered. | Each product order runs as its own Camunda process, so every order has a state, a history and a trace. | The process creates the service orders that deliver the product and waits for them. | Downstream systems answer asynchronously through callbacks; the steps that need a person become user tasks."
/>

<Demo id="workflow-stepper" />

## What I built

Expand Down
57 changes: 52 additions & 5 deletions src/app/work/[slug]/page.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,16 @@ import { notFound } from "next/navigation";
import { getTranslations } from "next-intl/server";
import { ArrowLeft } from "lucide-react";
import { RailSection, ReadingShell } from "@/components/layout/reading-shell";
import { Tag } from "@/components/ui/badge";
import { Label, Tag } from "@/components/ui/badge";
import { WorkCard } from "@/components/work/work-card";
import { getTheme } from "@/config/themes";
import { Counter } from "@/components/motion/counter";
import { LabCard } from "@/components/labs/lab-card";
import { Toc } from "@/components/writings/toc";
import { renderMdx } from "@/lib/mdx";
import { extractHeadings } from "@/lib/writings";
import { getLabsBySlugs } from "@/lib/labs";
import { getWorkBySlug, getWorkSlugs } from "@/lib/work";
import { getProgrammeParts, getWorkBySlug, getWorkSlugs } from "@/lib/work";
import { pageMetadata } from "@/lib/seo";

export async function generateStaticParams() {
Expand Down Expand Up @@ -45,10 +47,13 @@ export default async function WorkStudyPage({
const work = await getWorkBySlug(slug);
if (!work) notFound();

const [content, labs] = await Promise.all([
const [content, labs, parts, programme] = await Promise.all([
renderMdx(work.content),
getLabsBySlugs(work.labs ?? []),
getProgrammeParts(work.slug),
work.programme ? getWorkBySlug(work.programme) : null,
]);
const themes = work.themes.map(getTheme).filter((x) => x !== undefined);
const headings = extractHeadings(work.content);

return (
Expand All @@ -57,8 +62,25 @@ export default async function WorkStudyPage({
<>
<dl className="flex flex-col gap-2 rounded-[var(--radius-xl)] border border-border p-4 text-ui">
<Fact label={t("sector")}>{work.sector}</Fact>
<Fact label={t("kind")}>{t(`kinds.${work.kind}`)}</Fact>
<Fact label={t("role")}>{work.role}</Fact>
<Fact label={t("period")}>{work.period}</Fact>
<div>
<dt className="text-caption text-muted-foreground">
{t("themes")}
</dt>
<dd className="mt-1.5 flex flex-col gap-1">
{themes.map((theme) => (
<Link
key={theme.slug}
href={`/work#${theme.slug}`}
className="font-medium text-foreground underline decoration-border underline-offset-4 transition-colors hover:decoration-foreground"
>
{theme.title}
</Link>
))}
</dd>
</div>
<div>
<dt className="text-caption text-muted-foreground">
{t("stack")}
Expand Down Expand Up @@ -87,9 +109,23 @@ export default async function WorkStudyPage({
</Link>

<header className="intro mt-6 flex flex-col gap-4 border-b border-border pb-8">
<p className="mono text-caption text-faint">
{work.sector} · {work.period}
<p className="flex flex-wrap items-center gap-x-2 gap-y-1">
<span className="mono text-caption text-faint">
{work.sector} · {t(`kinds.${work.kind}`)} · {work.period}
</span>
{work.aiNative && <Label tone="info">{t("aiNative")}</Label>}
</p>
{programme && (
<p className="text-ui text-muted-foreground">
{t("partOf")}{" "}
<Link
href={`/work/${programme.slug}`}
className="font-medium text-foreground underline decoration-border underline-offset-4 transition-colors hover:decoration-foreground"
>
{programme.title}
</Link>
</p>
)}
<h1 className="text-h1 font-medium text-balance">{work.title}</h1>
<p className="text-lead text-muted-foreground">{work.summary}</p>
{work.outcomes && work.outcomes.length > 0 && (
Expand Down Expand Up @@ -117,6 +153,17 @@ export default async function WorkStudyPage({

<div className="mt-2">{content}</div>

{parts.length > 0 && (
<section className="mt-14">
<h2 className="mb-4 text-h3 font-medium">{t("parts")}</h2>
<div className="grid gap-4 sm:grid-cols-2">
{parts.map((part) => (
<WorkCard key={part.slug} work={part} />
))}
</div>
</section>
)}

{labs.length > 0 && (
<section className="mt-14">
<h2 className="mb-4 text-h3 font-medium">{t("tryIt")}</h2>
Expand Down
45 changes: 42 additions & 3 deletions src/app/work/page.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ import { WorkCard } from "@/components/work/work-card";
import { QorpeBand } from "@/components/home/qorpe-band";
import { OpenSource } from "@/components/products/open-source";
import { getAllWork } from "@/lib/work";
import { THEMES } from "@/config/themes";
import { pageMetadata } from "@/lib/seo";

export async function generateMetadata(): Promise<Metadata> {
Expand All @@ -20,6 +21,13 @@ export async function generateMetadata(): Promise<Metadata> {
export default async function WorkPage() {
const t = await getTranslations("work");
const work = await getAllWork();
// Featured cases lead the page; every other case is listed once, under its
// first theme. Empty themes are hidden.
const featured = work.filter((w) => w.featured);
const sections = THEMES.map((theme) => ({
...theme,
items: work.filter((w) => !w.featured && w.themes[0] === theme.slug),
})).filter((s) => s.items.length > 0);

return (
<Container className={PAGE_PADDING}>
Expand All @@ -29,9 +37,40 @@ export default async function WorkPage() {
{t("empty")}
</p>
) : (
<div className="grid gap-4 sm:grid-cols-2">
{work.map((item) => (
<WorkCard key={item.slug} work={item} />
<div className="flex flex-col gap-14">
{featured.length > 0 && (
<section aria-label={t("featured")}>
<div className="grid gap-4 sm:grid-cols-2">
{featured.map((item) => (
<WorkCard key={item.slug} work={item} />
))}
</div>
</section>
)}
{sections.map((section) => (
<section
key={section.slug}
id={section.slug}
aria-labelledby={`${section.slug}-title`}
className="scroll-mt-24"
>
<div className="mb-5 flex flex-col gap-1 border-b border-border pb-3">
<h2
id={`${section.slug}-title`}
className="text-h3 font-medium"
>
{section.title}
</h2>
<p className="text-ui text-muted-foreground">
{section.summary}
</p>
</div>
<div className="grid gap-4 sm:grid-cols-2">
{section.items.map((item) => (
<WorkCard key={item.slug} work={item} />
))}
</div>
</section>
))}
</div>
)}
Expand Down
Loading
Loading