Home > technical > Intimately Bound

Intimately Bound

Out of the bazillions of definitions of “software architecture” out in the wild, my favorite is:

the initial set of decisions that are costly to change downstream“.

It’s my fave because it encompasses the “whole” product development ecosystem and not just the structure and behavior of  the product itself. Here are some example decisions that come to mind:

Once your production code gets intimately bound with the set of items on the list, there comes a point of no return on the project timeline where changing any of them is pragmatically impossible. Once this mysterious time threshold is crossed, changing the product source code may be easier than changing anything else on the list.

PONR

Got any other items to add to the list?

  1. April 24, 2013 at 9:09 am

    Persistence – file system, RDBMS, NoSQL, etc. etc.

    • April 24, 2013 at 9:41 am

      A HUGE error of omission! Thanks Gene.

      • April 24, 2013 at 10:03 am

        No problem…it’s great to see advocacy for a holistic approach to architecture.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: