Solution Architecture Guidance

November 22, 2011 · 1 min read

Here is my general guidance in regards to solutions architecture:

  • Leverage what we have first
  • Gather facts, not opinions when assessing solutions
  • Avoid making early assumptions
  • Prove that issues are real before escalating concerns
  • Present issues or concerns within proper context
  • If prototypes reveal concerns, consider alternative solutions.
This article is part of the GWB Archives. Original Author: Eric Johnson

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.