|
|
|
|
|
by splicer
5177 days ago
|
|
In the context of software development, I think his idea that we should switch from open mode to closed mode when it's time to implement something is dead wrong. I today I gave a demo of something epic at work that I had developed exclusively on my own time. The way I managed to get myself to spend 30+ hours of my free time producing something for work was by remaining in open mode: i.e. I was playing. |
|
It takes the closed mode to focus on 'divide and conquer' and implementation of the idea as envisioned. This doesn't stop you going back in to Open mode to frequently consider where you are. Judge your work against it's initial goal etc.
If you are perpetually in Open mode you would continually add new features and extend the brief and never implement anything. I've worked with those kinds of people, they are a PITA.... although very creative.
Some people seamlessly switch between open and closed and others are stuck in one or the other.
I personally struggle to get in to the Open mode. After 30 years of disciplined coding, leading teams and divide and conquer my mind is highly specialised. It doesn't mean I'm not creative but it takes me longer to get in to that mode of thinking.