I hereby offer the "brain weasels are like bad code" analogy up for any other software engineer / giant computer geeks it may help.
(If this does not help you, or you find it offensive, I hope you realize that was not the spirit in which this was intended.)
Credit should also go to nonethefewer for our synchronous spawning of this analogy. I honestly couldn't tell you who thought of it first and I'm willing to bet she couldn't either. That having been said:
All types of brain weasels can be likened to buggy code. When you realize that it's having unwanted, unintended effects in your life, so you try to debug it yourself. After all, you wrote the code your brain runs on, right? ... well, maybe not.
Think about it. As you grew up, your parents, family members, teachers, peers, friends, youth groups, etc all gave you ideas, gave you opinions, gave you advice, demanded that you follow [perhaps arbitrary] rules & commands, gave you homework and often you were told: "listen to X, they are teaching you things." Many of the things they taught you were helpful. Some of the ideas they passed along are not.
Plus, it's not like you could control your literal genetic code, or how that was influenced by your socioeconomic environment, or your psychosocial environment, for that matter. So... you begin to realize, perhaps, this is a bigger endeavor than you thought.
Cruft! Bad ideas! Legacy coding, in other words. It's old, and it's buggy, and you very well might not be able to fix it yourself because this is all legacy code.
Don't be afraid to ask others for bug-fixes and patches. Don't be afraid to consult an expert, like a therapist or a psychiatrist or other psyche-healer or whomever has training in this that you're comfortable bringing it to.
Sometimes when I think of my brain this way, it makes it easier to be compassionate towards myself. "Awww, brain, you're all stuck in a do-while loop," I think. "Have you considered arrays? Pythonic tuples?"
It's okay, brain of mine. You were partially coded way back in 1985; come on, COBOL was cutting edge back then. I'm not getting RID of the programs—nope nope—this is just an upgrade. It'll be as gentle as possible, I promise.
I also like this analogy because ... debugging code is just a thing that has to happen. There's no real value judgment attached: you're not a WORSE programmer because you have to debug your code. In fact, I'd argue that the best programmers debug their code as frequently as required and ask expert advice whenever necessary.
(Plus, it helps me not to smash people's faces in when they say shit like "MOAR WILLPOWER will overcome your clinical depression!" It's like awww, it's like you're secretly a commodore 64, still around! still got your CPU in your keyboard! still demagnetizing tapes because they're stored on top of the tape drive like the manual says to do!)
no subject
(If this does not help you, or you find it offensive, I hope you realize that was not the spirit in which this was intended.)
Credit should also go to
All types of brain weasels can be likened to buggy code. When you realize that it's having unwanted, unintended effects in your life, so you try to debug it yourself. After all, you wrote the code your brain runs on, right? ... well, maybe not.
Think about it. As you grew up, your parents, family members, teachers, peers, friends, youth groups, etc all gave you ideas, gave you opinions, gave you advice, demanded that you follow [perhaps arbitrary] rules & commands, gave you homework and often you were told: "listen to X, they are teaching you things." Many of the things they taught you were helpful. Some of the ideas they passed along are not.
Plus, it's not like you could control your literal genetic code, or how that was influenced by your socioeconomic environment, or your psychosocial environment, for that matter. So... you begin to realize, perhaps, this is a bigger endeavor than you thought.
Cruft! Bad ideas! Legacy coding, in other words. It's old, and it's buggy, and you very well might not be able to fix it yourself because this is all legacy code.
Don't be afraid to ask others for bug-fixes and patches. Don't be afraid to consult an expert, like a therapist or a psychiatrist or other psyche-healer or whomever has training in this that you're comfortable bringing it to.
Sometimes when I think of my brain this way, it makes it easier to be compassionate towards myself. "Awww, brain, you're all stuck in a do-while loop," I think. "Have you considered arrays? Pythonic tuples?"
It's okay, brain of mine. You were partially coded way back in 1985; come on, COBOL was cutting edge back then. I'm not getting RID of the programs—nope nope—this is just an upgrade. It'll be as gentle as possible, I promise.
I also like this analogy because ... debugging code is just a thing that has to happen. There's no real value judgment attached: you're not a WORSE programmer because you have to debug your code. In fact, I'd argue that the best programmers debug their code as frequently as required and ask expert advice whenever necessary.
(Plus, it helps me not to smash people's faces in when they say shit like "MOAR WILLPOWER will overcome your clinical depression!" It's like awww, it's like you're secretly a commodore 64, still around! still got your CPU in your keyboard! still demagnetizing tapes because they're stored on top of the tape drive like the manual says to do!)