How well you understand the feature

[rakibhasanbd4723]

How big the influence it has on the rest of the system
When asking yourself such questions many doubts may arise. You might want to mitigate the risk of implementing the feature incorrectly by taking small implementation steps – write small chunks of code and verify if they meet requirements you form along the way.

You may revalidate requirements multiple times when working. This play along with baby steps approach nicely – you write test, write the simplest implementation, refactor and validate your bulgaria mobile number understanding of the feature before writing a new test or changing some existing one. You constantly put your understanding in question and thus make yourself confident that you’re doing the right job.

Of course in every point of such routine you want to have at most one failing test at the time, this also gives you confidence that you can quickly rollback to previously “working” version of the code.

That said having many test cases and implement the feature by many careful tiny steps should increase your confidence in the codebase. I believe this is a huge gain but there are of course situations when you want to make bigger, more courage steps to achieve better efficiency. It is always about finding a good balance.

Design influence
When starting implementing object behavior you need to make some decisions at the beginning: