If you aren’t familiar with the Widgets of Wisdom feature, see the explanation and disclaimer here.
- Carry?a model at all times to express?your understanding to others.
- Look for patterns in all systems at all levels. Seeing them is the very essence of insight.
- At the application level, architecture and design are synonymous.
- “BizTalk is overkill” is a typically overheard comment of Drive by Architecture.
- Developers would never prescribe BizTalk or a TIBCO or any other message bus system. That type of decision is typical of a CTO or someone who reports directly to one. These are strategic decisions.
“I think that, generally, if you’re looking at something like BizTalk, you’re probably looking at somebody, a directory port of a CIO or a CTO, I would say.” — Roger Session - “Anything that is architecture and is specific to a particular technology is kind of an oxymoron.” — Roger Sessions
- Good design allows for emergent functionality, which we can also think of as purposeful evolution.
- The Open/Close principle doesn’t mean you can’t recompile. — Allan Shalloway
- Fewer keystrokes != Elegant Code. Damn it! — Dave Starr 🙂
- Architectural decisions are those that will kill your business if they are wrong.
- To introduce a new technology into a system, have the entire team immerse in an architectural spike, then estimate.
- Schedule riskiest work first. Try prioritizing a backlog by risk.
- The work of a developer is to uncover complexity, the work of an architect is to simplify it.
- A legacy system is one that is already making money.
- ?The Winchester House in?San Jose?is the perfect example of following a vision without a plan.?