Skip to main content

16. Don’t try to solve every problem

Don’t try to solve every problem

Absolutely do not try to solve every problem you can think of before you really have to.

This ties in with the whole test-driven development thing. The test defines the task you need to do, and you only do that task.

If there is a problem that comes up in the project or a bug, then you write a test for that bug, and you write code that solves just that test.

To read this post you'll need to become a member. Members help us fund our work to ensure we can stick around long-term.

See our plans (Opens in a new window)

Topic Yellow

0 comments

Would you like to be the first to write a comment?
Become a member of Out of the Software Crisis and start the conversation.
Become a member