Git beyond the basics

#704 – November 22, 2026

worktrees, cherry-picks and signed commits

Git beyond the basics: Worktrees, cherry-picks and signed commits
35 minutes by Christian Hofstede-Kuhn

Git tutorials usually stop after the first push. Christian's one covers the middle ground: worktrees for working on multiple branches at once without losing context, fixup commits and interactive rebase for cleaning up history before sharing, and the reflog as a safety net when rewrites go wrong. Signing commits with a hardware token means a leaked access token alone is no longer enough to push code in your name, but rebasing drops signatures unless you explicitly ask Git to re-sign.

One API Provider for Many Travel Data Need
sponsored by SerpApi

Scrape Airbnb stays with prices, ratings & photos. Also explore our APIs for hotels, flights, maps & reviews to power any travel app.

A family tree of software job titles
6 minutes by Ian Miell

Job titles in tech keep changing, but the work mostly stays the same. A family tree of 104 software roles, from the 1940s to today, shows clear patterns: titles split apart and merge back together, old roles return under new names, and some titles barely survive before getting absorbed into others. The Dev and Ops divide has never really been solved — it just keeps getting renamed.

Slack’s migration to a cellular architecture
9 minutes by Cooper Bethea

Slack rebuilt its infrastructure after a 2021 outage where a single data center network failure caused user-visible errors across the entire service. The fix was a "cell-based" architecture where each data center zone only talks to services within itself, so failures stay contained. Engineers can now drain traffic away from a failing zone within minutes using load balancer controls, without dropping requests. This turns a complex distributed systems problem into a simple button press.

Chromium bug caused by a 25-Hour day
6 minutes by ZhenRui Liang

Some countries shift their clocks forward in spring and back in autumn, making certain days 23 or 25 hours long. A bug in Chromium assumed every day has exactly 24 hours, causing a task scheduler to fire in a tight loop on the 25-hour day. The fix adds a 4-hour buffer before rounding to midnight, which handles the extra hour without breaking the once-per-day logic.

Building a mechanical watch in a database
16 minutes by Trevor Dwyer

A working mechanical watch, all 34 parts, was designed and simulated entirely inside a database using spatial geometry. SQL Server handled the flat 2D work well but lacked basic tools like rotation, 3D support, and fast transforms, forcing a move to PostgreSQL and PostGIS. PostgreSQL built the full 3D model, checked every part for clashes, worked out the disassembly order, and computed all 30,901 frames of one minute of running. No physics formulas were coded directly; the correct gear ratios and timing fell out of the shapes themselves.

And the most popular article from the last issue was:

newsletters