What I Am Doing Right Now
A transparent, monthly update outlining my primary engineering priorities, production software initiatives, technical reading list, and operational constraints.
Inspired by Derek Sivers' public /now page project, this document serves as a public declaration of focus. If you are wondering what I am spending my working hours on, what kind of problems I am wrestling with, or whether I have capacity for new advisory projects, this is the canonical source.
Working with distributed partners and clients across the US, UK, and Asia-Pacific.
Limiting meetings to 2 days per week to protect consecutive engineering blocks.
Open for 30-minute private architectural and FinOps advisory calls.
Reviewed and updated on the first calendar day of every month.
Primary Operating Commitments
Scaling Fraoula Data Auditor & In-Memory Architecture
As Co-Founder and Chief Product Officer, the majority of my focus is dedicated to advancing Fraoula's technology core. We are currently scaling our cryptographic validation engine to process upwards of 50 million daily inspection records while strictly preserving our sub-350-millisecond response budget.
- Benchmarking zero-disk memory wipes to guarantee compliance with new Swiss and European data residency statutes.
- Refactoring our Redis ring-buffer partitions to eliminate cross-datacenter synchronization jitter.
- Collaborating with enterprise health-tech clients to verify outbound transaction logs without saving patient names to disk.
Writing "The In-Memory Architecture Handbook"
I am finalizing the manuscript for my next book, a practical handbook dedicated to teaching engineers how to build fast, sub-second systems by respecting the physical computer memory hierarchy. Too many web applications crawl slowly because developers treat databases like infinite filing cabinets instead of keeping hot working state in RAM.
- Writing Chapter 7: Zero-Copy Ring Buffers and Streaming Primitives in Production.
- Publishing weekly companion breakdowns to 15,000+ engineers via The Weekly Letter.
- Preparing complete open source benchmark scripts in Rust and Node.js for readers to test locally.
FinOps Cloud Reviews & Architecture Advisory
I maintain a strictly limited consulting advisory practice for technology founders, CTOs, and VP of Engineering leaders seeking independent, mathematically grounded reviews of their cloud infrastructure and latency profiles.
- Conducting one two-week Speed & Cost Audit for a mid-stage FinTech organization aiming to cut $40,000 in monthly AWS spend.
- Holding 2 weekly 30-minute private advisory sessions with engineering founders.
Active Technical Research Questions
When I am not shipping production code, I explore foundational systems questions in my notebook and local development environment:
SIMD Vectorization for JSON Parsing
Exploring how modern CPU vector registers (AVX-512 and ARM NEON) can parse incoming JSON request payloads in parallel, eliminating string allocation overhead in low-latency microservices.
Lightweight Byzantine Consensus for Agents
Investigating minimal cryptographic quorum protocols that allow autonomous AI agents to agree on state transitions without relying on centralized coordination servers.
The Post-SaaS Outcome Pricing Model
Analyzing the mathematical breakdown of per-seat software pricing and formulating replacement models where software charges strictly per verified transaction or computational output.
Hyper-Lean Software Studios
Documenting operational patterns that allow 10-person software organizations to maintain multi-million-dollar software portfolios with zero middle management and zero bureaucratic meetings.
What Is Currently on My Desk
I read physical books every morning and evening. Here are the three titles currently sitting on my reading desk:
Database Internals
Re-reading Petrov's definitive guide to B-tree storage engines, LSM-tree append logs, and distributed consensus mechanisms. Essential reading for every systems architect.
The Master and His Emissary
An expansive exploration of hemisphere specialization, human attention, and the cultural dangers of prioritizing narrow bureaucratic efficiency over holistic human context.
Systems Performance
The benchmark manual for Linux kernel profiling, CPU instruction counters, eBPF tracing, and eliminating memory bus bottlenecks in high-throughput enterprise servers.
What I Am Saying "No" To
Focus is not defined by what you say yes to; it is defined by what you choose to ignore. To protect the quality of my engineering and writing, I adhere strictly to these boundaries:
No Agenda-Less Meetings
I decline all conversational meetings without a written one-page memo sent at least 12 hours in advance. If a question can be resolved via an asynchronous email, that is where it belongs.
No Premature Microservices
I refuse to architect distributed microservice meshes for teams smaller than 50 engineers. A disciplined, modular monolith scales farther, costs less, and avoids operational nightmare states.
No Vanity Headcount Growth
We measure engineering success by business cash flow and platform reliability per engineer, never by total team size. A small team of 10 exceptional builders is the ideal organizational structure.
No Speculative Technology Churn
We do not rewrite working software just because a new framework launched on social media. We choose stable, boring technologies with proven track records of reliable production uptime.
Want to Collaborate or Discuss an Architectural Challenge?
If you have a production cloud optimization challenge, need a technical review of your software latency, or want to explore an advisory engagement, let us connect directly.