<p>A great quote I recently heard whilst watching a conference talk was "No-one is paying us to do <em>something</em>, but we need to do it to work effectively".</p>
<p>This talk was about decoupling, but the same quote could be re-used for various topics.</p>
<p>A common one is automated tests and test-driven development.</p>
<p><a href="/daily/2025/02/23/line-item">Tests aren't a line item</a> that should be billed for separately and clients and customers just want their software to work.</p>
<p>Generally, they aren't concerned that there are automated tests or whether the tests were written before the code.</p>
<p>If I need to give an estimate, I always include time to write automated tests.</p>
<p>It's part of my software development process.</p>
<p>Whether people know they're paying for me to write automated tests as part or not, I can work more effectively when I have tests and am doing test-driven development.</p>
<p>Both when writing the code, but also if it needs to be <a href="/daily/2024/10/20/test-then-refactor">refactored or changed in the future</a>.</p>
format:full_html
processed:|
<p>A great quote I recently heard whilst watching a conference talk was "No-one is paying us to do <em>something</em>, but we need to do it to work effectively".</p>
<p>This talk was about decoupling, but the same quote could be re-used for various topics.</p>
<p>A common one is automated tests and test-driven development.</p>
<p><a href="/daily/2025/02/23/line-item">Tests aren't a line item</a> that should be billed for separately and clients and customers just want their software to work.</p>
<p>Generally, they aren't concerned that there are automated tests or whether the tests were written before the code.</p>
<p>If I need to give an estimate, I always include time to write automated tests.</p>
<p>It's part of my software development process.</p>
<p>Whether people know they're paying for me to write automated tests as part or not, I can work more effectively when I have tests and am doing test-driven development.</p>