3 ms·
>If you do this before you understand EXACTLY what you need, you're going to be wrong. The main problem with this is culture imo. I agree 100%, but it is so ha
by goostavos 6y ago
>If you do this before you understand EXACTLY what you need, you're going to be wrong.
The main problem with this is culture imo. I agree 100%, but it is so hard to fight against the idea that "real engineering" or being a "good developer" means tiers of abstraction.
To me, being a good developer actually means understanding what your operating parameters are, and then writing the smallest amount of code that satisfies the business requirement. Sometimes (a lot of times!) this DOES mean you have to go back and refactor or completely throw away code. By _design_ you chose to only solve the immediate problem. However, culturally, this is seen as a failure rather than a success.