A fresh blog post dives into how to get devs pulling their weight on test automation - not as extra credit, but as part of shipping code.
The playbook: tie automation work straight to the definition of done, clear up who owns what, and stop pretending delivery pressure is a mystery. The big idea? Most “why aren’t tests written?” problems aren’t technical. They’re cultural.
