CTO / Technical founder
CEO, FrameShift
Notes / Long form / Technical only
Thinking in
public.
Architecture decisions, build logs, systems failures, technical leadership, and occasional frustration with imprecise engineering language.
Distributed systems / 11 min
Networking is a failure-detection problem
DNS, TCP, retries, NAT, and why a timeout can never tell you what actually happened.
Engineering practice / 11 min
Benchmarks without engineering theater
How to share technical accomplishments with enough evidence that confidence becomes reproducible.
AI systems / 11 min
When generation is cheap, verification is the work
Machine-generated proofs, code, and plans move the engineering bottleneck from production to trustworthy validation.
Build log / 11 min
Spot GPUs have no loyalty
A FrameShift build log about unreliable machines, frame leases, and designing for interruption.
Algorithms / 11 min
Algorithms click when state becomes visible
Two pointers, frequency buckets, and selection sort reveal why execution traces teach what final code hides.
Personal note / 11 min
Why I keep building the whole thing
On moving between architecture, interfaces, operations, and the stubborn reality of shipping.
DeFi systems / 11 min
Trust is a systems problem
Why decentralized products need verifiable behavior, not another promise to believe.
Vent / 01 / 11 min
Please stop calling everything AI
A small vent about vague labels, magical thinking, and products that still need to solve something real.
Leadership / 11 min
Leading through better questions
Technical leadership is less about having every answer and more about improving the decisions a team can make.
Engineering / 11 min
Performance is part of the product
In financial systems, speed and reliability are not backend details. They shape confidence.