Ship Software That Does Nothing
https://kerrick.blog/articles/2025/ship-software-that-does-nothing/
Ship Software That Does Nothing
https://kerrick.blog/articles/2025/ship-software-that-does-nothing/
...source code, invoking any #codeanalysis tools, running the #automatedtests, versioning the deployment artifacts, #provisioning the #infrastructure, updating the database schema, deploying to a staging slot and then, after proven healthy, swaps it with the production slot. All without having to share production passwords to developers, and without anybody connecting to the production environment and manually running scripts and other command-lines. And if your manager...
If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.
ideally, there is a Test Engineer or QA team that can either write the functional tests, or confirm that those being referred to are legitimate and sufficient.
It's just important that when something is a barrier between your feature code and shipping there should be someone responsible for helping the team keep it green.
If your #git #repository runs #automatedTests or #linters #precommit or #prepush I WILL --no-verify that shit *everytime*
I think that "write a test for every bug" is a foolish advice.
Write #tests for business logic only. Everything else is an implementation detail.