Achieving Efficiency and Simplicity in Code Design
A fast test suite is crucial to test many ideas for the same problem.
If we want to deviate from the TDD Mantra’s first step, we should start with an Acceptance test at the system’s outer edge. This test describes when the user stops using the product. An Acceptance test doesn’t need to detail a user’s click in a specific view.
Flow is a state of mind where information processing happens, and some writers refer to it as “being in the zone.”
For programmers, being in the Flow means being able to think about an idea and translate it into code. To achieve this state, one needs to have a clear understanding of the problem and its context. Every change in an application is a chance to write code that doesn’t fit into the existing structure.
Every attempt to change implies rearranging the current knowledge about the problem to fit the new and old behavior. Design and architecture require a lot of effort because they guarantee to have changeable code in the future.
Good design should always move towards simplification.
