|
|
|
|
|
|
by ronocod
3480 days ago
|
|
|
I'm not sold on the whole "code quality" vs "getting things done" mentality here. I think there are diminishing returns in reducing technical debt and keeping a high quality codebase, but the point of doing it that you can maintain a sustained, relatively high "getting things done" rate over the project's lifetime. There are times where you should implement something in a quick and easy way, but if code is going to be present and important for a long time then going the extra mile usually pays off. |
|
|
https://vuejs.org/v2/guide/comparison.html
Based on above, I don't think the dichotomy you pose is applicable in this comparative case.