How I approach technical work

Trax Armstrong’s working approach emphasizes clear requirements, evidence, reviewable changes, AI-assisted workflows, and maintainable handoffs.

I start by understanding the desired outcome and the systems already in place. Existing users, account ownership, data, and operational dependencies shape what can safely change.

System design and performance

I map the data path and the relationships between applications, databases, networking, and operating-system resources. My continuing study includes Brendan Gregg’s Systems Performance and Jason Cannon’s Linux Administration. I connect workload observations, latency, resource use, and recovery constraints to the decisions being made, then validate changes against the task people rely on.

Use evidence and preserve context

I separate measured behavior from assumptions and record the decisions that matter. Before a change, I want to know how the result will be checked and how we would recover if it fails.

Use AI with responsibility

I use AI tools in daily work for research, drafting infrastructure code, reviewing changes, troubleshooting, and documentation. Their output still needs context, inspection, and validation. Responsibility for the result remains with the people making the change.

Communicate so the work can continue

I work comfortably with remote teams and English-language technical communication. I continue studying Japanese. Written preparation and clear documentation help make cross-language collaboration more precise.