01 ABETA JOURNAL
Thoughtful writing from builders, designers, and engineers making software more reliable and resilient. Published in public, peer-reviewed, and completely open.
Why IEEE 754 floating point numbers fail in fintech ledgers, and how we built go-fintech-india with exact integer paise math, UIDAI Verhoeff Aadhaar verification, and zero heap allocations.
How we architected and released @abeta.dev/react-libs v0.17.0 on npm: Compiling W3C design tokens to Tailwind v4 @theme inline directives, APCA contrast enforcement, and zero runtime CSS-in-JS overhead.
How we engineered go-app-kit to eliminate dual-write data loss across distributed microservices using PostgreSQL transactional outbox queues, Change Data Capture, and idempotent consumers.
How we built go-libs to protect cloud services against cascading downtime: Three-state circuit breakers, sliding window token bucket rate limiting, and 64-bit Sonyflake ID generation.
How we structured cloud-native-observability for enterprise Kubernetes clusters: Correlating logs, traces, and metrics with Google SRE multi-window multi-burn-rate alerting rules.
Why standard database transactions choke during high-volume drops, and how OpenStore uses CAS idempotency and memory-mapped queues to deliver instant checkouts.
How we engineered Signal to eliminate tracking cookies while delivering sub-20ms cohort queries and partition-tolerant peer replication.
How modern browser storage and reactive state machines provide instant UI feedback and 100% data privacy with zero cloud latency.
Small teams do their best work when the product, the code, and the conversation stay close together.
Open source grows through clear invitations, useful first tasks, and the trust to let other people shape the work.
The strongest interfaces are not collections of beautiful screens. They are systems that make good decisions repeatable.