>>can make or brake any architecture. HA! I wanted to see "break" (as in fracture) any architecture, but I think "brake" (as in device for arresting or preve

>>can make or brake any architecture. HA! I wanted to see "break" (as in fracture) any architecture, but I think "brake" (as in device for arresting or preventing the motion) works even better here — the details of the code increase 'friction' in the machine and prevent it's efficient motion... Overall, I quite agree; the devil is in the details, and those details can swamp the 'architectural' decisions. Best to get both mostly right vs one 'perfect' and be ruined by overlooking the other.