Coding revolution, was: Seeking: IBM Coding Forms

I've seen that. I'm not sure the folks who own it would be happy if I invoked their corporate name (it was an internal tool), but that's exactly what they built: a system that took flow charts and converted them to code. The code was nearly impossible to maintain outside the tool environment, and awkward to maintain within it. -- Ian ________________________________________ From: cctalk-bounces at classiccmp.org [cctalk-bounces at classiccmp.org] On Behalf Of Charlie Carothers [csquared3 at tx.rr.com] Sent: Saturday, February 12, 2011 5:58 PM To: On-Topic Posts Only Subject: OT: Coding revolution, was: Seeking: IBM Coding Forms On 2/10/2011 7:48 PM, Fred Cisin wrote: Something along those lines has actually occurred to me too. I keep thinking there should be *something* that could be done to revolutionize the way software is created. I'm pretty convinced the way it's currently done is not the answer. Though I still really enjoy writing C code, and though I'm careful to try to create easily understandable and maintainable code, I always seem to finish projects with the uneasy feeling that it could have been done better, maybe a lot better. BTW, I reject the idea that OO is the answer. I think when I was younger I didn't feel that way; I was just happy that the blooming thing worked! Maybe there's a penalty for spending too many years doing too many projects - you start to get all philosophical about the process... Later, Charlie C.