5 ms·
It was required by our ex-manager and director to do so. As we were re-inventing the wheel in any application. If you're a fully hands-on manager you should und
by zldkz5 8y ago
It was required by our ex-manager and director to do so. As we were re-inventing the wheel in any application. If you're a fully hands-on manager you should understand the value of having strong common components that can be plugged in an out.
If you don't think so, just use a plain language without any framework, module, library or third party component and let's see who target the release date first.
We are paid not to build beautiful or robust software, but, first, to deliver faster and without headache. Decoupling stuff and avoid redundancy is a huge benefit and we experienced it dropping down the delivery time by at least 20%.
- navinsylvester 8y agoYou are missing the point here. No one is doubting the usefulness of reusable code or common components. Its about developers spending time on what they think needs to be refactored due to the engineering itch on an already functional and maintainable code. Most times by doing it they can be introducing instability to the whole system. In a larger code base with handful of engineers and teams it becomes a bottleneck to make quick changes since it can break others stuff so too much interaction and policy around it and so forth.