This page is a collection of cool building blocks.
Fundamentally, debugging is an exercise in changing what a program does to match what it should do. It requires us to know what a program should do, which isn't captured in the code. Sometimes that's easy: What it does is crash, what it should do is not crash. Outside those trivial cases, discovering intent is harder.
This is probably what I care about most in programming: stream processing.

Stream Processing
How to be old in tech Lazy Looping in Python

Emerging Tech
HTML5 intro to semantic HTML RabbitMQ in Depth Kite - AI coding assistant A bunch of tech things I have my eye on. Deno - Run JavaScript more securely than with Node.js. Apache Arrow and Apache Flight - Unify data structures across computer architectures. Avoid serialization penalty. Parquet - columnar data formats are pretty smart Common Crawl project. Postgrest Static site generators: Publii and

TUI (Text UI) libraries

Inspired by this discussion on Hacker News
TypeScript type challenges Building distributed systems without imperative APIs The OAuth Bible Robust Client-Side JavaScript (complement to npm with package scores)

Message Bus / Event Sourcing

Input Validation

The shortest way to suppress favicon 404s in your logs On writing effective automated tests for bug-finding OT vs CRDT re: via data structure traversal systems like XPath, jq: via HN

macOS development Swift dev


- -