2020-12-08 01:00:00 +0100
2022-01-17 10:55:00 +0100
Debugging the self as if it was a malfunctioning software.
Self debugging consists in the process of sitting down, forgetting about everything else, and debugging yourself as if you were a buggy program. The aim is trying to find out what is going on at a deeper level, without ending up throwing away, repressing, or wrongly addressing the core of some personal issue.
- Switch off everything, distraction included
- Loosen the self for a few minutes, getting ready to stay focused for a long time
- Pinpoint a problem, hence try to identify the source of stress or pain, define its extension and influence
- Start the very debugging process:
- identify the source of the problem
- identify its effects
- imagine how would it be to live without it
- think about a possible resolution
- Try to come up with a solution
- think if there may be other solutions
- reflect on the applicability of those solutions
- Take a few other minutes tinkering about the conclusion you got to and appreciate what’s been achieved. Not much has been achieved? Start a new debug
A great [[Loops|habit]] would be to perform self debugging even when there is nothing relevant bothering or pressing us. Addressing the cause of some suffering while not suffering for it could open a new, brighter and helpful new perspective on a possible solution — or, to stay in the Computer Sciences vocabulary, a possible fix.