Software Engineering

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

Misc

• Read Every Single Error

• Explaining

• Amir’s 10 Laws of Tech

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

• My Approach to Building Large Technical Projects

• Page Weight Matters

• All the Hard Stuff Nobody Talks About when Building Products with LLMs

• Introducing “Implement DNS in a Weekend”

• 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

• llm, ttok and strip-tags—CLI tools for working with ChatGPT and other LLMs

• Task

• DevEx: What Actually Drives Productivity

• Language Tooling Antipatterns

• Technology Decision Making (and Boring Technology)

• What is Technical Debt?

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

• Levelling up Pull Requests

• 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

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