Comments on: Simplest versus first thing that could possibly work http://lostechies.com/jimmybogard/2009/06/11/simplest-versus-first-thing-that-could-possibly-work/ Strong opinions, weakly held Wed, 19 Jun 2013 17:39:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Ryan Riley http://lostechies.com/jimmybogard/2009/06/11/simplest-versus-first-thing-that-could-possibly-work/#comment-1589 Ryan Riley Thu, 11 Jun 2009 14:58:48 +0000 /blogs/jimmy_bogard/archive/2009/06/10/simplest-versus-first-thing-that-could-possibly-work.aspx#comment-1589 (Sorry if this gets duplicated, something weird happened when I submitted the first time...) I absolutely agree. This is the same problem with YAGNI. Especially when you do, in fact, know you are going to need it yet write it as though you didn't and then have to almost rip out the original implementation to get it to work later. It's a nice phrase to emphasize the point, but it goes a bit overboard. Everyone wants a single definition of "simple", but it just doesn't exist. You have to be thoughtful as well if you want to ensure quality throughout the entire system. Again, well said! (Sorry if this gets duplicated, something weird happened when I submitted the first time…)

I absolutely agree. This is the same problem with YAGNI. Especially when you do, in fact, know you are going to need it yet write it as though you didn’t and then have to almost rip out the original implementation to get it to work later. It’s a nice phrase to emphasize the point, but it goes a bit overboard.

Everyone wants a single definition of “simple”, but it just doesn’t exist. You have to be thoughtful as well if you want to ensure quality throughout the entire system. Again, well said!

]]> By: Hernan Garcia http://lostechies.com/jimmybogard/2009/06/11/simplest-versus-first-thing-that-could-possibly-work/#comment-1588 Hernan Garcia Thu, 11 Jun 2009 11:10:22 +0000 /blogs/jimmy_bogard/archive/2009/06/10/simplest-versus-first-thing-that-could-possibly-work.aspx#comment-1588 Excellent post. I will also add that code reviews (even reviewing your own code after a day or two) have a great impact in the quality of the design. While you are working in a problem you may get mentally fixated on one or two solutions, and never see an alternative. Changing context (working on something else, or go to sleep) goes a long way in brake that "writers block". Excellent post. I will also add that code reviews (even reviewing your own code after a day or two) have a great impact in the quality of the design. While you are working in a problem you may get mentally fixated on one or two solutions, and never see an alternative.
Changing context (working on something else, or go to sleep) goes a long way in brake that “writers block”.

]]> By: Tim Scott http://lostechies.com/jimmybogard/2009/06/11/simplest-versus-first-thing-that-could-possibly-work/#comment-1587 Tim Scott Thu, 11 Jun 2009 03:20:29 +0000 /blogs/jimmy_bogard/archive/2009/06/10/simplest-versus-first-thing-that-could-possibly-work.aspx#comment-1587 Well put. We go wrong here when we base our decision on the easy->hard continuum rather than the simple->complex continuum. The easiest path rarely leads to the simplest solution. Well put. We go wrong here when we base our decision on the easy->hard continuum rather than the simple->complex continuum. The easiest path rarely leads to the simplest solution.

]]>