We have all seen software architects with their ambitious projects, starting out with grand visions, ending up as costly lessons in what not to do, leaving behind the ruins of promising paradigms, technologies, tools, and careers. But why do software architecture approaches sometimes hurt instead of providing value? Why has “software architect” become a negative term for some people? And what can we do to improve our own work? This presentation presents some of the most common software architecture’s pitfalls that ensure you will come up with a disaster, and discusses how they can be avoided.