Metrics-Driven Development
Everywhere I&#x27;ve worked has been in reactive mode. We never have time to slow down and adjust. Never given any time to work on the infrastructure projects that will give us the tools to do our jobs better in the long run.<p>This looks like the epitome of reactionary development. Plus it doesn&#x27;t lend you any real insight into the &quot;why&quot; of a given problem.<p>In the included example, latency is up on a given method.  Lets say it turns out that particular process calls three different &quot;manager&quot; classes, and has another inline sql query. So, you do the right thing and spend a bunch of time cleaning it up and getting things looking more <i>right</i> (with no help from MDD, since there&#x27;s nothing about development practices in this outline.)<p>Turns out, it wasn&#x27;t the code after all. Someone had designed autocomplete to work off of a sql table, and someone else disabled the job that re-indexed the search column.<p>* Long story short, TDD and BDD give us development tools<p>* MDD appears to give us... help making minor decisions on potential focus areas? Maybe ammunition to tell our PMs what we should work on?<p>Anyone else see what the big draw for this would be?