Correct. The ones I randomly picked don&#x27;t cover plasticity. How does one measure (and convey) software plasticity to other [non-technical] shareholders?<p>Tech: &quot;It&#x27;s going to take x amount of time to refactor so that the software can easily change in the future&quot;
BusDev: &quot;What if we don&#x27;t need it to change [like that] in the future?&quot;<p>How does Tech and BusDev objectively measure the software plasticity if it can&#x27;t be measured until change must occur? &quot;Our software is X plastic&quot; means what? &quot;This change will take 1 day instead of a 1 week because we made our software plastic.&quot; What if you pre-optimzied plasticity and YAGNI&#x27;ed wasting precious time and resources. This is where things get real dicey... trying to objectively measure the importance and value of clean code. WE, techs, understand it and can feel it while trying to implement new features and changes but those that don&#x27;t touch or understand code can&#x27;t.<p>ADD: How do we determine the code is clean (and refactored) enough (but not too much)? &quot;Everything should be made as simple as possible, but not simpler.&quot; &quot;Do as much is needed but nothing more&quot;?