Codes of Conduct focus on vices and naively attempt to list all the banned behaviors. We focus on virtues and thus set the bar on behavior HIGH. Therefore, we do not have a Code of Conduct. We have a Code of Virtues—virtues that have been present and part of Perl from the very beginning.

Virtues versus Vices

The concept of virtues is very old, dating back to Nicomachean Ethics. Aristotle identified virtues as character traits that enable individuals to live a good life and achieve eudaimonia (flourishing or happiness). Examples include courage, temperance, and justice. Virtue was seen as the “golden mean” between two extremes (e.g., courage is the balance between recklessness and cowardice).

Aristotle’s virtues, such as courage, justice, and temperance, emphasize achieving a balanced and flourishing life through reason. These ideals directly influenced formal Christian virtues, particularly through St. Thomas Aquinas’ prolific writings, which integrated them with faith, hope, and charity as moral principles for spiritual growth. For example, the medieval codes of chivalry reflected this synthesis, urging knights to embody classical virtues like courage, meekness, humility, and compassion, as seen in their oaths to protect the weak and uphold justice.

Here we describe what Larry Wall meant in correct, virtuous, and perhaps chivalrous terms.

The 3 Virtues of a Perl Programmer, Properly Defined

Our Code of Virtues is made of the Three Virtues of a Perl Programmer, first elucidated by Perl’s founder, Larry Wall. With a mind toward virtue, we define what he described in positive terms of virtue rather than the traditional words, which are actually vices.

Practical Wisdom or Prudence, Not Laziness

Unlike the vice of laziness, this virtue refers to practical wisdom or prudence. It involves the ability to make sound decisions and take appropriate actions based on understanding, experience, and ethical considerations. This aligns closely with Larry’s definition of laziness, summarized as:

“…the quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don’t have to answer so many questions about it.”

Spiritedness, Not Impatience

Accounting for the passionate aspect of human nature, this encompasses emotions like anger, righteous indignation, and the drive to achieve justice or excellence. Who among us has not experienced this in some form, particularly during heated online discussions? This aligns well with Larry’s definition of impatience, summarized as:

“…the anger you feel when the computer is being lazy. This makes you write programs that don’t just react to your needs but actually anticipate them—or at least pretend to.”

Good Order, Not Hubris

Far from harmful pride, this refers to maintaining good order and governance, both in societal contexts and personal conduct. Applied to programming, it signifies creating well-structured, organized, and maintainable code. This aligns well with Larry’s definition of hubris, summarized as:

“…the quality that makes you write (and maintain) programs that other people won’t want to say bad things about.”