matklad-github-io

The author explains their reasons for avoiding home-manager for dotfile management on NixOS, citing two aesthetic and one practical objection, though the article does not elaborate further in the provided excerpt.

The article offers practical tips for improving code comprehension, arguing that effective debugging and understanding of software systems rely on a mindset of "always blaming" — systematically tracing causality rather than making assumptions — to better navigate complex codebases.

The article presents a simple mechanical habit for developers to catch flaky tests early: immediately after merging a change to the main branch, clone the repository fresh and run the CI commands locally. This practice helps detect infrastructure-dependent or non-deterministic failures before they pollute the mainline.

The article responds to a physicist seeking advice on learning software architecture, suggesting that studying existing open-source codebases, practicing refactoring, and understanding design patterns through concrete examples can help bridge the gap from academic to professional software engineering skills.

The article offers two tips for using zig fmt effectively, targeting both Zig developers and those implementing code formatters.

Zig's built-in error handling uses strongly-typed error codes but leaves error reporting to the user. The idiomatic approach is to pass a Diagnostics out parameter as a sink to generate human-readable error messages when needed.

The author describes a minimalist property-based testing library that can be implemented in just a few hundred lines of code, contrasting it with more complex testing approaches that require extensive research and infrastructure.

The article discusses monotonic time as a fundamental abstraction in computing, noting that monotonicity is often enforced through specific code patterns. It explores considerations around strictly monotonic time implementations.

The article describes a keyboard sequence pattern involving the Up arrow key and Enter key. It appears to document a specific command or navigation sequence using these keyboard inputs.

The author created "box," a thin SSH wrapper for running commands on remote machines. They express interest in developing a similar box-shaped interface for continuous integration systems.

The author reflects on programming knowledge, noting that much of it involves reducing new problems to a vocabulary of known tricks. This is a personal, descriptive post about the author's thought process rather than prescriptive advice.

Safari implemented text-wrap: pretty in 2025, bringing improved typography to web development. This feature enables better paragraph formatting, advancing web technology toward historical printing standards.

The author describes their personal default approach to error reporting, focusing on showing users useful error messages. This follows their previous discussion about Zig's strongly-typed error codes solving error handling.

The author shares a realization about code comment formatting practices, specifically regarding line wrapping techniques for comments in programming.

The article critiques query-based compilers, which are currently popular, by highlighting potential pitfalls and challenges in their implementation. It aims to provide a balanced perspective on this trending approach to compiler design.

The upcoming LSP 3.18 version introduces a Text Document Content Request feature that will significantly simplify implementing a Magit-style user experience for the jj version control system, making it much less hacky than previously described approaches.

The author aims to provide visual illustrations to help explain consensus algorithms, positioning this as complementary to existing formal explanations of Paxos.