About

A little more context than a bio box usually allows.

This is the part where I am supposed to sound coherent, accomplished, and suspiciously tidy. I will settle for honest, useful, and just self-aware enough to know the difference.

Who I am

I am Charles, a software engineer with a soft spot for thoughtful tools, sharp writing, and ideas that survive contact with actual users. I like systems work, product thinking, and the kind of engineering problems that ask for both rigor and taste. Somewhere along the way I developed a habit of turning curiosity into projects, notes, prototypes, talks, and occasionally a strong opinion with a README attached.

The short version is that I enjoy building things that feel alive: apps that solve a real problem, internal tools that save a team from death by repetition, small experiments that reveal bigger patterns, and writing that helps me think in public without pretending every draft is a thesis. I am interested in software not just because it scales, but because it lets you compress judgment into systems other people can use.

What I work on

Lately I keep returning to the overlap between software engineering and AI-assisted workflows. Not the theatrical version where everything becomes “autonomous” overnight, but the grounded version where a tool meaningfully reduces friction, improves a decision, or helps someone move faster without handing their brain to a probability machine.

I am drawn to products with a strong point of view: developer tools with clear ergonomics, AI features that respect user attention, internal systems that feel calm instead of chaotic, and side projects that act like tiny research labs. If I can learn something practical, ship it, and write about what worked, that is usually a pretty good week.

By day, I lead quality assurance efforts at DT One, helping build systems that are reliable, stable, and ready for real-world use. Outside of that, and often outside the kitchen, I spend my time exploring AI and open-source models, mostly to understand how they work and where they can be applied in practical ways.

What I care about

I care about clarity. In code, in writing, in product decisions, in meetings that threaten to become folklore. I like systems that explain themselves, interfaces that respect the person using them, and engineering cultures where people can say “I am not convinced yet” without turning it into a personality contest.

I also care about the craft side of the internet: learning in public without becoming a content mill, building in a way that leaves room for taste, and staying curious enough to be wrong on the way to something better. The technology changes fast. Good judgment still has to be earned the long way.

Speaking and events

I like talking about engineering when the goal is insight rather than performance. That usually means talks about building side projects that teach quickly, the practical realities of using AI in developer workflows, or the messy but interesting gap between a neat architecture diagram and a system that has met production traffic.

I am especially interested in meetups, community events, podcasts, and panels where the conversation can stay technical without becoming sterile. Good events feel like a shared annotation layer on the industry. You leave with sharper questions than the ones you walked in with.

What this site is for

This site is my personal corner of the internet: part portfolio, part notebook, part public archive of what I am learning. It is where I can write longer than a post, point to what I am building without turning it into a pitch deck, and collect ideas that would otherwise disappear into tabs, drafts, and suspiciously confident voice notes.

If you are here because you care about software engineering, AI, machine learning, product thinking, or internet culture with a little more signal than average, you are exactly who this is for. If you are here by accident, you can still stay. There are worse corners of the web.