Independent Angular engineer & consultant
Reusable interfaces, data-rich workflows and system integrations — from architecture to tested releases. I work directly with teams on new features, modernization and the technical decisions behind growing products.
Project delivery or a role in your team. Working together ↗
01 / Selected work
My own product, the shared UI behind it
and the way it is delivered.
Case study · Own product
A map portal for Poland, built as a thin domain application over shared UI and map libraries.
Parcel search, layers, attribute tables, reports, printing and an experimental assistant that drives the portal through the same commands as the keyboard. The case study explains the architecture, my contribution and the evidence behind the implementation.
Shared Angular UI and a catalog of 53 pattern pages: tables, forms, files, commands and an assistant.
Explore the shared UI Process · DeliveryFrom a change to a verified release: clear boundaries, regression tests, human review and remote CI gates.
See the delivery process02 / How I can help
A review and a plan, a modernization, a map application, or an assistant with the person in charge.
A review of boundaries, state, shared UI, tests and delivery, with a prioritised plan your team can start on.
02 /Standalone components, signals, zoneless change detection and Nx, introduced step by step with checks for the behaviours each stage affects.
03 /Map applications on reusable layers: data integrations, drawing, reports and printing, built on a tested library.
04 /Assistants built around real tasks, with visible actions, confirmation rules, limits and evaluations against an agreed baseline.
03 / How a product is made
I start from the user's task and the risks of the change. Product rules and shared behaviour get clear owners; regression tests protect the affected workflows. I review the result and use CI checks matched to the release policy.
The result is an application whose decisions are written down and whose state a new person — or a new team — can take over.
See the delivery process04 / AI, with people in charge
GeoAtlas includes an experimental assistant that turns a sentence into map commands. The application enforces confirmation rules and offers undo for supported actions. I also use coding agents for defined implementation tasks, with written briefs, tests and human ownership of the result. The articles explain the evidence and the limits of both approaches.
How the assistant is built05 / The person behind the work
I work across Angular architecture, reusable libraries, geospatial and agentic interfaces, and document-heavy systems. Open-source contributions are part of that practice: understand the problem, make a focused change and verify the result.
Outside product work, I explore deployment, observability and local AI in my personal homelab. Experiments with Hermes and agent interfaces give me a place to test ideas, record failures and bring useful lessons back to application development.
Inside the homelabOne command core, AG-UI events, confirmations and undo, guardrails in code, recorded tests and evals.
Read the article ↗Delivery · AI agentsBounded tasks, written briefs and reviewable evidence from building GeoAtlas.
Read the article ↗Angular · ModernizationThe order that keeps the product working, with the pitfalls of each step.
Read the article ↗Angular · Web mappingWho owns the map, layers as components, bridging OpenLayers events to Angular signals, destroying and testing a map.
Read the article ↗Let's work through it
Describe your project and the stage where you need help. If you are hiring, tell me about the Angular product, the role and the team. We can start with one concrete question.
contact@clearcraft.devYou work directly with me, from the first conversation to the handover.