Why publish technical notes as an onion service?
A small engineering blog can be served directly through Tor without opening an inbound port on the home router.
TOPIC
Engineering Notes
Lessons, explainers, experiments, and implementation notes.
Programming Can Start With a Communication System
If programming begins as syntax memorization, the relationships inside a system can arrive late. A tiny communication system introduces useful questions immediately: who asks, who answers, and what happens when no answer arrives?
Errors Reveal the Assumptions We Forgot We Made
An error does more than stop work. It can reveal a condition we silently assumed would always be true: the file exists, the network is reachable, the response arrives on time.
Why I Started Saving Packet Captures with the Incident Notes
A short pcap plus context is often more useful six months later than a page of remembered conclusions.
The Future Reader of Your Code Is a User Too
The visible users of software are not the only people who experience it. Someone who later has to understand, change, or debug the code at night is a user of its structure too.
The Mobile Core Lab Became Useful When I Could Break It Predictably
A working lab proves very little. A lab becomes valuable when failures can be introduced, observed and explained on demand.
A Year of Small Network Labs: What Broke Most Often
Most beginner lab failures were not exotic protocol bugs. They were wrong masks, wrong VLANs, missing routes, stale assumptions and tests that did not isolate the failing layer.
Variable Names Preserve the Meaning of State
Knowing that a variable contains a number is not the same as knowing what the number means. A name that preserves unit, time, or state reduces the amount of context a future reader has to reconstruct.
The Edge Voice Device Architecture Finally Connected Firmware, SIP and Backend Work
By the end of the year the interesting problem was no longer a codec or PBX; it was the boundary between device identity, firmware, SIP and backend control.
The Voice Product Stack Was Finally One System, Not Three Projects
Firmware, backend and telephony stopped being separate workstreams once their failure states and deployment policies were designed together.