Send your work to review early
I am a fan of exposing half-baked work early to the eyes of my peers.
I will write an example from my programming activity, but the same principle applies to any artifacts including writing essays or designing of physical products.
At my job, I recently took on a programing assignment that requires me to learn new piece of technology and code-base. We peer-review our code before releasing, and I was expecting that it'd take much longer than typical assignment before I can release it live.
I put my code on review as soon as things barely start working, rather than waiting my solution to be more clean and efficient. Naturally, I get tons of comments from the peers who are experts on the technology and code-base.
It is more efficient and effective to borrow other people's eyes to check your work quickly.
That is what I wanted. The mode of our brain is very different when we are authoring and reviewing, and it is hard to check your own work as you drive the production. It is more efficient and effective to borrow other people's eyes to check your work quickly.
I know my nature. I often get in the mindset that I need to knit every single details right before showing my work to anybody. The problem of this mindset is that I may be locally optimizing while whole direction of the effort is off the point. Exposing the work whether it's a piece of code or thesis is a great way to raise the quality and speed of the work.
All it takes is a courage to expose your imperfect work. It's always humbling and even humiliating sometimes, but the pay-off is big. So, send your work to review early.
Original post: Nov. 5, 2014 | Last updated: Nov. 15, 2014