Stefan Tilkov

We’ve all seen them: 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 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? We’ll look at some of the most common pitfalls that ensure you’ll come up with a disaster, and discuss how they can be avoided.

In general, everybody just wants good things to happen, yet it it’s extremely hard to affect meaningful change, especially in large organizations. This is a lesson many conference attendees learn the hard way: They get “back home” to the mothership after attending a fantastic conference, and find themselves running into brick walls when they suggest the company adopts some of the cool new ideas they learned. In this talk we’ll take a the typical problems, and try to find some patterns on how to overcome them. Spoiler alert: It’s way more related to people and their interests instead of technology.