In the previous post, “Frieda”, my coaching client, asked about producing test cases for auditors or regulators. In Rapid Software Testing (RST), we find it helpful to frame that in terms of formal testing.

Testing is formal to the degree that it must be done in a specific way, or to verify specific facts. Formal testing typically has the goal of confirming or demonstrating something in particular about the product. There’s a continuum to testing formality in RST.

Artificial intelligence is helping paleontologists and anthropologists reconstruct the complex patterns of interbreeding among archaic populations that led to the modern human race.

As a software craftsman and CLI lover, I'm always looking for the best tools to be as productive as possible.

Let me show you how I use tmux as the foundation of what I call my custom IDE.

Chinese New Year is a festival beyond compare. Technically it’s a week—determined by the lunar calendar but always late January to mid February—but for many, Chunjie (Spring Festival) is more like 40 days of celebrations.

Monkeypatching is dynamically changing a piece of software (such as a module, object, method, or function) at runtime. Monkeypatching is often used for bug fixes or prototyping software, especially when using external APIs or libraries. Pytest uses this feature to allow you to test out interfaces that you don’t want to actually execute. For example, you can create a monkeypatched version of the requests module that doesn’t do the actual HTTP transactions during testing, but just returns fixed data that you set.