Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In a similar vein:

Don't think to teach, teach to think.

Don't think to implement, implement to think.

(Writing is less formal than coding, so there can still be flaws, ambiguities and imprecisions resident in your revised writing, but once you turn things into code, it will turn out to be taken to another level of clarity and precision needed.)



I love the way you phrased this, I wrote a book entitled Creative Doing and it's really all about how doing and thinking are part of a loop! Everything is just a snapshot into the creative process and each person's larger body of work.


>Don't think to implement, implement to think.

No matter how much I plan out the process/code, once I actually start coding I think of new edge cases, issues, and often better solutions.


Can this all be summed up to "JUST DO IT", since were all saying the learning and revision comes after the work we should all just stop procrastinating and "JUST DO IT" already.


>Don't think to implement, implement to think.

Analysis through synthesis. It's the only way for me.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: