Comments on: Writes large correct programs http://www.johndcook.com/blog/2008/09/19/writes-large-correct-programs/ The blog of John D. Cook Sat, 31 Jul 2010 07:45:27 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: NuCode http://www.johndcook.com/blog/2008/09/19/writes-large-correct-programs/comment-page-1/#comment-30566 NuCode Mon, 11 Jan 2010 10:01:36 +0000 http://www.johndcook.com/blog/?p=401#comment-30566 Exactly to the point. The biggest problem probably lies in the fact that amateurs who's written 100-liners has absolutely no idea of the design, architectural requirements for such a vast project, and thus fail, as the backend, the design, is not robust, and easy enough to manage. I wonder how complex a 100k liner would be, biggest i've tackled so far is just around 30k. Exactly to the point. The biggest problem probably lies in the fact that amateurs who’s written 100-liners has absolutely no idea of the design, architectural requirements for such a vast project, and thus fail, as the backend, the design, is not robust, and easy enough to manage.

I wonder how complex a 100k liner would be, biggest i’ve tackled so far is just around 30k.

]]> By: Bastien koert http://www.johndcook.com/blog/2008/09/19/writes-large-correct-programs/comment-page-1/#comment-29513 Bastien koert Thu, 24 Dec 2009 04:23:50 +0000 http://www.johndcook.com/blog/?p=401#comment-29513 John, I've read two of your posts regarding programming, this one obviously an the programming productivity vs pay article. Both were enjoyable and in my experience , entirely correct. The good programmers write fewer lines of better code. They also plan better solutions and understand the ramifications of those design decisions better that less capable programmers. I work with both, one is great fun to work with, the less capable is far less fun. We then spend too much rime correcting errors and tracking down bugs. John,

I’ve read two of your posts regarding programming, this one obviously an the programming productivity vs pay article. Both were enjoyable and in my experience , entirely correct. The good programmers write fewer lines of better code. They also plan better solutions and understand the ramifications of those design decisions better that less capable programmers. I work with both, one is great fun to work with, the less capable is far less fun. We then spend too much rime correcting errors and tracking down bugs.

]]> By: Ezrad Lionel http://www.johndcook.com/blog/2008/09/19/writes-large-correct-programs/comment-page-1/#comment-9973 Ezrad Lionel Thu, 20 Nov 2008 05:15:32 +0000 http://www.johndcook.com/blog/?p=401#comment-9973 I'm having so much fun browsing around your thoughts. I can remember my old days programming in basic and being disappointed when my code was only a few kb and I also remember quite distinctly when my programs started going over basics limits and scrambling for 3rd party tools to extend memory. Thank God for Qbasic. I've been programming for about 10 years now and alot of your logic seemed intrinsic to me. It made alot of my Computer Science classes extremely boring but it was pretty cool to learn different techniques to create more efficient code. I think your analysis.. well your paradigm effectively illustrates the gap that exists between small programs and large ones. I'm just putting the finishing touches on my web toolkit and your words are fresh in my ears. I've written larger programs before but I went all out on this one. I've never done so much unit testing before and I'm starting to suspect that I'm paranoid. It's so crazy how the implementation of some seemingly benign piece of code can complicate a project. The most important thing I've learnt however, is that shortcuts are to my detriment. Knowing exactly why certain systems create errors is more rewarding than patching it up. I’m having so much fun browsing around your thoughts. I can remember my old days programming in basic and being disappointed when my code was only a few kb and I also remember quite distinctly when my programs started going over basics limits and scrambling for 3rd party tools to extend memory. Thank God for Qbasic.

I’ve been programming for about 10 years now and alot of your logic seemed intrinsic to me. It made alot of my Computer Science classes extremely boring but it was pretty cool to learn different techniques to create more efficient code. I think your analysis.. well your paradigm effectively illustrates the gap that exists between small programs and large ones. I’m just putting the finishing touches on my web toolkit and your words are fresh in my ears.

I’ve written larger programs before but I went all out on this one. I’ve never done so much unit testing before and I’m starting to suspect that I’m paranoid. It’s so crazy how the implementation of some seemingly benign piece of code can complicate a project. The most important thing I’ve learnt however, is that shortcuts are to my detriment. Knowing exactly why certain systems create errors is more rewarding than patching it up.

]]>