|
|
|
|
|
by whstl
895 days ago
|
|
> "Not if you are encapsulating and naming effectively..." When you only have to superficially skim the code, that works. If there are incorrect abstractions, such as logging, transaction logic or manual error handling mixed with "well named function calls", then it is already very problematic even to skim. If you have to debug, it quickly becomes torture. Especially if state is involved and shared between multiple methods or classes. If you have to reimplement the code: you're probably fucked. |
|