|The stupid question is the question not asked|
I once implemented a Turing machine in production code because it was the correct and cost-effective solution
I think it is all too easy to forget how much practical experience it requires to be able to reach that determination.
Just as theory without practice--real-world practical application--is just so much hot air; so you can practice as much as you like, but without the theory to back you up and allow you to choose the right starting point, the likely outcome of your practice is that you will become very good at doing the wrong thing.
From previous discussion, I think that you are likely in tune with the theory and practice of 'balance in all things'.
In programming as in life, balance is everything, and inbalance--the over concentration on one aspect to the exclusion of others--is the source of most woes.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^4: Worst blog post ever on teaching programming