Skip to main content

Visual design patterns

Most of the time, when guys were explaining the role of the software architect to me, I was not able to believe it would be possible to organise software development on such a division of responsibilities. I always feel the architecture is a discipline each member of a team should embrace.
The "Design Patterns Quick Reference" from Mc Donaland is really useful because it allows the team to speak about the most appropriate choice in front of this great summary.
But a common pitfall with these pattern design concepts is the fact people will over design and move to a solution too complex.
One solution resides in the Test driven development principles where after coding the test and writing the code for them to pass, there is the refactoring step.
This is the good moment to consider inserting a design pattern.
Make things work, then focus on building maintainable code.

Sources :
Mcdonaldland: mcdonaldland » Design Patterns Quick Reference
Davidhayden: Design Patterns and Agile Software Development

Comments

Popular posts from this blog

Learning about Data Science?

This is the end of a beautiful summer, and also one of the warmer recorded in France. I’m continuing my journey in the product management world and today I’m living in the product marketing one too. I will blog about this later. During this first half of this year, I read several articles on big data and started to understand how important the data science discipline is. Being able to define a direction/goal to search, collecting the proper data, then using a collection of techniques to extract something others can’t see - it sounds like magic. Also, when I listened to the Udacity Linear Disgression podcast episode “Hunting the Higgs”, I understood people with these skills can be better at solving a problem than the domain experts themselves. Katie Malone explained that in a competition to solve a particle physics problem, the best results came from machine learning people. Then I read the article about Zenefit on the vision mobile website : “Zenefits is an insurance compan

Lancement de ProductTank Lyon

Tout d’abord, bonne année 2020. Je me suis investi ces dernières années dans les communautés/événements CARA Lyon, MiXiTConf, LyonDataScience et CaféDevOps sur Lyon, France. Ces activités m’ont permis de comprendre les experts de ces domaines, d’apprendre quelques notions fondamentales à travers leurs exposés et d'améliorer mes capacités d’échange avec eux. Product Manager depuis plus de 5 ans, je désire améliorer mes réflexes et compétences dans mon domaine. Le faire à travers des rencontres/meetup est ce que je préfère et j’aimerais retrouver la stimulation des communautés dans cette discipline. En cette année 2020, quelques Product Manager Lyonnais, lançons, le meetup ProductTankLyon à Lyon, France. Le réseau ProductTank compte plus de 150 meetup dans le monde et profite des conférences, blog et podcast MindTheProduct. Inscrivez-vous ici , si vous voulez vous joindre à nous.

Read bead experiment

The "Read bead experiment" was created by Dr. Edward Deming and aim to demonstrate the ineffectiveness (sometimes effectiveness) of the various management methods. At the end of the experiment, a statistical graphical tool is used to analyse the experiment's results. By following this exercise, you will understand that actions taken by the people playing the managers are detrimental to the employees, but after the analyses are shown to have no impact on the efficiency of the process . The conclusion proposes ways to properly use performance data in a quality environment in order to achieve continual improvement. The several videos by Fluor Hanford (Steve Prevette) posted below, will help you to understand what is really important in a process. Meet the  company  with its "willing workers", quality control personnel, a data recorder, and a foreman. All wish to produce white beads using a 50 holed paddle, but unfortunately there are bad quality red beads.