In today’s episode, we’re diving into Marc’s personal cheat sheet—a handy collection of laws, adages, and principles that resonate with anyone involved in software development and team leadership. Marc explains how these age-old sayings aren’t always 100% accurate but serve as quick shortcuts to understanding complex issues in work and technology. He even shares one of his favorites, stating, "The amount of energy needed to refute bullshit is an order of magnitude larger than to produce it." It’s a clever reminder of how much easier it is to criticize than to create. This cheat sheet not only covers well-known commandments like Conway’s Law and the Pareto Principle, but also provides insights into managing projects, team dynamics, and system design—helpful for anyone looking to streamline their workflow and leadership style.

Key Points:

• Purpose of the Cheat Sheet: Marc created this guide to record and share frequently referenced laws and principles in software development and team management.
• Commonly Cited Laws and Principles:
  • Brandolini’s Law: Emphasizes the energy cost discrepancy between producing and refuting "bullshit."
  • Brook’s Law: Warns that adding manpower to a late project may only delay it further.
  • Conway’s Law: Suggests that system design mirrors the communication structures of its creators.
  • Gall’s Law: Highlights that a complex system working today evolved from a simpler working system.
  • Goodhart’s Law: Points out that when a measure becomes a target, its value diminishes.
  • Hanlon’s Razor: Advises against attributing to malice what can be explained by simple ignorance.
  • Hofstadter’s Law: Reminds us that things always take longer than expected.
  • Law of Demeter: Advocates for minimal knowledge between system units.
  • Ninety-Ninety Rule: Notes that the last part of coding can take just as much time as the initial portion.
  • Pareto Principle: States that 80% of results often come from 20% of causes.
  • Parkinson’s Law: Observes that work expands to fill the time allocated.
  • Peter Principle: Warns that employees often rise to the level of their incompetence.
• Additional Resources: Marc also points readers to more of his writings, including recommended YouTube channels on Software Engineering, reflections on experience growth, and practical coders’ lessons.

Stay tuned and let these principles guide you as you navigate your journey in software and leadership!
Link to Article