the Adimeo PHP teams attended the PHP Forum as they do every year. The opportunity to find famous faces but also to benefit from feedback such as that of Frédéric Bouchery (@FredBouchery – lead developer at Klaxoon) on pragmatic development, or how to use common sense when developing. Almost all the seats in the room are occupied for the first conference of the day, dealing with pragmatic development , presented by Frédéric Bouchery. foumphp2019-pragmatic-development Credit : Julien Pauli (@JulienPauli) But what is pragmatism my dear Jamy?

It’s buying a Renault Espace Venezuela Phone Number List than an Audit R8 when you have 3 children. It is giving each of them a tablet during the vacation trip, rather than letting them get bored and every 2 minutes being entitled to the endless question “When are we arriving?” ”(Although we could also question the long-term effect of the use of digital media for young children). In short, it’s based on your experience to put in place, not the best solution, but the one that actually works . The importance of structuring your code Unlike an artificial intelligence which would generate all its code in a single file without it being a problem to maintain it and make it evolve, we human beings do not have the same speed of calculation. “Any fool can write code that a computer can understand.

The Php Forum: The Opportunity To Benefit

Good programmers write code that humans can understand. ” – Martin Fowler We need to structure our code so that it is understandable by other developers , from beginner to senior, and by our future us. “You are your future legacy. » Frédéric reminds us, and it’s true! How many times do we go over the code of our former us saying to ourselves “But who is the moron who wrote that? Ah, it’s me … ”. “The code is like jokes, if you have to explain it, it’s bad!” – Cory House There are so many principles to experiment with when coding. Each of them promises a more maintainable and scalable code than the other. Too many programming rules kill programming!


The developers all apply (or try to) apply “good programming” principles , with some rules illustrated by nice acronyms, such as: “SOLID “: Single responsibility | Open / closed | Liskov substitution | Interface segregation | Dependency inversion; representing the five basic principles for object oriented programming . Until then, everyone follows. “DRY” : Don’t Repeat Yourself; philosophy of avoiding code redundancy . “Demeter law, Calistenic, East-Oriented, Hollywood principle, Else-less, Comment-less, DDD, TDD, KISS, YAGNI, TU, CI, AOP, OOP, Immutable, Strict-typed, Cyclomatic complexity, Dependency injection,

From Feedback. Frédéric Bouchery, Lead

Design by contract, Fail fast, Defensive programming, Loose coupling, High cohesion, Composition over Inheritance, CQRS, … » quickly lists Frédéric, breathless … After all these years of development trying to apply these principles, he has come to the conclusion that there is only one perfect, bug-free, and everyone-agreeable code. He gives us his secret (I don’t have to say that I told you ): forumphp-pragmatic-development And yes, the perfect code doesn’t do anything, because it just doesn’t exist ! Why do we have to go back to basics What if we stopped for 5 minutes and asked ourselves the right questions: why not design a solution according to the experience of each developer on the team?

Instead of putting up barriers, why not let developers choose what suits them best? Why not code less, but more appropriately ? When faced with a technical problem, Frédéric and his team meet to discuss the alternatives available to them, then use a choice matrix to determine which option is the most appropriate. The winning solution is retained collegially , which allows the whole team to agree. pragmatic-development-php-forum WET rather than DRY? Frédéric invites us to ask ourselves questions before applying the previously mentioned principles and to find a happy medium between dogma and benefit .

Leave a Reply

Your email address will not be published.