We celebrate the wrong things.
I recently came across a quotation from Thomas Fuller that was written about medicine, but it immediately made me think about Joomla, open source, and the way we value contributions within our community.
"He who cures a disease may be the skillfullest, but he that prevents it is the safest physician. — Thomas Fuller
Thomas Fuller wrote those words centuries ago, yet the principle behind them remains just as relevant today. We naturally admire those who solve problems because their achievements are visible. When a crisis occurs, everyone can see the damage being done and everyone can see the person who steps forward to fix it. Success is measurable, dramatic, and often worthy of praise.
Yet Fuller's observation reminds us that there is another kind of contribution that is no less valuable and may, in fact, be more important. The person who cures a disease demonstrates skill. The person who prevents the disease from occurring demonstrates foresight. One reacts to a problem after it appears, while the other removes the problem before it has the opportunity to cause harm.
The challenge is that prevention is almost invisible.
Why We Celebrate the Wrong Things
Human nature draws our attention to events rather than absences. We notice the server outage because people cannot work. We notice the conflict because it disrupts a community. We notice the volunteer shortage because tasks stop getting done. What we rarely notice are all the situations that never became problems in the first place.
As a result, communities such as Joomla often celebrate the wrong achievements. We recognise the developer who fixes a critical bug just before a release, the volunteer who steps in to rescue an event, or the team that works through a weekend to resolve a security issue. Those contributions are important and deserve recognition. However, we rarely give the same attention to the people whose work prevented those situations from arising in the first place.
Crisis management is visible and dramatic. Prevention is quiet and uneventful. One creates stories that can be retold. The other leaves little evidence that anything happened at all. The irony is that the quieter contribution is frequently the more valuable one.
The Hidden Value of Prevention
Within Joomla, some of the most valuable contributions are also the least visible. A volunteer who improves documentation may prevent hundreds of support requests. Someone who mentors new contributors may prevent frustration and burnout. A team that establishes clear processes may avoid conflicts that would otherwise consume countless hours of discussion.
When prevention is working well, it can even appear that very little work is being done. Releases happen without drama. Teams collaborate effectively. Contributors know where to find information and understand how decisions are made. From the outside, everything appears ordinary.
In reality, maintaining that sense of normality often requires significant effort. It demands planning, communication, and a willingness to deal with small issues before they become large ones. It requires people to invest time in activities whose success will never be measured because success means that nothing happens.
That can be a difficult concept for any community to appreciate. It is far easier to recognise the person who solves a visible problem than the person who quietly ensured the problem never existed.
Lessons from Joomla
Joomla has always depended upon volunteers. Because of that, the health of the project is determined not only by the quality of its code but also by the quality of its community. Whenever a volunteer leaves because they feel ignored, unsupported, or unappreciated, the immediate impact may seem small. Over time, however, those losses accumulate and become far more difficult to repair than they would have been to prevent.
We often focus our attention on recruiting new contributors when existing contributors leave. Recruitment is important, but prevention is usually more effective than replacement. Retaining an experienced volunteer requires far less effort than replacing their knowledge, experience, and commitment after they have gone.
The same principle applies throughout the project. It is easier to maintain clear communication than to repair damaged trust. It is easier to support contributors than to replace them. It is easier to address concerns early than to deal with the consequences after people have become frustrated or disengaged.
These actions rarely attract recognition because they do not produce dramatic stories. Nevertheless, they are often the difference between a healthy community and one that finds itself repeatedly facing the same problems.
Prevention and Leadership
Within Joomla, leadership is often judged by visible outcomes: successful releases, events, partnerships, or strategic initiatives. Yet some of the most important leadership work is far less visible. It involves listening to concerns before they become complaints, addressing tensions before they become disputes, and creating an environment in which contributors feel heard, respected, and valued.
The best leaders are not necessarily those who manage crises most effectively. Often they are the people who identify risks early enough that a crisis never develops. Their success can be difficult to measure because it is reflected in events that never occur. There is no headline for the volunteer who chose to stay, the disagreement that never escalated, or the problem that was resolved before anyone else became aware of it.
Yet these quiet successes are often the foundation upon which every visible success is built.
The Contributions That Matter Most
Modern culture has a tendency to celebrate firefighters. We admire the people who rush into difficult situations and save the day. There is certainly value in that admiration because solving problems requires expertise, dedication, and commitment.
However, Thomas Fuller reminds us that there is another standard by which we should measure success. The most skilled person may be the one who cures the disease after it appears. The safest person is the one who prevents the disease from spreading in the first place.
Joomla does not need more heroes who repeatedly save the project from preventable problems. It needs more people who quietly create the conditions in which those problems are less likely to occur at all. The developer who fixes the bug may demonstrate great skill. The leader who prevents the bug from becoming a crisis, the mentor who prevents a volunteer from leaving, or the contributor who prevents confusion through better documentation may never receive the same recognition.
Yet their contribution is often the one that has the greatest long-term impact on the project.
The healthiest communities are rarely those that become experts at surviving crises. They are the ones that become experts at preventing those crises from occurring at all.
