The Old School Manifesto
Mon, 10/11/08 – 22:08 | 2 Comments

As we saw in the last essay, the 80:20 rule seemingly appears in many circumstances. When I was attending college and working as a programmer during the 80’s, there were some commonly accepted tenets that guided our software development processes and behaviors.

Read the full story »
Management

Methodology

Metrics

Quality

Requirements

Home » Design

Good Design is Important

Submitted by Bill Miller on Monday, 25 August 2008 No Comment

I just stumbled upon a blog posting by Chad Myers titled “Good Design is not Subjective.”  It’s hard for me to believe, but apparently this is a controversial subject in the software community today.   The thrust of his position is that a good design is characterised by its ability to easily maintain and enhance while a bad design is characterised by its difficulty to maintain and enhance.  A bad design exhibits characteristics of rigidity, fragility, and immobility.  It’s an interesting article, and it is reminiscent of many of the themes advocated on this blog.  A good design is the essence of agility.   A good developer knows a good design when he sees it.  Read the article.  I’m sure you’ll like it.  The comment thread is interesting as well.

Email This Post Email This Post Print This Post Print This Post
Vote This Post DownVote This Post Up (No Ratings Yet)
Loading ... Loading ...

Related Articles:

  • Don’t Code Yourself into a Corner
  • Simple by Design

  • Leave a comment!

    Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

    Be nice. Keep it clean. Stay on topic. No spam.

    You can use these tags:
    <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

    This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.