When I code, I have a habit of wanting to get it done. To see it work. Corey pointed this out and he’s right. Unknowingly, this habit affects the way I code and limits how fast I can grow as a programmer because I’m likely do the things that I know how to do. I may venture out of my comfort zone but I would quickly retreat on first sign of problem. This is totally okay. When I’m paid to get things done, it’s not right for me to disappear into the la-la programming land to explore and learn. And when the deadline is tight, I’m forced to cut corners (partly because I am not skilled enough) to get it done. But just understand, with this habit, little programming skills are developed.
At the retreat, the purpose of coding is not about getting it done. It’s about putting aside this attitude and just code and be with it. It’s a different space to be in. It’s like going back to my kindergarten days playing in the sandbox. The play was one continuous stream of one play idea to another. That’s what I feel at the retreat. A coding idea leads to another idea for me to explore and practice. Every now and then, I catch myself wanting to get it done. I have to pull back and say to myself, “Just code Thanou.”
The space is there for me to challenge my programming skills without judgment. It is for me to develop new skills through coding on an idea to absurdity (no if-statement in the code) or not and so forth. It’s about bringing back the curiosity of wanting to experience the various solution paths as fully as possible. According to Corey, and I agree, the skills I learn will benefit the “get it done” space in forms of cleaner code and less corners cut. I’ll get it done better!
I’m still processing my experience. It was my first taste to a path to become a better programmer. It’s a journey. It’s about changing attitude and view. I’ve learn to create a space for me to be with the code which in turn, when I need to get things done, I would do it more skillfully.