Lesson 132 - Architecture By Implication AntiPattern

What happens when you create an application without thinking about an architecture and simply just :start coding"? Is it really necessary to engage an architect for this new application? Do we even need an architecture? This is what the “Architecture by Implication” anti-pattern is all about. In too many cases a software architecture is just “implied”, usually resulting is catastrophic failures. In this lesson Mark Richards describes what this anti-pattern is all about, and what can happen if you fall into this trap. Mark also describes the scenarios when, in fact, you don’t need to think about architecture.

Reference Links:

[morgadoapi]

Thanks a lot for your Architecture Monday's videos! Because of the length I never have an excuse not to watch them. Thanks again!

[abhishek]

That awkward moment when an Architecture lesson feels like a meme review video

[neko]

Not the best analogy. Software is much easier to change than houses