Comments on: Action-Oriented Programming

By: JTtheGeek

JTtheGeek — Thu, 17 Jul 2008 00:19:18 +0000

That's freaking awesome lol. I can't even begin to gripe about how much time is wasted over analyzing the situation, stalling development, finally figuring out a slightly modified approach, that we would have discovered already if we had just started coding. This isn't to say there isn't a need for good research, design, and architecture, only that there is a balance that we developers usually are way off on

By: Jesse Freeman

Jesse Freeman — Sun, 20 Apr 2008 13:22:31 +0000

I like this term. When I developer I do a little up front thinking about the problem then start working my ideas out in the code. When I get it stable, I go back and see how I can organize it and make it fit into a better design pattern before going to production. I feel I get a lot more done this way, even though I wind up with a little extra throw away code, I can always track my progress through my SVN commits as well as showing my clients/boss something that is always working. There is a lot to be said about getting it done vs perfection.

By: Kyle Hayes

Kyle Hayes — Sun, 16 Mar 2008 14:46:09 +0000

I can totally relate to this. I am one of those people who over-analyzes just about everything. Not to say that it is a bad quality, but it must only be used when it is appropriate.

By: mike

mike — Wed, 12 Mar 2008 17:37:54 +0000

re: 'getting things done' -- yes, exactly!

By: felix

felix — Wed, 12 Mar 2008 17:29:09 +0000

haha - that's great! I'm starting to think that a lot of these frameworks and patterns are a form of procrastination through over-engineering. It's similar to people who spend hours a day reading blogs about 'getting things done'.