# credits
© 2026 Kof Twenty Two. All rights reserved.
built with ♥ by james maes and the q's (qqq, qRun, qBits, qStudio)
~/kof22·©2026·git:ec62f12·api·rssContact·
~·~/blogs·~/projects·~/personal·~/about·api·~/admin·~/stream
Skip to content
james@kof22:~$
Home~
Blogs~/blogs
Field NotesIdeas Into Systems
Projects~/projects
Kof22 WebsitesQQQ Framework
Personal~/personal
PhotographyCarsWood WorkingMetal Working
About~/about
Stream~/stream
Home~
Blogs~/blogs
Field NotesIdeas Into Systems
Projects~/projects
Kof22 WebsitesQQQ Framework
Personal~/personal
PhotographyCarsWood WorkingMetal Working
About~/about
Stream~/stream
james@kof22:~/about$

About Kof Twenty Two

Welcome to Kof Twenty Two. I build software, lead engineering teams, and write up what I learn along the way.

James Maes, with his complete head and shoulders visible.
James Maes

~/image$ Image viewer

James MaesEsc to close
close
minimize
fullscreen
zsh
$neofetch
██╗  ██╗ ██████╗ ███████╗
██║ ██╔╝██╔═══██╗██╔════╝
█████╔╝ ██║   ██║█████╗
██╔═██╗ ██║   ██║██╔══╝
██║  ██╗╚██████╔╝██║
╚═╝  ╚═╝ ╚═════╝ ╚═╝
    ██████╗ ██████╗
    ╚════██╗╚════██╗
     █████╔╝ █████╔╝
    ██╔═══╝ ██╔═══╝
    ███████╗███████╗
    ╚══════╝╚══════╝
james@kof22
--------------
Name:James Maes
Location:St. Louis, MO
Role:CTO / Software Engineer
Focus:Web, DevOps, Photography
Stack:Java, QQQ, TypeScript, Nix
Shell:zsh
Editor:Neovim + IntelliJ
GitHub:KofTwentyTwo
$whoami --about
Passionate CTO and Software Engineer focused on shipping products, building high-performance teams, and turning struggling organizations around.
ready
Explore the writing and projects below.
[Process completed]

$ cat about.md

  1. 01 /From a technical idea to a working system
  2. 02 /Ideas, engineering and the work behind them
  3. 03 /Beyond the keyboard

From a technical idea to a working system

I’m James Maes, a CTO and software engineer. My work connects technical direction with the engineering decisions, teams and delivery practices that make it real.

I care about making complex ideas clear enough to act on. An architecture should make sense to the engineer who has to build it and to the person deciding what the organization needs from it. That means explaining the mechanism, the tradeoffs and the consequences in language each reader can use.

Engineer to Engineer: inspect the architecture, the boundaries, the failure modes and the evidence. CTO to Human: explain what those technical choices mean for people, priorities and the organization. Both perspectives should lead to the same understanding.

Ideas, engineering and the work behind them

This site brings my writing and software projects together. The blogs explore engineering judgment, standards, software delivery and information security, including how those practices change when AI agents become part of the team.

The projects make the engineering visible: architecture, source code, releases and the decisions behind the work. This website is one of those projects, with its own Java backend, publishing tools and delivery pipeline.

The stream puts published work in chronological order. It is a way to follow the ideas and the systems as they develop.

Beyond the keyboard

The Personal section is home to photography, woodworking, metalworking and restoration projects. Its journals keep the decisions, updates and photographs together as the work progresses.

Luke’s truck restoration has its own journal. It is set up to follow the work over two years, with room for dated updates and galleries as there is real progress to share.

  • GitHub
  • LinkedIn
  • Discord
  • james@kof22.com