Skip to content
Flad Logic

About

Hi, I'm Adam.

I'm a software engineer with more than 15 years of experience, most of it building lending software for banks. For a decade I was a founding engineer on a loan origination platform that regional banks ran their lending on.

I owned the work end to end: designing features with bank executives, writing the specs, training users, and running Kubernetes in production. I also took us from two-hour manual releases to fifteen-minute deploys and led our SOC 2 Type 2 certification.

What I'm best at is fitting the pieces together: learning how a team works, connecting the systems it depends on, and automating the slow, error-prone parts. These days I'm building Studio Clarity and taking on consulting through Flad Logic.

01 / Experience

Where I've worked

  1. 2024 – Now

    Founder and Principal Engineer

    Flad Logic

    Building Studio Clarity (beta), multi-tenant scheduling and billing software for dance and martial arts studios, on the same tenant-isolation rules as the bank platform. Taking on fixed-scope consulting.

    • Next.js
    • TypeScript
    • PostgreSQL
    • Claude Code
    • Cursor
  2. 2014 – 2024

    Principal Software Engineer, Founding Team

    LendingLink

    Founding engineer on a loan origination platform used by regional banks with up to $44B in assets to process more than $700M in loans a year. Owned product, platform, security and operations.

    • Java
    • Spring Boot
    • Angular
    • Azure Kubernetes Service
    • ArgoCD
    • Terraform
    • Istio
    • Elasticsearch
  3. 2010 – 2014

    Senior Software Engineer

    Wiredmax

    Built a client's commercial loan origination platform that processed more than $1B in loans and cut funding times by 30%. Led the team through an early-stage build.

    • C#
    • ASP.NET MVC
    • SQL Server

View the full resume (PDF)

02 / Principles

How I work

  1. 01Make deploys boring.If releasing is scary, you release less. Automate it until it's a non-event.
  2. 02Automate the slow, error-prone parts.People should spend their time on judgment, not copying data between systems.
  3. 03Learn how the team actually works.I sit with the people who use the software before I design anything.
  4. 04Leave an audit trail.Decisions, approvals and changes should be easy to prove later.
  5. 05Hand it over.When I'm done, your team owns it and can run it without me.

03 / Tools

How I build with AI agents

I use Claude Code and Cursor every day, like most developers now. What I add is the part around them. I spent a decade shipping software to banks, where every change was reviewed, tested, deployed by pipeline and could be proven to an auditor later. Code an agent drafts gets held to that same bar. Here's how that works as of October 2026.

  1. 01I write the planRequirements, data model and the shape of the change come from me, usually as a short spec the agent can follow.
  2. 02Agents prototype and draftClaude Code and Cursor build quick prototypes to test an idea, then draft the implementation and the tests to go with it.
  3. 03I review it; tests and CI decideAgent output gets the same review as a teammate's pull request, and nothing ships unless the tests, type checks and pipeline pass.
  4. 04Some things stay with meArchitecture, security, data migrations and anything touching production access are mine to design and verify.

In practice: Studio Clarity

Studio Clarity is multi-tenant, like the bank platform was, so the most expensive mistake an agent can make is a query that forgets which studio it belongs to.

The repo's agent instructions say every page and server action must check the user's studio and scope every query by it, store money as integer cents, and read the time from the studio's own clock. Then the end-to-end tests try to break those rules: they sign in to one studio and try to open another studio's admin pages and files. No change is pushed until lint, type checks and those tests pass.

04 / Skills

What I work with

Languages and frameworks
JavaSpring BootTypeScriptAngularC#/.NETSQLReactNext.js
Cloud and DevOps
AzureAWSKubernetesDockerIstioTerraformAnsibleArgoCDGitHub ActionsLinux
Data
PostgreSQLSQL ServerElasticsearchRedisRabbitMQ
Security and observability
SOC 2 Type 2OIDC/OAuthSingle sign-onSnykCentralized loggingMonitoring and alertingZabbix

EducationWeb Application Development, Gateway Technical College, Kenosha, WI

Available now

Hiring, or need something built? Let's talk.