The hottest Build Systems Substack posts right now

And their main takeaways
Category
Top Technology Topics
Bite code! • 1712 implied HN points • 14 Dec 25
  1. Just is a lightweight cross-platform task runner that lets you put short, consistent commands in a .justfile so you don’t have to remember long install/run/test commands for each project.
  2. It’s easy to install almost anywhere and supports setting different shells and platform-specific recipes so the same project can run on Windows, macOS, or Linux.
  3. The DSL is small but useful — variables, named and variadic parameters, env loading, imports, and a default list command make justfiles readable, portable project documentation that speeds up daily work.
Blog System/5 • 744 implied HN points • 24 Nov 25
  1. Bazel is getting better with mandatory features like bzlmod and a real BUILD Foundation to support its community. This means it's growing up and easier to use.
  2. The Bazel team is really focused on making builds faster and more efficient, with cool new tools like Skycache for speeding things up on the client side.
  3. Community-driven tools are expanding Bazel's reach, solving old problems. For example, Aspect's task runner helps fill in gaps and improve work processes.
Blog System/5 • 661 implied HN points • 21 Jul 25
  1. Bazel builds need to be deterministic to avoid issues. If builds aren't consistent, they can fail unexpectedly, making it hard to trust the system.
  2. Non-determinism in builds can come from various sources like timestamps, random data, or changes in environment. It's important to identify and manage these to ensure reliable builds.
  3. To prevent non-determinism, use controlled environments and keep settings consistent across machines. This includes managing toolchains and avoiding network access that could introduce variability.
Infra Weekly Newsletter • 4 implied HN points • 03 Mar 26
  1. OS‑level and toolchain dependencies are often left unmanaged, so CI becomes the only place the full environment reliably exists and developers end up in a commit→push→wait debugging loop.
  2. Tooling sits on a spectrum: asdf/mise pin runtime CLIs, Devbox gives a consistent per‑project shell, and Nix provides declarative, reproducible builds — treating the environment as a first‑class artifact makes local‑first, reproducible pipelines practical.
  3. YAML+embedded shell turns pipelines into untestable code, so keep build/test logic in locally runnable artifacts (Nix/Devbox) and reserve YAML for orchestration, permissions, and deployment policy.
Subsack • 3 HN points • 22 Feb 24
  1. Bazel can be amazing for bigger projects, but setting it up takes a lot of time, which startups often don't have. It's crucial to focus on building a product quickly before diving into complex systems.
  2. Using Bazel with languages like Python and JavaScript can be tricky because they aren't as well supported. It can lead to a lot of wasted effort if you're not careful about the tools you choose.
  3. While Bazel has great potential, it's often not the right choice for startups due to the time and resources needed. It's better to find a simpler solution until you have a stable system.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Zig

Why Now • 1 HN point • 12 Jun 23
  1. Zig is a programming language efficient and simple like C, but without hidden surprises in its memory management.
  2. Zig offers developers a clear and explicit approach with minimal language-specific keywords for simplicity and readability.
  3. Zig's toolchain provides various build modes catering to different needs such as Debug, ReleaseSafe, ReleaseSmall, and ReleaseFast.