Developers are endlessly fascinated by how things work. Each time they look at the system, they wonder - how was this done? Why doesn't this work? How can I improve this? They want to dismantle it to see how it "breathes". This applies to software, but also to cars, radios, lamps, lifts and, if you are really happy, a dead insect. But what if the problem is in the operating system, or in other words, between the chair and the keyboard - in the programming mind ?! Mind, like any other program, when it's in trouble, reaches out to the outside world and says to the outside world: "What you presented, caused the problem, do something different if you want to continue!". It can not fix itself. Of course, we can train computers to learn and adjust themselves to a certain extent, but there are always situations where the outside presence of developers is needed. Mind also needs to be corrected. Mind is doing self-corrections and learning, but it has inherent limitations. As Einstein said, "you can not solve the problem with the same level of consciousness that created it." Something beyond your mind is needed for the mind to really be refactored - which is not surprising to us since this is only the area where a parent can "kill" children without interference of the law (compiler). 7th on the top session list. 9th most visited lecture of the conference.