Comments on: The editing pass http://michael-mccracken.net/2007/10/the-editing-pass/ This is a weblog Sun, 25 Mar 2012 04:06:25 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: 0xDECAFBAD accumulator » Blog Archive » Beautiful Code http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-361 0xDECAFBAD accumulator » Blog Archive » Beautiful Code Wed, 05 Dec 2007 07:58:40 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-361 <p>[...] Michael McCracken: “Once you get a piece of code to the point where you believe it works - it’s passing its tests - go back over it and edit it. That is, go back and edit it for clarity, flow, and style. Just as if it were an essay.“ [...]</p> [...] Michael McCracken: “Once you get a piece of code to the point where you believe it works – it’s passing its tests – go back over it and edit it. That is, go back and edit it for clarity, flow, and style. Just as if it were an essay.“ [...]

]]> By: tima thinking outloud. http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-365 tima thinking outloud. Fri, 12 Oct 2007 03:16:34 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-365 <p><strong>The Editing Pass...</strong></p> <p>Edit code just as if it were an essay says Michael McCraken....</p> The Editing Pass…

Edit code just as if it were an essay says Michael McCraken….

]]> By: Clever::Tagline::Pending » Treat code like prose http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-367 Clever::Tagline::Pending » Treat code like prose Thu, 11 Oct 2007 01:59:04 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-367 <p>[...] this explanation of refactoring by Michael O [...]</p> [...] this explanation of refactoring by Michael O [...]

]]> By: J. B. Rainsberger http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-359 J. B. Rainsberger Thu, 11 Oct 2007 00:33:02 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-359 <p>I just read this and it seems to describe refactoring almost exactly. I don't know why I hadn't thought of it before. Excellent.</p> I just read this and it seems to describe refactoring almost exactly. I don’t know why I hadn’t thought of it before. Excellent.

]]> By: Infovore » links for 2007-10-10 http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-366 Infovore » links for 2007-10-10 Wed, 10 Oct 2007 23:21:21 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-366 <p>[...] michael-mccracken.net » The editing pass “Anything worth writing is worth re-writing. This applies to code as well as prose.” (tags: code programming editing style refactoring) [...]</p> [...] michael-mccracken.net » The editing pass “Anything worth writing is worth re-writing. This applies to code as well as prose.” (tags: code programming editing style refactoring) [...]

]]> By: mark http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-368 mark Wed, 10 Oct 2007 16:21:13 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-368 <p>Don Knuth said something similar in his book Literate Programming.</p> Don Knuth said something similar in his book Literate Programming.

]]> By: Alf Watt http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-356 Alf Watt Wed, 10 Oct 2007 15:05:48 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-356 <p>I've long though that the term 'Software Engineering' is a misnomer. It's really 'Writing Software', code is in the end written for other humans to read, the compiler doesn't care what you name your symbols and the processor really doesn't care what your code looks like. Since software is written to be read, the traditional drafting, editing, review and publication model makes much more sense and is much closer to the actual practice than any traditional engineering discipline.</p> I’ve long though that the term ‘Software Engineering’ is a misnomer. It’s really ‘Writing Software’, code is in the end written for other humans to read, the compiler doesn’t care what you name your symbols and the processor really doesn’t care what your code looks like. Since software is written to be read, the traditional drafting, editing, review and publication model makes much more sense and is much closer to the actual practice than any traditional engineering discipline.

]]> By: Erik http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-364 Erik Wed, 10 Oct 2007 11:31:43 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-364 <p>Where I work, nothing can be checked in without a code review. The repository is even configured to prevent commits without a code reviewer's name in the commit comment.</p> Where I work, nothing can be checked in without a code review. The repository is even configured to prevent commits without a code reviewer’s name in the commit comment.

]]> By: MacPro.se - Skriv snyggare kod http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-360 MacPro.se - Skriv snyggare kod Wed, 10 Oct 2007 08:18:29 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-360 <p>[...] Läs mer här [...]</p> [...] Läs mer här [...]

]]> By: 0xDECAFBAD » beautiful code http://michael-mccracken.net/2007/10/the-editing-pass/comment-page-1/#comment-355 0xDECAFBAD » beautiful code Wed, 10 Oct 2007 04:59:21 +0000 http://michael-mccracken.net/wp/2007/10/09/the-editing-pass/#comment-355 <p>[...] code Michael McCracken: “Once you get a piece of code to the point where you believe it works - it’s passing [...]</p> [...] code Michael McCracken: “Once you get a piece of code to the point where you believe it works – it’s passing [...]

]]>