Alexandru Bolboaca

CTO at Mozaic Works


Designing code without types
Friday 11:25 - 12:10
work smart

Your rating:

The first programming languages I've learned and used were strongly typed: Turbo Pascal, C, C++, later Java and C#. I used to believe that strong typing is essential and a great help for quality code. In fact, a strong type system that ensures correctness sounds amazing from an intellectual perspective.

However, I started noticing practical problems. Trying to use a Haskell library for the first time was harder than it should have been due exactly to the strong types. On the other side, Python and later Groovy proved to be excellent for solving problems fast and maintaining code. So what's the answer? Is strong typing essential? How useful is it? And does weak typing work for me because I'm compensating the types with experience and design principles?

Join me to explore this topic and learn from code samples and practical experience how I've used weak types and the conclusions I reached from comparing the approaches.

This talk contains a lot of code samples in multiple programming languages.

Watch the talk    Check the slides


Alex is a polyglot programmer, trainer and coach at Mozaic Works. He has worked for almost 15 years in software development, for various industries and in various european countries and UK.

Alex co-facilitated the first code retreat outside US in Bucharest in 2009. Since then, he's facilitated tens of events such as coding dojos, architectural katas, code retreats and others in many countries from Europe.

He is also a contributor to publications and blogs such as: Today Software Magazine, Agile Record Magazine, and his own blog,