Christian Jacob - Simulating Evolution with Mathematica

Mike's Notes

I have collected here some historical references to work by Christian Jacob, a Professor at the University of Calgary, about evolutionary algorithms. There are many Mathematica Notebooks available in Mathematica version 2.2. I hope to use the Wolfram-provided copy of WolframOne to open and try out these notebooks.

These references are for future planned Pipi developments.

Resources

References

  • Simulating Evolution with Mathematica (1997) by Christian Jacob
  • Illustrating evolutionary computation with Mathematica by Christian Jacob. Morgan Kaufmann Publishers Inc., San Francisco, CA, 2001. 578 pp. Type: Book (9781558606371)
  • Holland, J.H. Adaptation in Natural and Artificial Systems : An Introductory Analysis with Applications to Biology, Control, and Artificial Intelligence. MIT Press, Cambridge, MA, 1992.

Repository

  • Home > Ajabbi Research > Library > Authors > Christian Jacob
  • Home > Ajabbi Research > Library > Evolutionary Algorithm
  • Home > Ajabbi Research > Library > Membrane Computing

Last Updated

23/04/2025

Simulating Evolution with Mathematica

By: Christian Jacob
Google Scholar: 1997

Evolutionary mechanisms as observed in nature are successfully used in evolutionary algorithms (EA) in order to solve complex optimisation tasks or to mimic natural evolution processes. We present a collection of evolutionary algorithms which we have implemented in Mathematica, together with some visualisation examples and applications. The three major EA classes are discussed: Evolution Strategies (ES), Genetic Algorithms (GA), and Genetic Programming (GP). Interactive evolution is demonstrated by the breeding of biomorphs, recursively branched line drawings. Multi-modal ES- and GA- experiments are demonstrated for a parameter optimisation task. The evolution of robot control programs shows a simple GP application. The article concludes with a more sophisticated GP example: breeding developmental programs for artificial plant-like structures encoded based on Lindenmayer systems.

The Physics of Flow: How the Constructal Law Can Revolutionize Product Development

Mike's Notes

"The constructal law, stated by Duke’s Adrian Bejan in 1996, is the law of physics that accounts for the phenomenon of evolution (configuration, form, design) throughout nature, inanimate flow systems and animate systems together." - Duke University


Adrian Bejan 2018

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Authors > Adrian Bejan
  • Home > Handbook > 

Last Updated

22/04/2025

The Physics of Flow: How the Constructal Law Can Revolutionize Product Development

By: Leah  Brown
IT Revolution: 17/04/2025

Leah Brown, Managing Editor at IT Revolution working on publishing books and guidance papers for the modern business leader. I also oversee the production of the IT Revolution blog, combining the best of responsible, human-centered content with the assistance of AI tools.

In product development, the quest for better flow has been a constant for nearly two decades. From Donald Reinertsen’s seminal work in 2009 to the DevOps movement and beyond, creating smooth, efficient value streams has been central to organizational success. But what if there was a fundamental law of physics that could deepen our understanding of flow and revolutionize how we approach product development?

In the Spring 2025 issue of the Enterprise Technology Leadership Journal, Brian Moore of RTX offers a fascinating perspective in his paper “It’s All About Flow: Applying the Constructal Law of Physics to Product Development.” Moore introduces the constructal law, a principle of physics formulated by Duke professor Adrian Bejan in 1996, and shows how it applies to product development value streams.

What is the Constructal Law?

The constructal law states: “For a flow system to persist in time (to live) it must evolve freely such that it provides easier and greater access to its currents.”

Simply put, this principle explains why flow systems throughout nature—from river basins to tree branches to our own circulatory systems—evolve certain patterns and hierarchies. They naturally organize to provide better access to their flows. Moore argues that this same law governs our product development processes, and understanding it can help us accelerate improvement in our value streams.

Three Key Imperatives

Moore distills three primary imperatives from the constructal theory that can transform how we approach product development:

1. Support Freedom

For flow systems to evolve and improve, they need freedom to change. In nature, water inexorably finds the fastest path downhill because it’s free to do so. Similarly, product development teams need freedom to adapt both their processes and products in response to feedback.

The paper examines how freedom exists on a continuum in organizations, with various factors limiting it:

  • Team mindset (“We can’t change that.”)
  • Organizational policies and processes
  • Product architecture
  • Tooling and infrastructure
  • Alignment and accountability

Moore demonstrates how freedom is already central to many Lean-Agile practices, including SAFe’s principles of decentralized decision-making, preserving options, and unlocking intrinsic motivation. Industrial DevOps similarly emphasizes team autonomy within clearly defined objectives.

2. Embrace Hierarchy

Though hierarchy often gets a bad reputation in organizational theory, Moore points out that it’s essential in nature—without hierarchy, life would be limited to single-cell organisms. Effective flow systems naturally organize in hierarchical patterns with “many small components and a few large ones that are flowing together.”

This applies to product development in several ways:

  • SAFe’s focus on organizing around value and applying systems thinking.
  • Industrial DevOps principles of architecture for flow and establishing cadence.
  • Reinertsen’s guidance on embedding fast control loops inside slow loops.
  • Team Topologies’ emphasis on appropriate team structures.

The key insight is that without hierarchy, development would be limited to small, isolated teams rather than coordinated solutions to complex problems.

3. Pursue Beauty

Perhaps the most surprising imperative is the pursuit of beauty. Drawing on the work of Frederick Turner and Christopher Alexander, Moore argues that beauty is not subjective fluff but a central organizing principle relating to wholeness, meaning, fitness for purpose, and harmony.

Beauty serves as a powerful pull force for product development flow systems. As the paper states: “When we deliver products that create beauty in the world, we delight our customers, enhance society and the environment, and provide a profound source of motivation to our team members.”

Moore shows how this manifests in:

  • SAFe’s strategic themes and solution visions
  • Design thinking practices that focus on holistic solutions
  • Industrial DevOps’ systems engineering sensibility
  • The wholeness approach in Wiring the Winning Organization

Why This Matters

Moore’s application of constructal theory to product development is groundbreaking because it provides a unifying scientific framework for understanding the evolution of value streams. Just as Newton’s laws transformed civil engineering, enabling the construction of previously unimaginable structures, the constructal law can potentially accelerate our ability to design more effective product development systems.

The paper argues that this approach allows practitioners to:

  1. See how various Lean-Agile and DevOps principles relate to each other
  2. Apply these principles more confidently in their organizations
  3. Communicate more effectively about transformational initiatives

“Just as structural engineers, grounded in their knowledge of physics, can confidently build amazing bridges or aircraft that are both daring and safe, so can we accelerate the evolution of product value streams in the direction of making access to better value easier and faster,” Moore writes.

Practical Applications

For leaders in technology and product development, the paper offers several practical takeaways:

  • Evaluate freedom constraints: Identify where your organization limits the freedom of teams to respond to feedback and evolve their processes.
  • Design appropriate hierarchies: Rather than rejecting hierarchy outright, focus on creating value-oriented hierarchies that enable coordination without bureaucracy.
  • Connect work to beauty: Help teams understand how their contributions create holistic, meaningful solutions rather than just features.

Moore’s work doesn’t reject existing Lean-Agile frameworks but rather enriches them by providing a deeper scientific foundation. It shows how principles from SAFe, DevOps, and other methodologies align with natural laws that govern all flow systems.

The Future of Flow

By grounding product development theory in physics, Moore opens the door to new insights about how to design organizations that can evolve faster and more effectively. His paper suggests that as we deepen our understanding of constructal theory, we’ll continue to discover new ways to improve value flow.

For anyone involved in product development, process improvement, or organizational design, Moore’s paper represents a significant contribution to the field. It bridges the gap between science and practice, offering both theoretical depth and practical guidance.

“It’s All About Flow” is available in the Spring 2025 issue of the Enterprise Technology Leadership Journal from IT Revolution Press. For those intrigued by the intersection of physics, organization design, and product development, it promises to be essential reading.

As Moore himself recommends, those interested in this approach would benefit from exploring Adrian Bejan’s work directly and starting to observe constructal patterns in nature, society, and their workplaces. The more we understand these fundamental patterns of flow, the better we can design systems that harness them.

Ranked: Duolingo’s Most Popular Languages in Every Country in 2024

Mike's Notes

This could be a rough guide to what languages to initially target for translating Pipi UI and documentation. Pipi 9 has already been set up and tested to be multi-lingual and multi-script.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Visual Capitalist
  • Home > Learn > Reference > i18n

Last Updated

21/04/2025

Ranked: Duolingo’s Most Popular Languages in Every Country in 2024

By: Marcus Lu & Amy Kuo
Visual Capitalist: 6/04/2025

Key Takeaways

  • English is the number #1 ranked language on Duolingo in 134 different countries.
  • Other popular languages include Spanish (#1 in 33 countries) and French (#1 in 16 countries).

About half of the world’s population speaks at least two languages.

Learning a second language is a valuable endeavor, improving cognitive function, social awareness, and providing more career opportunities.

But what languages are people around the world trying to learn, and how does it differ from country to country?

We map the most popular languages studied on Duolingo from their 2024 language report.

The Most Popular Languages For Learning

English is the number #1 ranked language on Duolingo in 134 different countries. It is also the most prominent language on the planet, with approximately 1.5 billion speakers.

Browse the below table to see the top language and second-most popular language in every country Duolingo is available in.

Country Top Language on DuoLingo 2nd Language
๐Ÿ‡ฆ๐Ÿ‡ซ Afghanistan English German
๐Ÿ‡ฆ๐Ÿ‡ฑ Albania English German
๐Ÿ‡ฉ๐Ÿ‡ฟ Algeria English French
๐Ÿ‡ฆ๐Ÿ‡ฉ Andorra English Spanish
๐Ÿ‡ฆ๐Ÿ‡ด Angola English French
๐Ÿ‡ฆ๐Ÿ‡ท Argentina English Portuguese
๐Ÿ‡ฆ๐Ÿ‡ฒ Armenia English French
๐Ÿ‡ฆ๐Ÿ‡น Austria English German
๐Ÿ‡ฆ๐Ÿ‡ฟ Azerbaijan English Turkish
๐Ÿ‡ง๐Ÿ‡ญ Bahrain English French
๐Ÿ‡ง๐Ÿ‡ฉ Bangladesh English Korean
๐Ÿ‡ง๐Ÿ‡พ Belarus English German
๐Ÿ‡ง๐Ÿ‡ช Belgium English French
๐Ÿ‡ง๐Ÿ‡ฏ Benin English Spanish
๐Ÿ‡ง๐Ÿ‡ด Bolivia English Portuguese
๐Ÿ‡ง๐Ÿ‡ท Brazil English Spanish
๐Ÿ‡ง๐Ÿ‡ฌ Bulgaria English German
๐Ÿ‡ง๐Ÿ‡ซ Burkina Faso English French
๐Ÿ‡ง๐Ÿ‡ฎ Burundi English French
๐Ÿ‡จ๐Ÿ‡ป Cabo Verde English French
๐Ÿ‡ฐ๐Ÿ‡ญ Cambodia English Chinese
๐Ÿ‡จ๐Ÿ‡ฒ Cameroon English German
๐Ÿ‡จ๐Ÿ‡ซ Central African Republic English French
๐Ÿ‡น๐Ÿ‡ฉ Chad English French
๐Ÿ‡จ๐Ÿ‡ฑ Chile English Portuguese
๐Ÿ‡จ๐Ÿ‡ณ China English Japanese
๐Ÿ‡จ๐Ÿ‡ด Colombia English French
๐Ÿ‡ฐ๐Ÿ‡ฒ Comoros English French
๐Ÿ‡จ๐Ÿ‡ฌ Republic of the Congo English Spanish
๐Ÿ‡จ๐Ÿ‡ท Costa Rica English Spanish
๐Ÿ‡จ๐Ÿ‡ฎ Cรดte d'Ivoire English Spanish
๐Ÿ‡ญ๐Ÿ‡ท Croatia English Spanish
๐Ÿ‡จ๐Ÿ‡บ Cuba English French
๐Ÿ‡จ๐Ÿ‡พ Cyprus English Spanish
๐Ÿ‡จ๐Ÿ‡ฟ Czechia English German
๐Ÿ‡จ๐Ÿ‡ฉ Democratic Republic of the Congo English French
๐Ÿ‡ฉ๐Ÿ‡ฏ Djibouti English French
๐Ÿ‡ฉ๐Ÿ‡ด Dominican Republic English French
๐Ÿ‡ช๐Ÿ‡จ Ecuador English French
๐Ÿ‡ช๐Ÿ‡ฌ Egypt English French
๐Ÿ‡ธ๐Ÿ‡ป El Salvador English French
๐Ÿ‡ฌ๐Ÿ‡ถ Equatorial Guinea English French
๐Ÿ‡ช๐Ÿ‡ท Eritrea English French
๐Ÿ‡ช๐Ÿ‡ช Estonia English Spanish
๐Ÿ‡ช๐Ÿ‡น Ethiopia English French
๐Ÿ‡ซ๐Ÿ‡ท France English Spanish
๐Ÿ‡ฌ๐Ÿ‡ฆ Gabon English Spanish
๐Ÿ‡ฌ๐Ÿ‡ช Georgia English German
๐Ÿ‡ฉ๐Ÿ‡ช Germany English German
๐Ÿ‡ฌ๐Ÿ‡ท Greece English Spanish
๐Ÿ‡ฌ๐Ÿ‡น Guatemala English French
๐Ÿ‡ฌ๐Ÿ‡ณ Guinea English French
๐Ÿ‡ฌ๐Ÿ‡ผ Guinea-Bissau English French
๐Ÿ‡ญ๐Ÿ‡น Haiti English Spanish
๐Ÿ‡ญ๐Ÿ‡ณ Honduras English French
๐Ÿ‡ญ๐Ÿ‡บ Hungary English German
๐Ÿ‡ฎ๐Ÿ‡ณ India English Hindi
๐Ÿ‡ฎ๐Ÿ‡ฉ Indonesia English Japanese
๐Ÿ‡ฎ๐Ÿ‡ท Iran English German
๐Ÿ‡ฎ๐Ÿ‡ถ Iraq English French
๐Ÿ‡ฎ๐Ÿ‡ฑ Israel English Hebrew
๐Ÿ‡ฎ๐Ÿ‡น Italy English Italian
๐Ÿ‡ฏ๐Ÿ‡ต Japan English Korean
๐Ÿ‡ฏ๐Ÿ‡ด Jordan English French
๐Ÿ‡ฐ๐Ÿ‡ฟ Kazakhstan English French
๐Ÿ‡ฐ๐Ÿ‡ฎ Kiribati English Spanish
๐Ÿ‡ฐ๐Ÿ‡ผ Kuwait English French
๐Ÿ‡ฐ๐Ÿ‡ฌ Kyrgyzstan English Russian
๐Ÿ‡ฑ๐Ÿ‡ฆ Laos English Chinese
๐Ÿ‡ฑ๐Ÿ‡ป Latvia English German
๐Ÿ‡ฑ๐Ÿ‡ง Lebanon English French
๐Ÿ‡ฑ๐Ÿ‡พ Libya English French
๐Ÿ‡ฑ๐Ÿ‡ฎ Liechtenstein English Spanish
๐Ÿ‡ฑ๐Ÿ‡น Lithuania English Spanish
๐Ÿ‡ฑ๐Ÿ‡บ Luxembourg English French
๐Ÿ‡ฒ๐Ÿ‡ฌ Madagascar English French
๐Ÿ‡ฒ๐Ÿ‡ผ Malawi English French
๐Ÿ‡ฒ๐Ÿ‡พ Malaysia English Japanese
๐Ÿ‡ฒ๐Ÿ‡ป Maldives English Spanish
๐Ÿ‡ฒ๐Ÿ‡ฑ Mali English French
๐Ÿ‡ฒ๐Ÿ‡น Malta English Spanish
๐Ÿ‡ฒ๐Ÿ‡ท Mauritania English French
๐Ÿ‡ฒ๐Ÿ‡ฝ Mexico English French
๐Ÿ‡ฒ๐Ÿ‡ฉ Moldova English German
๐Ÿ‡ฒ๐Ÿ‡จ Monaco English French
๐Ÿ‡ฒ๐Ÿ‡ณ Mongolia English Korean
๐Ÿ‡ฒ๐Ÿ‡ช Montenegro English Spanish
๐Ÿ‡ฒ๐Ÿ‡ฆ Morocco English French
๐Ÿ‡ฒ๐Ÿ‡ฟ Mozambique English French
๐Ÿ‡ฒ๐Ÿ‡ฒ Myanmar English Japanese
๐Ÿ‡ณ๐Ÿ‡ต Nepal English Japanese
๐Ÿ‡ณ๐Ÿ‡ฑ Netherlands English Spanish
๐Ÿ‡ณ๐Ÿ‡ฎ Nicaragua English French
๐Ÿ‡ณ๐Ÿ‡ช Niger English French
๐Ÿ‡ด๐Ÿ‡ฒ Oman English French
๐Ÿ‡ต๐Ÿ‡ฐ Pakistan English Arabic
๐Ÿ‡ต๐Ÿ‡ฆ Panama English French
๐Ÿ‡ต๐Ÿ‡พ Paraguay English Portuguese
๐Ÿ‡ต๐Ÿ‡ช Peru English Portuguese
๐Ÿ‡ต๐Ÿ‡ฑ Poland English Spanish
๐Ÿ‡ต๐Ÿ‡น Portugal English French
๐Ÿ‡ถ๐Ÿ‡ฆ Qatar English Spanish
๐Ÿ‡ท๐Ÿ‡ด Romania English Spanish
๐Ÿ‡ท๐Ÿ‡บ Russia English German
๐Ÿ‡ท๐Ÿ‡ผ Rwanda English French
๐Ÿ‡ธ๐Ÿ‡ฒ San Marino English Italian
๐Ÿ‡ธ๐Ÿ‡น Sรฃo Tomรฉ and Prรญncipe English French
๐Ÿ‡ธ๐Ÿ‡ฆ Saudi Arabia English French
๐Ÿ‡ธ๐Ÿ‡ณ Senegal English Spanish
๐Ÿ‡ธ๐Ÿ‡จ Seychelles English Spanish
๐Ÿ‡ธ๐Ÿ‡ฌ Singapore English Japanese
๐Ÿ‡ธ๐Ÿ‡ฐ Slovakia English German
๐Ÿ‡ธ๐Ÿ‡ด Somalia English Arabic
๐Ÿ‡ฐ๐Ÿ‡ท South Korea English Japanese
๐Ÿ‡ธ๐Ÿ‡ธ South Sudan English French
๐Ÿ‡ช๐Ÿ‡ธ Spain English Spanish
๐Ÿ‡ฑ๐Ÿ‡ฐ Sri Lanka English Japanese
๐Ÿ‡ธ๐Ÿ‡ฉ Sudan English French
๐Ÿ‡จ๐Ÿ‡ญ Switzerland English French
๐Ÿ‡ธ๐Ÿ‡พ Syria English German
๐Ÿ‡น๐Ÿ‡ฏ Tajikistan English Russian
๐Ÿ‡น๐Ÿ‡ญ Thailand English Japanese
๐Ÿ‡น๐Ÿ‡ฑ Timor-Leste English Portuguese
๐Ÿ‡น๐Ÿ‡ฌ Togo English German
๐Ÿ‡น๐Ÿ‡ณ Tunisia English French
๐Ÿ‡น๐Ÿ‡ท Tรผrkiye English German
๐Ÿ‡น๐Ÿ‡ฒ Turkmenistan English Russian
๐Ÿ‡ฆ๐Ÿ‡ช United Arab Emirates English French
๐Ÿ‡บ๐Ÿ‡ฆ Ukraine English German
๐Ÿ‡บ๐Ÿ‡พ Uruguay English Portuguese
๐Ÿ‡บ๐Ÿ‡ฟ Uzbekistan English Russian
๐Ÿ‡ป๐Ÿ‡ช Venezuela English Portuguese
๐Ÿ‡ป๐Ÿ‡ณ Vietnam English Chinese
๐Ÿ‡พ๐Ÿ‡ช Yemen English French
๐Ÿ‡ง๐Ÿ‡ผ Botswana French Spanish
๐Ÿ‡จ๐Ÿ‡ฆ Canada French Spanish
๐Ÿ‡ธ๐Ÿ‡ฟ Eswatini French Spanish
๐Ÿ‡ฌ๐Ÿ‡ฒ Gambia French English
๐Ÿ‡ฌ๐Ÿ‡ญ Ghana French Spanish
๐Ÿ‡ฐ๐Ÿ‡ช Kenya French Spanish
๐Ÿ‡ฑ๐Ÿ‡ธ Lesotho French Spanish
๐Ÿ‡ฑ๐Ÿ‡ท Liberia French English
๐Ÿ‡ฒ๐Ÿ‡บ Mauritius French English
๐Ÿ‡ณ๐Ÿ‡ฌ Nigeria French Spanish
๐Ÿ‡ธ๐Ÿ‡ฑ Sierra Leone French Spanish
๐Ÿ‡น๐Ÿ‡ฟ Tanzania French Swahili
๐Ÿ‡บ๐Ÿ‡ฌ Uganda French English
๐Ÿ‡ป๐Ÿ‡บ Vanuatu French English
๐Ÿ‡ฟ๐Ÿ‡ฒ Zambia French English
๐Ÿ‡ฟ๐Ÿ‡ผ Zimbabwe French Spanish
๐Ÿ‡ง๐Ÿ‡ฆ Bosnia and Herzegovina German English
๐Ÿ‡ฒ๐Ÿ‡ฐ North Macedonia German English
๐Ÿ‡ณ๐Ÿ‡ฆ Namibia German Spanish
๐Ÿ‡ท๐Ÿ‡ธ Serbia German English
๐Ÿ‡ธ๐Ÿ‡ฎ Slovenia German Spanish
๐Ÿ‡ป๐Ÿ‡ฆ Vatican City Italian English
๐Ÿ‡ง๐Ÿ‡น Bhutan Japanese Korean
๐Ÿ‡ง๐Ÿ‡ณ Brunei Japanese Chinese
๐Ÿ‡ต๐Ÿ‡ผ Palau Japanese English
๐Ÿ‡ต๐Ÿ‡ญ Philippines Japanese English
๐Ÿ‡ฆ๐Ÿ‡ฌ Antigua and Barbuda Spanish French
๐Ÿ‡ฆ๐Ÿ‡บ Australia Spanish French
๐Ÿ‡ง๐Ÿ‡ธ Bahamas Spanish French
๐Ÿ‡ง๐Ÿ‡ง Barbados Spanish French
๐Ÿ‡ง๐Ÿ‡ฟ Belize Spanish English
๐Ÿ‡ฉ๐Ÿ‡ฐ Denmark Spanish German
๐Ÿ‡ฉ๐Ÿ‡ฒ Dominica Spanish French
๐Ÿ‡ซ๐Ÿ‡ฏ Fiji Spanish French
๐Ÿ‡ซ๐Ÿ‡ฎ Finland Spanish Finnish
๐Ÿ‡ฌ๐Ÿ‡ง United Kingdom Spanish French
๐Ÿ‡ฌ๐Ÿ‡ฉ Grenada Spanish French
๐Ÿ‡ฌ๐Ÿ‡พ Guyana Spanish English
๐Ÿ‡ฎ๐Ÿ‡ธ Iceland Spanish English
๐Ÿ‡ฎ๐Ÿ‡ช Ireland Spanish Irish
๐Ÿ‡ฏ๐Ÿ‡ฒ Jamaica Spanish French
๐Ÿ‡ฒ๐Ÿ‡ญ Marshall Islands Spanish Japanese
๐Ÿ‡ซ๐Ÿ‡ฒ Micronesia Spanish Japanese
๐Ÿ‡ณ๐Ÿ‡ท Nauru Spanish Chinese
๐Ÿ‡ณ๐Ÿ‡ฟ New Zealand Spanish French
๐Ÿ‡ณ๐Ÿ‡ด Norway Spanish Norwegian
๐Ÿ‡ต๐Ÿ‡ฌ Papua New Guinea Spanish English
๐Ÿ‡ผ๐Ÿ‡ธ Samoa Spanish French
๐Ÿ‡ธ๐Ÿ‡ง Solomon Islands Spanish English
๐Ÿ‡ฟ๐Ÿ‡ฆ South Africa Spanish French
๐Ÿ‡ฐ๐Ÿ‡ณ St. Kitts and Nevis Spanish French
๐Ÿ‡ฑ๐Ÿ‡จ St. Lucia Spanish French
๐Ÿ‡ป๐Ÿ‡จ St. Vincent and the Grenadines Spanish French
๐Ÿ‡ธ๐Ÿ‡ท Suriname Spanish English
๐Ÿ‡ธ๐Ÿ‡ช Sweden Spanish Swedish
๐Ÿ‡น๐Ÿ‡ด Tonga Spanish French
๐Ÿ‡น๐Ÿ‡น Trinidad and Tobago Spanish French
๐Ÿ‡น๐Ÿ‡ป Tuvalu Spanish French
๐Ÿ‡บ๐Ÿ‡ธ U.S. Spanish English

Aside from English, other popular languages include Spanish (#1 in 33 countries) and French (#1 in 16 countries). But there’s clearly an overwhelming preference.

According to Duolingo research, the top reasons people learn English are to support their education, connect with others, and boost their careers.

English’s journey to become the dominant global language goes all the way back to British colonialism that spread it around the world. Back then, other languages—also part of empires—competed for lingua franca status, like French and Spanish.

Rank Language Countries Where
Language is #1
on Duolingo
1 ๐Ÿ‡ฌ๐Ÿ‡ง English 134
2 ๐Ÿ‡ช๐Ÿ‡ธ Spanish 33
3 ๐Ÿ‡ซ๐Ÿ‡ท French 16
4 ๐Ÿ‡ฉ๐Ÿ‡ช German 5
5 ๐Ÿ‡ฏ๐Ÿ‡ต Japanese 4
6 ๐Ÿ‡ฎ๐Ÿ‡น Italian 1

However, with the Industrial Revolution, English gained economic influence, and after the U.S. emerged as a global superpower, it became the preferred language for trade.

American cultural exports—Hollywood movies, music, clothing brands—also increased the language’s prominence.

What to Do

Mike's Notes

Notes on the worldview of Paul Graham.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

19/04/2025

What to Do

By: Paul Graham
paulgraham.com: March 2025

Paul Graham is a programmer, writer, and investor. In 1995, he and Robert Morris started Viaweb, the first software as a service company. Viaweb was acquired by Yahoo in 1998, where it became Yahoo Store. In 2001 he started publishing essays on paulgraham.com, which now gets around 25 million page views per year. In 2005 he and Jessica Livingston, Robert Morris, and Trevor Blackwell started Y Combinator, the first of a new type of startup incubator. Since 2005 Y Combinator has funded over 3000 startups, including Airbnb, Dropbox, Stripe, and Reddit. In 2019 he published a new Lisp dialect written in itself called Bel.

Paul is the author of On Lisp (Prentice Hall, 1993), ANSI Common Lisp (Prentice Hall, 1995), and Hackers & Painters (O'Reilly, 2004). He has an AB from Cornell and a PhD in Computer Science from Harvard, and studied painting at RISD and the Accademia di Belle Arti in Florence..

What should one do? That may seem a strange question, but it's not meaningless or unanswerable. It's the sort of question kids ask before they learn not to ask big questions. I only came across it myself in the process of investigating something else. But once I did, I thought I should at least try to answer it.

So what should one do? One should help people, and take care of the world. Those two are obvious. But is there anything else? When I ask that, the answer that pops up is Make good new things.

I can't prove that one should do this, any more than I can prove that one should help people or take care of the world. We're talking about first principles here. But I can explain why this principle makes sense. The most impressive thing humans can do is to think. It may be the most impressive thing that can be done. And the best kind of thinking, or more precisely the best proof that one has thought well, is to make good new things.

I mean new things in a very general sense. Newton's physics was a good new thing. Indeed, the first version of this principle was to have good new ideas. But that didn't seem general enough: it didn't include making art or music, for example, except insofar as they embody new ideas. And while they may embody new ideas, that's not all they embody, unless you stretch the word "idea" so uselessly thin that it includes everything that goes through your nervous system.

Even for ideas that one has consciously, though, I prefer the phrasing "make good new things." There are other ways to describe the best kind of thinking. To make discoveries, for example, or to understand something more deeply than others have. But how well do you understand something if you can't make a model of it, or write about it? Indeed, trying to express what you understand is not just a way to prove that you understand it, but a way to understand it better.

Another reason I like this phrasing is that it biases us toward creation. It causes us to prefer the kind of ideas that are naturally seen as making things rather than, say, making critical observations about things other people have made. Those are ideas too, and sometimes valuable ones, but it's easy to trick oneself into believing they're more valuable than they are. Criticism seems sophisticated, and making new things often seems awkward, especially at first; and yet it's precisely those first steps that are most rare and valuable.

Is newness essential? I think so. Obviously it's essential in science. If you copied a paper of someone else's and published it as your own, it would seem not merely unimpressive but dishonest. And it's similar in the arts. A copy of a good painting can be a pleasing thing, but it's not impressive in the way the original was. Which in turn implies it's not impressive to make the same thing over and over, however well; you're just copying yourself.

Note though that we're talking about a different kind of should with this principle. Taking care of people and the world are shoulds in the sense that they're one's duty, but making good new things is a should in the sense that this is how to live to one's full potential. Historically most rules about how to live have been a mix of both kinds of should, though usually with more of the former than the latter. [1]

For most of history the question "What should one do?" got much the same answer everywhere, whether you asked Cicero or Confucius. You should be wise, brave, honest, temperate, and just, uphold tradition, and serve the public interest. There was a long stretch where in some parts of the world the answer became "Serve God," but in practice it was still considered good to be wise, brave, honest, temperate, and just, uphold tradition, and serve the public interest. And indeed this recipe would have seemed right to most Victorians. But there's nothing in it about taking care of the world or making new things, and that's a bit worrying, because it seems like this question should be a timeless one. The answer shouldn't change much.

I'm not too worried that the traditional answers don't mention taking care of the world. Obviously people only started to care about that once it became clear we could ruin it. But how can making good new things be important if the traditional answers don't mention it?

The traditional answers were answers to a slightly different question. They were answers to the question of how to be, rather than what to do. The audience didn't have a lot of choice about what to do. The audience up till recent centuries was the landowning class, which was also the political class. They weren't choosing between doing physics and writing novels. Their work was foreordained: manage their estates, participate in politics, fight when necessary. It was ok to do certain other kinds of work in one's spare time, but ideally one didn't have any. Cicero's De Officiis is one of the great classical answers to the question of how to live, and in it he explicitly says that he wouldn't even be writing it if he hadn't been excluded from public life by recent political upheavals. [2]

There were of course people doing what we would now call "original work," and they were often admired for it, but they weren't seen as models. Archimedes knew that he was the first to prove that a sphere has 2/3 the volume of the smallest enclosing cylinder and was very pleased about it. But you don't find ancient writers urging their readers to emulate him. They regarded him more as a prodigy than a model.

Now many more of us can follow Archimedes's example and devote most of our attention to one kind of work. He turned out to be a model after all, along with a collection of other people that his contemporaries would have found it strange to treat as a distinct group, because the vein of people making new things ran at right angles to the social hierarchy.

What kinds of new things count? I'd rather leave that question to the makers of them. It would be a risky business to try to define any kind of threshold, because new kinds of work are often despised at first. Raymond Chandler was writing literal pulp fiction, and he's now recognized as one of the best writers of the twentieth century. Indeed this pattern is so common that you can use it as a recipe: if you're excited about some kind of work that's not considered prestigious and you can explain what everyone else is overlooking about it, then this is not merely a kind of work that's ok to do, but one to seek out.

The other reason I wouldn't want to define any thresholds is that we don't need them. The kind of people who make good new things don't need rules to keep them honest.

So there's my guess at a set of principles to live by: take care of people and the world, and make good new things. Different people will do these to varying degrees. There will presumably be lots who focus entirely on taking care of people. There will be a few who focus mostly on making new things. But even if you're one of those, you should at least make sure that the new things you make don't net harm people or the world. And if you go a step further and try to make things that help them, you may find you're ahead on the trade. You'll be more constrained in what you can make, but you'll make it with more energy.

On the other hand, if you make something amazing, you'll often be helping people or the world even if you didn't mean to. Newton was driven by curiosity and ambition, not by any practical effect his work might have, and yet the practical effect of his work has been enormous. And this seems the rule rather than the exception. So if you think you can make something amazing, you should probably just go ahead and do it.

Notes

[1] We could treat all three as the same kind of should by saying that it's one's duty to live well — for example by saying, as some Christians have, that it's one's duty to make the most of one's God-given gifts. But this seems one of those casuistries people invented to evade the stern requirements of religion: you could spend time studying math instead of praying or performing acts of charity because otherwise you were rejecting a gift God had given you. A useful casuistry no doubt, but we don't need it.

We could also combine the first two principles, since people are part of the world. Why should our species get special treatment? I won't try to justify this choice, but I'm skeptical that anyone who claims to think differently actually lives according to their principles.

[2] Confucius was also excluded from public life after ending up on the losing end of a power struggle, and presumably he too would not be so famous now if it hadn't been for this long stretch of enforced leisure.

Thanks to Trevor Blackwell, Jessica Livingston, and Robert Morris for reading drafts of this.

Kent Beck on Empirical Software Design: When & Why

Mike's Notes

An ACM Tech Talk interview yesterday with Kent Beck, author of Tidy First.

Resources

References

  • Reference

Repository

  • Home > Handbook > 

Last Updated

18/04/2025

Kent Beck on Empirical Software Design: When & Why

By: Kent Beck and Margaret-Anne Storey
ACM Tech Talk: 18/04/2025

Kent Beck is an American software engineer and the creator of Extreme Programming, a software development methodology that eschews rigid formal specification for a collaborative and iterative design process. Beck was one of the 17 original signatories of the Agile Manifesto.

Beck pioneered Test-Driven Development, its successor TCR: Test && Commit || Revert, software design patterns, and 3X: Explore/Expand/Extract. He wrote the SUnit unit testing framework for Smalltalk, which spawned the xUnit series of frameworks, notably JUnit for Java, which Beck wrote with Erich Gamma. Beck popularized CRC cards with Ward Cunningham, the inventor of the wiki.

Margaret-Anne Storey is a Professor of Computer Science and a Canada Research Chair in Human and Social Aspects of Software Engineering at the University of Victoria. Together with her students and collaborators, she seeks to understand how software tools, communication media, data visualizations, and social theories can be leveraged to improve how software engineers and knowledge workers explore, understand, analyze, and share complex information and knowledge. She has published widely on these topics and collaborates extensively with high-tech companies and non-profit organizations to ensure real-world applicability of her research contributions and tools.

Since the publication of Parnas' "On the Criteria to Be Used in Decomposing Systems into Modules" we have had good advice on how to design software. However, most software is more difficult to change than it should be and that friction compounds over time. The Empirical Design Project seeks to resolve the seemingly-irresolvable tradeoff between short-term feature progress and long-term optionality, focusing on:

  • How is software actually designed? What can we learn from data about how software is designed?
  • When should software design decisions be made? What is the optimal moment given unclear and changing information & priorities?
  • How can we enhance the survival of software projects while expanding optionality?

Spoiler alert: make design decisions later and in small, safe steps.

Other talks

Tidy First? A Daily Exercise in Empirical Design • Kent Beck • GOTO 2024

Wikipedia Structured Contents

Mike's Notes

Good news from Kaggle and Wikimedia. An opportunity to get structured data.

"...

As part of Wikimedia's mission to make all knowledge freely accessible and useful, Wikimedia is publishing a beta version of its structured content on Kaggle in French and English. This release gives data scientists, researchers, and machine learning enthusiasts a new, streamlined way to explore and analyze this global information resource.

..." - Kaggle.com

Resources

References

  • Reference

Repository

  • Home > 

Last Updated

18/04/2025

Wikipedia Structured Contents

By: Wikimedia Enterprise Team
Wikimedia Enterprises: 16/04/2025

Wikimedia Enterprise has released a new beta dataset on Kaggle, featuring structured Wikipedia content in English and French. Designed with machine learning workflows in mind, this dataset simplifies access to clean, pre-parsed article data that’s immediately usable for modeling, benchmarking, alignment, fine-tuning, and exploratory analysis.

This release is powered by our Snapshot API’s Structured Contents beta, which outputs Wikimedia project data in a developer-friendly, machine-readable format. Instead of scraping or parsing raw article text, Kaggle users can work directly with well-structured JSON representations of Wikipedia content—making this ideal for training models, building features, and testing NLP pipelines.The dataset upload, as of 15 April 2025, includes high-utility elements such as abstracts, short descriptions, infobox-style key-value data, image links, and clearly segmented article sections (excluding references and other non-prose elements). Because all content is derived from Wikipedia, it is freely licensed under Creative Commons Attribution-Share-Alike 4.0 and the GNU Free Documentation License (GFDL), with some additional cases where public domain or alternative licenses may apply.

“As the place the machine learning community comes for tools and tests, Kaggle is extremely excited to be the host for the Wikimedia Foundation’s data. Kaggle is already a top place people go to find datasets, and there are few open datasets that have more impact than those hosted by the Wikimedia Foundation. Kaggle is excited to play a role in keeping this data accessible, available and useful." - Brenda Flynn, Partnerships Lead, Kaggle

As a beta release, this dataset is an invitation to explore, test, and improve. We welcome feedback, questions, and suggestions from the Kaggle community directly in the dataset’s discussion tab.

Get the Dataset

Access the dataset directly on Kaggle

About Kaggle

Kaggle is home to one of the world’s largest communities of machine learning practitioners, researchers, and data enthusiasts. With millions of users and an expansive ecosystem of datasets, notebooks, and competitions—including challenges like the Arc Prize—Kaggle provides an ideal environment for experimenting with open structured data like Wikimedia’s Structured Content. Whether you’re testing a new architecture, evaluating data quality, or building a pipeline from scratch, this Wikipedia dataset is ready to plug into your process.

More info at Google Blog

Neobrutalism: Definition and Best Practices

Mike's Notes

This article by Hayat Sheikh from the NN Group's newsletter is relevant to the Ajabbi Design System. This Design System has a simple, clunky design style, like the web was 20 years ago and will be the default style of the Ajabbi workplace apps, and the Ajabbi website. The UI priority is nice, simple, reliable, fast, secure, and functional.

Users can easily change the style sheets to use their own design system.

Resources

References


Repository

  • Home > Design System >
  • Home > Ajabbi Research > Library > Subscriptions > The NN/g Newsletter

Last Updated

16/04/2025

Neobrutalism: Definition and Best Practices

By: Hayat Sheikh
The NN/g Newsletter: 11/04/2025

Hayat Sheikh, a Senior Designer at Nielsen Norman Group, is celebrated for her award-winning designs and extensive experience from renowned agencies. She also teaches at Lebanese American University, focusing on branding and human-centric design, and manages her NFT collection 'The Self.'

Summary:

As a UI design style, neobrutalism focuses on raw, unrefined elements like bold colors, simple shapes, and intentionally "unfinished" aesthetics.

Emerging as a reaction against sleek, minimalistic designs, neobrutalism creates a striking (almost rebellious) visual style. But while neobrutalism draws attention, designers must carefully balance its distinctive look with usability to avoid ending up with an overwhelming or confusing interface.

Defining Neobrutalism

Neobrutalist website design blends bold colors and sharp contrast for striking interfaces.

Neobrutalism (or neubrutalism), an evolution of traditional brutalism, is a visual-design trend defined by high contrast, blocky layouts, bold colors, thick borders, and “unpolished” elements.

Brutalism vs. Neobrutalism

Brutalism and neobrutalism are both edgy visual-design styles that draw inspiration from the architectural movements they get their names from. In digital design, brutalism tends to appear raw, harsh, unfinished, or utilitarian. Brutalist websites might use plain HTML elements and limited color palettes.

For example, Drudge Report embodies brutalist aesthetics with its barebones HTML structure, monospaced headlines, and rigid table-based layout, evoking the look of the pre-CSS web.


Drudge Report’s website embraces a brutalist style with its stripped-down aesthetic.

In contrast, neobrutalism combines the brutalist design style with nostalgic 90s graphic-design elements. Unlike true brutalist web design, neobrutalist designs are likely to be more colorful and orderly.

A striking example is Look Beyond Limits by Halo Lab, which features oversized typography, bold dividers, thick strokes with a pop of bright colors.

Look Beyond Limits by Halo Lab embraces neobrutalism with its raw, structured layout, and oversized typography.

Characteristics of Neobrutalism

High Contrast and Bright Colors

Neobrutalist designs use bold, primary colors and high-contrast combinations to emphasize key functions and UI elements. This approach introduces striking, contrasting hues to capture attention and enhance visual impact. It also helps users focus on essential elements while creating an unconventional, memorable experience.


99percentoffsale.com embraces neobrutalism through bold, high-contrast colors for a striking visual style.

Thick Lines and Geometric Shapes

This style does not shy away from using thick borders, angular forms, and solid lines that create structure without relying on gradients or shadows.


byooooob.com: Thick borders, solid lines, bright colors, and striking, playful shapes are typical for the neobrutalist visual style.

Stark Drop Shadows

Unlike minimalism, neobrutalism encourages bold, striking shadows instead of soft, layered ones. It incorporates solid, single-color shadows (e.g., a black drop shadow offset by 4px) to add depth while maintaining the "raw" aesthetic.


Unlike minimalist designs, which usually emphasize a flat, simple look and feel, neobrutalism often features bold, solid shadows that create depth while preserving a raw aesthetic.

Bold Type

Neobrutalism promotes the use of bold, “unpolished” elements that often include quirky or slightly eccentric typefaces. Despite their expressive forms, these typeface choices are balanced by a generous use of whitespace, creating a visual rhythm that feels deliberate rather than overwhelming. Typography in neobrutalism serves both as a functional element and as a focal point of the overall design.


Tony’s Chocolonely eCommerce by Tinloof uses bold, quirky typography that reinforces the brand’s personality.

Skeuomorphic Elements

Neobrutalism might incorporate nostalgic elements from early digital interfaces, such as Windows 98-style buttons and monospace fonts. These features create a sense of familiarity while blending retro aesthetics with modern design. For example, a neobrutalist design might use UI elements from an old browser, with traditional iconic buttons and appearance mimicking early web experiences.

cyanbanister.com: Neobrutalism blends retro UI elements (such as Pixel art and old-style  browser windows) with modern design elements (such as contemporary typography and layout).

Examples of Neobrutalism in Practice

Many brands are embracing the bold, raw aesthetic of neobrutalism to create memorable experiences through striking contrasts, unconventional typography, and minimalistic design. This approach reflects a shift toward prioritizing purpose and functionality over excessive polish, allowing brands to stand out in a crowded digital landscape.

Brands like Figma and Gumroad incorporated bold, high-contrast colors and raw elements, with a focus on user experience and simplicity.

Figma's brand refresh, with its use of bold contrasts and unconventional typography, exemplifies neobrutalist design. Just like its tools, the refreshed identity emphasizes creative freedom, flexibility, and a dynamic user experience, allowing users to work in ways that feel authentic and engaging.


Figma’s bold, geometric design reflects creative freedom.

Similarly, Gumroad, an ecommerce platform for independent creators, uses neobrutalism's raw aesthetic to align with its ethos of empowering independent creators. By stripping away unnecessary polish and focusing on functionality over flourish, the platform emphasizes simplicity and accessibility, staying true to its purpose of providing creative freedom and a straightforward user experience.


Gumroad’s raw design empowers creators with simplicity.

Designing with Neobrutalism: Best Practices

While neobrutalism thrives on bold colors, heavy typography, and sharp contrasts, without balance, it can overwhelm users and hinder accessibility. These tips help create designs that are both visually striking and user-friendly.

Design with Usability at the Forefront

Prioritize usability with clear buttons, readable type, and ample whitespace to keep the experience intuitive and accessible, even within a bold, raw aesthetic.

The API World landing page Incorporates a neobrutalist aesthetic while maintaining usability through its clear search functionality and calls to action.

Contrast Ratios Matter

Bold colors must meet text-contrast standards. Avoid pairing vibrant hues like yellow and cyan that fail readability tests. Tools like Coolors' contrast checker ensure that combinations remain accessible while staying visually striking.


Although neobrutalism uses bright, contrasting colors, it still needs to meet readability and accessibility standards.

Limit Your Color Palette

Restrict your palette to 2–3 bold, high-contrast colors (e.g., black, neon green, electric blue) to avoid overwhelming users.


bieffeforniture.it uses 2 main high-contrast colors (electric blue and red) to help maintain clarity and avoid overwhelming users.

Prioritize Readability

Pair bold, unconventional headlines (e.g., a chunky sans-serif font) with clean, neutral body fonts like Roboto or Inter. Avoid overly decorative or condensed typefaces for paragraphs to maintain legibility across devices.

dodonut.com adopts a neobrutalist style while still maintaining clear buttons, readable text, and ample whitespace.

Use Whitespace Strategically

Offset dense geometric shapes and thick borders with generous padding (e.g., 24–32px margins) to create breathing room, prevent clutter, and guide users to key actions or content.


Content in a neobrutalist layout needs enough padding to create space and focus users’ attention on key elements.

Test Interactions

Ensure that interactive elements (buttons, links) remain recognizable. Use underlines on hover or subtle color shifts to indicate state changes. For example, a neon button could lighten on click to signal feedback without gradients or shadows.

Interactive elements in a neobrutalist layout need clear feedback. Use underlines or color shifts to signal interaction.

Avoid Oversimplification

Retain hierarchy through size variation (e.g., headlines twice as large as body text) and color intensity. Even in a minimalistic layout, ensure that clear calls to action and key usability elements stand out to create a seamless user interface.

sui.io/overflow#overview maintains visual hierarchy by using different font sizes for headers, page text, and button labels, thus ensuring that CTAs and interactive elements stand out.

Key Takeaways

Neobrutalism’s rebellious aesthetic can grab attention, but its success hinges on balancing boldness with usability. By grounding the style in accessibility principles and testing with users, designers can create interfaces that are both striking and functional.