Back to Home page

Patrik Alexits

Frontend Architect

Patrik Alexits travelling in Austria in winter

Architecture, agents, coaching

In my roles I have designed front-end architecture, acted as lead engineer building systems, built harnesses for LLM coding agents and coached engineers, and I still do.

Get to know me

Currently

Now

Updated

  • Working on my indie game in Godot with GDScript.
  • Writing blog articles for this site by hand, in Markdown, without AI-generated text.
  • Visiting car meets and Swiss mountain passes with my RS3.

Skills

What I do best

Some things I do every week, at work and in my free time.

  1. Day job

    01. Frontend architecture

    I turn features of a Windows desktop app into Nx and Angular web applications built for performance, maintainability and security, and that are accessible and easy to use.

    • Nx
    • Angular
    • TypeScript
    • Accessibility
    • DDD
    • System design
    • Design patterns
    • Principles

  2. Side work

    02. Harnesses for LLM coding agents

    Rules, permissions and tests that check a coding agent's work before I review it. This site is built that way, and its repository is public.

    • Claude Code
    • CI gates
    • Playwright
    • Vitest
    • ADRs

  3. With people

    03. Coaching engineers

    I mentor juniors and lead teams with shared terminology, written principles and high standards.

    • Mentoring
    • Code review
    • Principles
    • Scrum

  4. Free time

    04. Learning and experimenting

    I try new tools on my own projects first. This site runs on Astro and plain CSS, and my game on Godot.

    • Astro
    • CSS
    • Godot
    • GDScript

Career

Work experience

Full CV

How I work

Principles

  • Fitness functions

    CI checks the rules I care about, so reviewers don’t have to.

  • Red, green, refactor

    I watch a test fail before I trust it.

  • Definition of Done

    Done means I ran it and saw it work, not that it compiles.

  • Make invalid states unrepresentable

    The types reject a state the app must never be in.

  • Human in the loop

    I review generated code like my own, and the design decisions stay with me.

  • Pre-mortem

    Before I build, I ask the model why the design would fail.

  • Context engineering

    The model gets the contract it needs and nothing more.

  • Small batches

    One concern per pull request, small enough to review in one sitting.

  • Architecture Decision Records

    Each decision is written down with its context and the options it rejected, so nobody reopens it without that context.

  • Ubiquitous language

    The team uses the same names for the same things, in code and in conversation.

Blog

Latest writing

All posts

Questions

Frequently asked

What is an agent harness?

The instructions, permissions, hooks and tests around a coding agent, so its work is checked before a person reviews it.

Do you use AI to write the blog?

No. I write every article myself, by hand, without AI-generated text.

Contact