Tag
7 related posts.
We picked practices by weighing cost against benefit, and AI has changed both sides of the scale. A tour of which practices get cheaper, which feed the model's context and tools, and where to be careful.
Testing is about confidence and money, not dogma. Know the whole spectrum of techniques so you can pick the ones your context needs, from where your tests start to golden masters on legacy code.
The small recipes I keep coming back to when doing TDD, from naming tests like business scenarios to building test data and keeping database tests fast.
We hold conversations with our code all the time, from the folder structure to the logs in production and the commit history. A tour of where those conversations go wrong, and why business naming matters in all of them.
Three common mistakes with test data, repeated values, unnecessary fields and misleading specific values, and how to avoid them to get clearer, more reliable tests.
Why throwing NotImplementedException or returning null to get your first red in TDD defeats its purpose, and how to get a red that actually verifies the test.
PowerShell switch parameters aren't booleans but SwitchParameter objects, so check them with IsPresent or ToBool(), especially in Pester tests.