3 ms·
What kind of business-relevant change are you referring to here? I don't think the compiler with the error messages makes a difference when the business is piv
by gls2ro 3y ago
What kind of business-relevant change are you referring to here?
I don't think the compiler with the error messages makes a difference when the business is pivoting between features, when they ask to add a new field to various forms, to generate new reports or add new emails in various points of the work flow. Or change the emails from one point to another point. Or add password less. Or just switch the external provider of an API from an important flow because there is a better deal elsewhere.
I am not saying static typing does not provide speed or flexibility, but I just wanted to say that business-relevant change has more to do with features than code.
- gavmor 3y ago> business-relevant change has more to do with features than code I cannot comprehend this. It's like saying "Health has more to do with organs than cells." Organs comprise features. Features comprise code. To change the feature, one must change the code. If the code is not business-relevant, delete it. It's a liability. We are not artists. If the code is well-written, the compiler errors will echo the business' failings.