News for hackers. Stuff that matters.

A comment on Things Every Software Architect Should Know.

Re:Things Every Software Architect Should Know by swombat on Wednesday February 18, 2009 @05:16AM (#485579)
There are no such thing as "best practices". What's "best" always depends on circumstances.

As such, this is perhaps useful as a list of advice to software architects (basically senior senior developers, in my experience), but only with a huge disclaimer that you must figure out for yourself which bits to apply in your current circumstances.

Why is that disclaimer always missing from list of best practices, even when those lists (like this one) contain self-contradictory examples?

[ Parent | on HN ]
Re:Things Every Software Architect Should Know by kailashbadu on Wednesday February 18, 2009 @01:06PM (#486041)
Agreed.

The key is to avoid slavishly following a rule. You should not shy away from breaking a rule, provided you have good reasons for the violation. First learn what the good rules are (as applicable in majority of cases) and then learn when to break them. The best practices are not supposed to be carried over verbatim into every development project.

[ Parent | on HN ]