Engineering portfolio

Work, from idea to operation.

Explore the platforms I've built, the decisions behind them and the experience that shapes my approach.

Explore and plan

Find the evidence most relevant to your project.

This is the starting point for my engineering portfolio. The work spans customer-facing websites, backend platforms, integrations, independent products and the infrastructure that keeps software usable after launch.

Projects show what was built

Use the projects collection to browse platforms and open-source work. Look for a similar workflow, integration or operating environment rather than an exact match to your industry. A booking platform and an order-management system can share important problems around availability, payments and reliable updates.

Case studies explain the decisions

Read a case study when you want the context behind a build: the business problem, the implementation and the delivery choices. Use experience pages to understand my responsibilities across teams, and ventures to see the products I develop independently.

Turn an example into a project brief

Choose one or two examples that resemble your requirements. Tell me what is similar, what must work differently, and which systems already exist. That gives us a practical starting point for discussing scope, constraints and the smallest useful release.

Questions about Software Development Portfolio & Selected Work

Where should I start reviewing the portfolio?

Start with projects for a broad overview, then read the relevant case studies for implementation context.

Are ventures the same as client projects?

Ventures are independently built products. The projects collection separates client and open-source work from those ventures.