I'm curious if anyone has tried anything like this before? I'd love some guidance or thoughts.
I'm curious if anyone has tried anything like this before? I'd love some guidance or thoughts.
This is proving quite hard to articulate as I try to find a way to visualize it.
To me...
Thoughts are like threads to follow and your wall is faceted shell. Each of these facets carries a kind of gravity which pulls on your thread.
Facets you have accepted without understanding appear solid, a barrier. When you run into one you have hit the wall.
Facets where you have no concept are wide open and you're free to follow your thread, but you risk finding yourself adrift with no reference asking for your thread to become tangled.
Facets where you have greater understanding are revealed to be a lattice, full of gaps to thread through and continue exploring.
You don't "leave" the shell, there's always another layer that might be completely new or something you've passed through many times before.
Imagination/discovery is the act of continually finding the gaps.
---
Personally, I've always done a lot of visualizing. As an adult I've come to recognize close similarities to what I do in the visualization techniques of Stoicism and general thought experiments.
One exercise I find quite useful is to avoid resorting to references for things I don't understand, to turn first toward visualizing how to create whatever it is that's puzzling me - to "search for the gaps" and see where I end up.
Unfortunately, I'm in DC, but with a little luck I'll end up out there eventually. I've visited several times and love it.
The real question is: how much benefit does having a strong and well exercised imagination have for a technical career? (I assume it's very useful for artists).
I've found that software development gets a large boost. The more of the design you can hold in your head on once, the better the coder is able to anticipate the consequences of their decisions. When debugging, the programmer is able to see the entire state of the application that must have predicated it, experiment with a range of fixes, all before writing any code.
I love this quote from The Tao of Programming[1]: "Sometimes there are difficult problems. I see them coming, I slow down, I watch silently. Then I change a single line of code and the difficulties vanish like puffs of idle smoke."
[1] http://www.canonical.org/~kragen/tao-of-programming.html
Tesla mentions that he would apply a small pressure to his eyes, which would then cause geometric shapes to appear and strange patterns to develop. The patterns put him in a different mindset whenever he saw them.
Reading that truly hit me hard, since I did that while I was a kid. I didn't use it for any purpose though... I just thought it looked badass.
Thanks for the tips.