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.
How to be old in tech
Lazy Looping in Python
HTML5 intro to semantic HTML
RabbitMQ in Depth
Kite - AI coding assistant
A bunch of tech things I have my eye on.
Apache Arrow and Apache Flight - Unify data structures across computer architectures. Avoid serialization penalty.
Parquet - columnar data formats are pretty smart
Common Crawl project.
Static site generators: Publii and https://www.11ty.dev/
TypeScript type challenges https://github.com/type-challenges/type-challenges
Building distributed systems without imperative APIs
The OAuth Bible
Libraries.io (complement to npm with package scores)
Message Bus / Event Sourcing
The shortest way to suppress favicon 404s in your logs
On writing effective automated tests for bug-finding
OT vs CRDT https://en.wikipedia.org/wiki/Operational_transformation
data structure traversal systems like XPath, jq: https://nigeltao.github.io/blog/2020/jsonptr.html
https://textdb.dev/ via HN
Swift dev https://developer.apple.com/tutorials/swiftui/creating-a-macos-app#introduction