La parole est aux speakers : Matthias Noback
Jusqu’au Forum PHP 2018, retrouvez nos interviews de speakers pour mieux comprendre leur parcours et le sujet qu’ils aborderont lors de leur conférence !
Beyond design patterns and principles - writing good OO code
Of course, you should read all you can about SOLID, Design patterns, Patterns of Enterprise Application Architecture, etc. Once you have a basic understanding of these topics you still have to write that code though, and write it well too! What is good code? Are there some guidelines, or rules of thumb, which you can follow while making your everyday coding decisions?
In this talk I’ll cover many of these coding guidelines, which aren’t usually covered by patterns or principles books. They should help you write better code and give you a richer vocabulary for reviewing other people’s code. Some of the subjects that we’ll discuss are: state, mutability, CQS, one-method objects, domain-first, API-driven, functional programming influences, object boundaries, (de)serialization, and many more!
You are a prolific author with 3 books on your belt, why do you write these books? Do you have a new book in preparation right now?
I like to write. In particular when I’m coding a lot, my « bucket of ideas » is overflowing, and I need to externalize it to keep a clear mind. There’s often no need to search for topics to write about, because my work as a developer and trainer already provides me with many relevant topics. Quite often a blog post starts off with someone asking a question during a training session. If someone has a question about something, I assume they are not alone; by explaining the answer in more detail on my blog, I like to believe that it answers this question for many people. Sometimes an article gets “triggered” by something I read on Twitter. A programming joke, or a piece of advice. Often this starts a little fire in me, and I want to explain in a post how « someone is wrong on the Internet ».
You publish one blog post a week. How do you keep up at this pace and still write interesting articles ?
These three books all have their own story. When writing « A Year with Symfony », I just wanted to share some things that I had figured out during my first year with Symfony 2. It did take a relatively small amount of time to write, because it was based on recent development experiences. « Principles of Package Design » was the « effect » of stumbling upon Uncle Bob’s « principles of component design ». These are very powerful design principles, which aren’t discussed as much as the SOLID principles, and I think they are at least equally important. “Microservices for everyone” was not born from experience, but from a desire to learn more. It reflects the things I learned during half a year of research.
I feel there’s another book sort floating around that I may need to catch and start working on. I’m not sure what it’ll be about actually, but I’m definitely collecting ideas already. Also, I’m revising « Principles of Package Design », because it’ll be re-published by Apress, towards the end of the year. »
You often come to France for work, did you grow fond of this country? 🙂
Yes, I do. In particular I’ve been doing many training sessions at Akeneo, in Nantes. It’s an interesting company, with excellent developers, and a management team that really appreciates the fact that developers need to learn continuously. It’s the only way to prepare a company revolving around software for a long and prosperous future. It made me like France, the French, and French too. I’ll be happy to return to France for AFUP in October.
|Matthias Noback has 15 years of experience in web application development. He is the author of A Year With Symfony, Principles of Package Design and Microservices for everyone. While always striving for better programming practices in general, he’s taken a special interest in application architecture, Domain-Driven Design, testing, microservices and application integration patterns|