Work

🧼 Reduce your boilerplate As mentioned in Part 1, we’ve moved away from Makefiles and bash scripts in favor of mise. In this final post of the series, I’ll walk you through how we’ve taken things further by sharing tasks across projects and environments—speeding up onboarding and keeping things consistent between dev machines and CI/CD. ⚙️ How tasks work in mise mise offers multiple ways to define and run tasks. After experimenting, we’ve decided to use a mix of both TOML-based and file-based tasks to get the best of both worlds. ...

In our development team, consistency and automation are essential. Here’s how we use Microsoft DevContainers and the fantastic mise tool to streamline tooling and environment setup. The combination of both provides a clean, reliable, and reproducible workflow that scales with the team. DevContainers and Mise ❤️ Using Microsoft DevContainers has significantly improved our development workflow by offering consistent environments across different machines. They make onboarding faster and smoother, especially for new team members, by encapsulating all dependencies and tools. However, one of the trade-offs is the added complexity introduced by layered features like Dockerfile extensions and Compose setups. These layers can sometimes obscure what’s really happening under the hood, making debugging and customization more challenging. ...

Reflecting on Our Legacy: Makefiles and Bash Scripts For many years, Makefiles and bash scripts were the faithful workhorses of our development process. They efficiently automated our tasks, were well-understood by developers, and did the job reliably, day in and day out. Whether it was setting up development environments or automating builds, these familiar tools were the backbone of our workflows. However, as our organization expanded, our trusty old tools began showing signs of strain: ...