170 karma · joined September 14, 2011
The main theoretical idea behind mitochondrial dysfunction is that it is a root cause of many mental health issues : depression, bipolar syndrome, migraine, alzheimer (aka type 3 diabete)... even schizophrenia. And the reason given is you have those neurone networks with impaired mitiochondria that are over or under excitable. These are not dead neurone so it is reversible if you can bring back healthy mitochondria... Part of it is done through mitophagy and mitogenesis induced by fasting/ keto therapy.
- https://www.youtube.com/watch?v=Y6iJMDhLmLc
Anyway in his book (or podcasts) there are many anecdotal but nevertheless fascinating cases of hopeless patients in total remission after a couple of months on keto therapy. It seems a lot of research is underway as well
BTW keto (fast mimicking) diet was invited in the 20s in the Mayo clinic to cure epileptic children. I encourage people to have a look at the fascinating "Brain Energy" book from Chris Palmer (or watch him on youtube) to see what's underneath it and how metabolism and brain efficiency are linked
But I am sceptical this can work without knowing and practicing good design principles (SOLID) independently from tests !
However I believe tests are super important for refactoring, wether the design is good or not. My 2 cents : if the design is bad, (spaghetti and all) tests should be done more at the functional level, when your confident design is getting good then rely more on unit test
See Chris Palmer book : "Brain Energy" or Bikman's : "What makes Us Sick" or Gundry the "Keto Code"... All saying the same thing although with different perspectives. Yes the Brain is just another organ and we're starting to discover ways to trigger self healing processes which can leverage and/or take over the common chemical oriented cures mimicking neurotransmitters...
It started 100 years ago at the Mayo clinic were they cured epileptic children with strict keto diet. Quit fascinating !
On the other hand blowing up the pipe means giving up on :
1. blackmailing the europeans if they don't comply to some demands. 2. A huge revenue - because BTW there's no way it can be repaired.
So I don't think contractual ramifications weighs much in that context
Nevertheless I strongly believe in the presumption of innocence, even outside of court, as a general moral rule we owe to others.
Outrageous might of been a little strong though :)
Also :
+ if it was holidays or a child he wouldn't have left in a rush : those departure should arguably be prepared in advance
+ "Technological details" are very vague and sounds like something he overheard but didn't understand or know how to use.
+ the throwaway account means nothing and could very well plead in his favour : he's not sure he wants to spend time attacking his company so he stays anonymous before taking a rushed decision.
+ not checking his email is consistent with not having the dongle !
While i'm at it I'll add that the main reason SRP is so important is because it limits combinatorial explosions of state, so you can keep control, test and reason about it - incidentally the main idea behind the success of React.js
Good article nevertheless.
For write operations (aka user interaction) I use a combination of solnic gem (Virtus) with ActiveModel that way I remove a s*t load of responsibilities from AR and the controller : - params management (and strong params) - validations - nested associations - callbacks - And all the context management (like user vs admin...)
That way I only mildly part from the rails way and yet have a good separation of concern. Actually ActiveModel is used by ActiveRecord so having a form object relying on it is still very much rails compliant. The refactoring is minor (no hexagonal stuff) and the level of indirection very low.
Add to the mixture charismatic personalities like R. Feldman and E. Czaplisky and this could be the answer.