Posted on in Programming
Most build tool wrappers start as kindness.
Someone notices that the "real" command is too long, too easy to forget, or too different between local development and CI. They add a Make target, a justfile recipe, a shell script, a package-manager alias, or a small Python helper. Now the team …
Posted on in Programming
Build failures become expensive when they stop being reproducible.
The first failure is usually just a problem. The third person saying "it only happens in CI" is when the problem starts turning into folklore. Someone reruns the job. Someone else clears a cache. A third person changes an unrelated file …
Posted on in Programming
CI output is part of your developer experience.
That sounds obvious until you look at the average failed build. A pull request goes red, the developer opens the CI job, and the first thing they see is a scrollback landfill: dependency installation noise, folded shell wrappers, progress bars, warnings from …
Posted on in Programming
Local CI commands should be boring.
That sounds like faint praise, but boring is exactly what you want from the command that tells a human developer, a coding agent, or a pull request bot whether the repository is healthy enough to trust.
The problem is that many repositories make this …
Posted on in Programming
Build tools are one of those engineering choices that look small until they are not small anymore.
At first, you just need a way to run tests. Then you add code generation. Then there is a Docker image. Then CI needs the same steps as laptops. Then one team needs …
Posted on in Programming
Learn how to start a practical C++ project with Meson, including meson.build, meson setup, meson compile, dependencies, tests, and when Meson is a better fit than CMake or Bazel.
