The plugin built, packaged and published on the first try. I could not have explained the packaging step to anyone, and I shipped it anyway. After several months of building games, static sites, libraries and plugins with an artificial intelligence (AI) assistant doing most of the typing, that sentence is the whole story: producing code stopped being the hard part, and something else moved into its place.
There are more kinds of software test than anyone can keep straight — unit, integration, contract, snapshot, mutation, smoke, load, chaos. This post walks through each one, what it actually buys you, and whether it earns its place in a real codebase.
Gherkin's real value isn't the .feature file. It's the discipline it imposes: a test that reads as a specification — given this, when that, then this — while every implementation detail stays hidden one level down. A colleague should be able to read the test body and understand the feature without reading a single line of setup code.
When you need to inspect, modify, or replay HTTP(S) traffic, few tools are as powerful and flexible as mitmproxy.
It's open-source, scriptable in Python, and works seamlessly as a man-in-the-middle proxy.
In software development, managing dependencies and state is crucial for ensuring deterministic behavior: for any given input, we aim for a consistent output (This is a key reason behind the growing hype for functional programming, as it emphasizes immutability and stateless functions, simplifying the management of dependencies and state). However, as the number of inputs and modules increases, so does the complexity of handling them, potentially leading to a higher risk of bugs—unintended outcomes. To mitigate this, it's essential to minimize and manage dependencies effectively, acknowledging that they can introduce similar challenges by increasing system interconnectedness and potential failure points.
The following article ("Stop testing your code!") made me think about the benefits of testing beyond Bug Cacthing.
Diving into the world of tests reveals a multitude of benefits beyond the obvious ones (like ensuring functionality integrity and catching bugs early). Let's break down some of these benefits and then touch upon common mistakes that can undermine these advantages.
Testing Shadow DOM elements can be a bit tricky due to their encapsulation. However, you can access the Shadow Root to test the elements inside it. In this article, we'll explore how to test Shadow DOM elements using React, TypeScript, and @testing-library/react.