daily-email: add 2023-10-05
Some solutions are good enough
This commit is contained in:
parent
223daa2ee9
commit
a85943fd2e
20
src/content/daily-email/2023-10-05.md
Normal file
20
src/content/daily-email/2023-10-05.md
Normal file
|
@ -0,0 +1,20 @@
|
|||
---
|
||||
title: >
|
||||
Some solutions are good enough
|
||||
pubDate: 2023-10-05
|
||||
permalink: >
|
||||
archive/2023/10/05/some-solutions-are-good-enough
|
||||
tags:
|
||||
- software-development
|
||||
- technical-debt
|
||||
---
|
||||
|
||||
Once you have a passing test and you're confident your code works as expected, what do you do next?
|
||||
|
||||
Do you keep refactoring and changing it, or is it good enough?
|
||||
|
||||
Do you need to extract additional classes and methods now, or as the test is passing, do you move on to the next task?
|
||||
|
||||
The main objective is to ship the change and for it to provide value to users, not to have a perfect or "gold-plated" solution.
|
||||
|
||||
Once it's shipped, because you have tests, you can confidently refactor it in the future.
|
Loading…
Reference in a new issue