Decision Records, Playbooks, and Other Acts of Kindness
You've opened a project you didn't write, hit a wall, and found no one left to ask. The code is there but the why is gone. Here are the small habits that spare the next developer that moment.
A window into how I track work: issue statuses, types, and pull request conventions, with sample PR templates you can copy. Take a look around and keep what's useful.
AMD Pensando™ Networking Solutions for the Modern Data Center
From front-end DPUs to scale-out AI NICs, AMD Pensando™ delivers programmable, open networking engineered for the performance and low latency that modern AI workloads demand.
WireGuard Is Fast, But You're Leaving Performance on the Table | SumGuy's Ramblings
Squeeze every MB/s from WireGuard: MTU sizing, GSO/GRO CPU offloading, AllowedIPs routing, PersistentKeepalive tradeoffs, and iperf3 benchmarks included.
Introduction Hashtables are one of the building blocks of computer science, and deservedly get a lot of attention - but less so within the JVM ecosystem. Part of this may simply be that most JVM code is not written with performance top of mind, or that the default JRE implementation is all-around reasonable - fast, efficient, resistant against attacks, why fix it if it ain’t broke? Today we’re looking at libraries that are interested in squeezing out every last byte and cycle of performance however, and we’ll be focusing specifically on primitive hashtables.
A tutorial on building a merkle tree AIR script in Plonky3 - HashCloak
Build a Merkle tree AIR script in Plonky3 with Poseidon2, SubAirBuilder, constraints, trace generation, and Merkle proof verification for STARK ZK developers.
Time is where application code meets uncertainty: clock skew, wall-clock corrections, ambiguous ordering, late schedulers, and business-calendar boundaries.
In the early 1990s, Don’t Copy That Floppy was an anti-piracy campaign that attempted to connect with computer-savvy youth through the power of hip-hop. While somewhat difficult to imagine gi…
Do I have a favorite standard? Silly question. How could I not? There are so many great ones, each with its own weirdly fascinating story. In a previous job, I spent a lot of time getting to know E…
TL;DR: A good tool is and ought to be invisible—striving to make such tools is the goal of a toolmaker.One habit I see a lot, and have to push back on, is taking a tool's shortcomings and reselling them as a "puzzle game" which is "fun" to solve.I don't want my tools to be "fun". I want my tools to be invisible.Text Editor WarsLet's take vim as an example This is just an example, and applies to other editors too.. I constantly see some people praise it not for what actually makes it good, but by taking the things ...
Generate production-grade API infrastructure from your OpenAPI spec. SDKs, validators, query hooks, and 20+ plugins across TypeScript and Python. Free and open source.