Oh i see, the point is decoupled code (usually classes) right? I'm currently using modular and doing very fine with tests (without abstraction), so is this like the good OOP way for doing tests (is to create abstraction first)?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Using abstractions allows us to write decoupled code.
Decoupled code is easier to test, thus to refactor and, in the end, to get better over time and not the opposite.
But we have to get into it and experience the frustration of code that get worse over time until we decide to rewrite everything from scratch.
And if we don't change our approach, we don't have any chance that the next rewrite will be better.
I never get tired of recommending to watch this masterpiece: vimeo.com/78898380
Oh i see, the point is decoupled code (usually classes) right? I'm currently using modular and doing very fine with tests (without abstraction), so is this like the good OOP way for doing tests (is to create abstraction first)?