You can pretty much just drop that &quot;micro-&quot;.   With very few exceptions, you really shouldn&#x27;t optimize until you have accurate measurements of what is going on.<p>Update: To me, a lot of responses here conflate &quot;optimization&quot; with &quot;design&quot;.   From where I&#x27;m sitting, &quot;optimization&quot; means making adjustments to and existing solution to make it faster.  That has nothing to do with choosing an appropriate language or toolset, and limited amounts to do with overall design.  Yes, sometimes you must project forward a bit, for example knowing you&#x27;ll be able to optimize out exponential behavior with a better data structure, say.<p>But often people do too much, too early, with too little information.