Software Engineering

For “cool tech stuff” see Tech.

Development

• https://conventionalcomments.org/

• https://www.conventionalcommits.org/

Infrastructure

• Artificial Intelligence Infrastructure-as-Code Generator

• 7 Core Elements of an Internal Developer Platform

• How to make an Impact as a Platform Product Manager

• Automating safe, hands-off deployments

• Awesome Load Management

• The Service Mesh Landscape

DevOps

• DevOps uses a capability model, not a maturity model

Metrics / Observability

• You Only Get 3 Metrics - Which Ones Would You Pick?

• OpenTelemetry Tracing in 200 lines of code | Jeremy Morrell

• All you need is Wide Events, not “Metrics, Logs and Traces”

• A Practitioner’s Guide to Wide Events | Jeremy Morrell

Developer Experience (DevEx)

• How To Get Buy-in for DevEx Initiatives: Strategies From GitHub, Notion, and More

• DevEx: What Actually Drives Productivity

Assorted Tools

• googleapis/release-please: generate release PRs based on the conventionalcommits.org spec

• cyrus-and/gdb-dashboard: Modular visual interface for GDB in Python

• 15r10nk/inline-snapshot: create and update inline snapshots in your python tests

• microsoft/markitdown: Python tool for converting files and office documents to Markdown.

• janestreet/bonsai: A library for building dynamic webapps, using Js_of_ocaml

• High-Performance SBOM Analysis Tools | Bitbom

• trustme: #1 quality TLS certs while you wait — trustme 1.2.0+dev documentation

• simeji/jid: json incremental digger

• frectonz/pglite-fusion: Embed an SQLite database in your PostgreSQL table. AKA multitenancy has been solved.

• coollabsio/coolify: An open-source & self-hostable Heroku / Netlify / Vercel alternative.

• MightyMoud/sidekick: Bare metal to production ready in mins; your own fly server on your VPS.

• Task

• wagoodman/dive: A tool for exploring each layer in a docker image

Learning Through Doing

• Introducing “Implement DNS in a Weekend”

• Writing a Simple Garbage Collector in C

• Write your Own Virtual Machine

• Building a distributed log using S3 (under 150 lines of Go) - blag

Career

• From engineer to head of engineering | Tales about Software Engineering

• 11 Articles that Heavily Impacted my Career Trajectory in Tech | Thiago Ghisi

• The Best Programmers I Know | Matthias Endler

Pull Requests and Code Reviews

• Code Reviews

• Your code sucks, and I hate you · jml :: Jonathan Lange

• Levelling up Pull Requests

Data Structures and Algorithms

• arXiv:1608.03960v1 [cs.DC] 13 Aug 2016 1 A Conflict-Free Replicated JSON Datatype

Misc

• Read Every Single Error

• Amir’s 10 Laws of Tech

• My Approach to Building Large Technical Projects

• Page Weight Matters

• A beginner-friendly introduction to Kubernetes

• Lullaby Language

• Talk Like A Systems Engineer: Yaks All The Way Down

• Ditherpunk — The article I wish I had about monochrome image dithering

• Whose Cert Is It Anyway?

• Netreap: A Practical Guide to Running Cilium in Nomad

• Building Customer-Facing Real-Time Dashboards with Postgres

• Language Tooling Antipatterns

• Technology Decision Making (and Boring Technology)

• What is Technical Debt?

• Refactoring CI/CD for a Moderately Large C++ Code Base

• Agility and Architecture: Balancing Minimum Viable Product and Minimum Viable Architecture

• User Story Template: What It Is and Why It Works So Well

• Avoiding the Rewrite Trap

• Should You Use Upper Bound Version Constraints? -

  • “Capping dependencies has long term negative effects, especially for libraries, and should never be taken lightly. A library is not installed in isolation; it has to live with other libraries in a shared environment. Only add a cap if a dependency is known to be incompatible or there is a high (>75%) chance of it being incompatible in its next release. Do not cap by default - capping dependencies makes your software incompatible with other libraries that also have strict lower limits on dependencies, and limits future fixes. Anyone can fix a missing cap, but users cannot fix an over restrictive cap causing solver errors. It also encourages hiding issues until they become harder to fix, it does not scale to larger systems, it limits your ability to access security and bugfix updates”

• Tech debt metaphor maximalism - apenwarr

• DevOps Notebooks Built with Markdown

• How do you cut a monolith in half? — programming is terrible

• Bugs Optional? - by Kent Beck

• the sudoku affair • Buttondown

• Tolerating full cloud outages with Monzo Stand-in

• Loopwerk: uv just keeps on getting better

• Dependency Management Data

• XOR

• The Problem with Using a UUID Primary Key in MySQL — PlanetScale

• Monolith: Real Time Recommendation System With Collisionless Embedding Table

• Cognitive load is what matters

• Institutional memory and reverse smuggling

• TBM 320: From Fluffy Concepts to Concrete Outcomes & Behaviors

• Tossed Salads And Scrumbled Eggs — Ludicity

• Lessons from 4 years of weekly changelogs | Blog | incident.io

• Egoless Engineering

• My Red Hot ADHD Programming ‘Affliction’

• The Practical Guide to Scaling Django

• How we page ourselves if incident.io goes down | Blog | incident.io

• APIs as infrastructure: future-proofing Stripe with versioning

• Old school architectures making a return, part 2: Backend rendered webapps

• Python Type Hints: How to Gradually Add Types for Third Party Packages - Adam Johnson

• The reality of long-term software maintenance - Ashley’s blog

• RDEL #75: How do interruptions impact different software engineering activities?

• 5 mindset shifts needed to grow from engineer to leader

• Infrastructure Platform Teams - Infrastructure as Code

• 1x Engineer

• Monki Gras 2025: What I’ve Learned by Building to Last – alexwlchan

• Everything I Know About Shipping Code Faster

• Take This On-Call Rotation and Shove It § Scott Smitelli

• Postel’s Law and the Three Ring Circus · Alex Gaynor

• Notes on coreutils in Rust · Alex Gaynor

• Against Vibecoding (Sorta) | shimweasel.com

• The Software Engineering Identity Crisis - Annie Vella

• A note on the USB-to-PS/2 mouse adapter that came with Microsoft mouse devices - The Old New Thing

• The 300% Production Problem | lbr.

• The Product Engineer – Rands in Repose

• Why speaking to users is a good idea. - by Jeff - JoT

• jwz: Wherein wrapping text remains the hardest problem in computer science.

• Non-Project Backlog Management for Software Engineering Team

• Fix your flaky tests first. - by Jeff - JoT

• Scrum Doesn’t Say… - adrianhoward.com

• Scrum Guide | Scrum Guides

• Common misconceptions of Trunk-based development | Bucket

• Is ops a bullshit job? – Dan Slimmon

• What Is a Modular Monolith? - by Dr Milan Milanović

• You can’t stop the business, or why rewrites fail | Swizec Teller

• Agile & Multitasking: Escape the Busyness Trap - Mountain Goat Software

• Programming With Chronic Pain | Thomas Vogelaar

• [Draft] Rewilding Software Engineering | by swardley | feenk | Medium

• Don’t make these feature flag mistakes - by Ian Vanagas

• Parsing JSON is a Minefield