97 Things Every Software Architect Should Know

Chapter 73. The Business Versus the Angry Architect

Chad LaVigne is a solutions architect and technical hired gun for Baltimore-based TEKSystems, Inc. He works primarily in the Minneapolis area designing and implementing solutions utilizing Enterprise Java technologies.

—Chad LaVigne

THERE COMES A TIME IN OUR CAREERS as architects when we realize many of the issues we encounter are recurring. Though the project and industry may change, many of the problems are similar. At this point we can draw on our experience to provide many solutions quickly, leaving more time to enjoy the challenging issues. We're confident in our solutions and we deliver as advertised. We have reached homeostasis. This is the perfect time to make a colossal mistake—like deciding you know so much that it's time for you to start talking more than you listen. This poor decision usually comes with a side of cynicism, impatience, and general anger toward inferior minds who dare contradict your superior understanding of all things technical and otherwise.

In its worst form this overconfidence bleeds into the business realm. This is an excellent way to land your career on a list somewhere next to the Black Rhino. The business is our reason for existence. That statement probably hurts a little, but we must not lose sight of that fact. We live to serve them, not vice versa. Listening to and understanding the business that ...