Hands-on guides for working developers: databases, Git and code review, JavaScript tooling, containers, repository security and the languages and platforms behind modern software, with code you can run.
A developer's guide to decentralized social: how ActivityPub, the AT Protocol, Farcaster and Lens work, what changed when Farcaster and Lens changed hands in January 2026, a working Bluesky posting script, and realistic first projects.
"Private" isn't a security setting. A hands-on checklist for securing private Git repositories: account and token hygiene, keeping secrets out with Gitleaks, branch rules and CODEOWNERS, signed commits, CI/CD hardening, Dependabot, and what GitHub charges for.
Set up a practical code review workflow on GitHub in under an hour, with CI checks, branch rulesets, CODEOWNERS and a PR template. Then the evidence-based habits (small PRs, fast responses, clear feedback) that make reviews worth doing.
Why do JavaScript projects install hundreds of tiny packages? James Garbutt's essay names three causes: old runtime support, atomic packages, and ponyfills that outlived their purpose. Here's what each means and the tools and code changes that help.
Git 3.0 is scheduled for April 2027, with SHA-256, reftable and "main" as new defaults and Rust as a build requirement. Meanwhile tools like Jujutsu, Sapling and Difftastic are changing how people use Git. Here's what's real and how to prepare.
Gabriella Gonzalez argues that specs detailed enough for AI agents just become code in disguise. Hillel Wayne counters that a spec describes a set of programs, not one. Here's what both get right, and how to write specs that actually help when you code with AI.
Most developers now use AI coding tools, and most don't fully trust them. A step-by-step workflow that gets the speed without the "almost right" code: context files, planning first, small diffs, tests as the contract and review habits.
A viral Hacker News post showed an AI coding agent asking permission, hearing "No", and making the changes anyway. Why agents misread instructions like this, and the practical guardrails (plan modes, permission settings, explicit approval words and git habits) that keep them in check.
Linters, formatters, bundlers and refactoring tools all work on abstract syntax trees. What an AST is, real trees from Python and JavaScript, and working code for finding patterns, writing an ESLint rule and rewriting code safely.
Ki is an open-source modal editor built around selection modes and syntax nodes. What it actually does, how it differs from Vim and Helix, and who might want to try it.
