Writing code for humans
In the previous chapter, we loaded our first data and built our first model to transform it.
With so little code developed in our project, there is no risk of making any confusion or calling the same things with different names, yet these are real concerns in any real project, and they matter so much more than most people think.
Most people believe that when coding, you just write new code, but the reality is that to write one row of new code, you often must go back and check what you have done in a few other places, which means reading tens of rows again and again in existing code.
This becomes truer and more evident the older a project becomes, and the more people become involved in the project.
We have seen in previous chapters that there are some patterns to minimize and keep in check this issue, but remember that size is one dimension of complexity, and we can only do so much to manage it.
Removing duplicated or copied and pasted code is...
