Do you print a copy of your source code?

[Arcadio]

Do you print a copy of your source code for review? I've been doing that since college. Reading source code on paper somehow lets me find problems that otherwise I would've missed by reading the code on a computer monitor.

 

[DaveSimmons]

I used to, but I've been coding for so long now that I don't need to any more.

 

[BrightCandle]

I also used to but I think these days reviews have evolved and now you can do them with tools like crucible, or better yet pair program and get the review line by line as it happens.

 

[KLin]

I also used to but I think these days reviews have evolved and now you can do them with tools like crucible, or better yet pair program and get the review line by line as it happens.

At my job, We do paired review of code on github before deploying. github makes it easy to review code that was added and removed.

 

[Markbnj]

No we use collaboration tools. I don't really print anything anymore.

 

[mosco]

At my last job we used Crucible, and now all our stuff is on Github and we do a review before we push it to the origin.

 

[Snapster]

It's just not feasible to print off code for anything larger than the simple bank account programs that I used to do for my assessments in high school, come to think of it I haven't printed off since then!

If you are needing to print off code to find problems, perhaps you should consider unit tests, or better yet TDD to help you.

 

[degibson]

Every time you print source code, Trogdor burninates a village. A better way to review your own code is by changing it iteratively, by testing it, and by talking about it with others.