Architect vs. developer

A software developer knows how to (and will be eager to) generalize things – for example using a list instead of a single item or a generic type or method instead of a specific one – enabling more scenarios with supposedly minimal amount of initial supplemental work, and with little or no performance penalties.

A software architect knows how much to (although may not be eager to) cut the developer’s wings and ensure that both the initial and assumed maintenance budgets would still fit, while the project remains scalable and its code stays easy to be adapted upon the usually unavoidable future change requests.

(When the architect is also developer strange things may happen.)

Advertisements

About Sorin Dolha

My passion is software development, but I also like physics.
This entry was posted in Architecture, Miscellaneous and tagged , , , , , . Bookmark the permalink.

Add 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