sponsored | Why does the big ball of mud keep happening and how to avoid it
In software development, the dreaded "big ball of mud" is all too familiar – a tangled, unmaintainable codebase that makes everything harder. Modularization? Impossible. Reuse? Too much coupling. Regression bugs? Endless. Simplifying or modernizing the code? Too risky. In this session, we'll explore why so many projects end up as big balls of mud, why it's so hard to avoid, and how we can break this cycle. Also share practical strategies and proven techniques to ensure clean, well-architected software. We’ll also discuss whether microservices really are the solution to this pervasive problem.
Alexander is co-founder and managing director of hello2morrow and CEO of the US subsidiary. He has more than 35 years of project and management experience. In 1993 he founded ootec – a company focused on project services around object-oriented software technology. In March 2000 this company was sold to Valtech group, a French company, and served customers like Siemens, BMW, Thyssen-Krupp-Stahl and other well-known names in German industry. From 2003 to early 2005 he worked as company Director for Central Europe for a French software vendor. Alexander has a degree in Computer Science from Technische Universität, Munich.
