Google Reader Would Have Been 21 Today

Mike's Notes

He has a point.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Subscriptions > CFBreak
  • Home > Handbook > 

Last Updated

17/10/2026

Google Reader Would Have Been 21 Today

By: Robert Zehnder
KISDigital: 07/10/2026

Robert Zehnder: I am just this guy, you know?.

...

I saw an article today claiming that reading for just 30 minutes a day can support cognition and well-being, and even help us understand and connect with other people. I agree, but I also think it depends a lot on what you're reading.

These days it's easy to hop on your platform of choice and doomscroll for hours, enjoying all the ads and sponsored posts along the way. Your feed was probably crafted by an algorithm designed to push your emotional buttons and get a reaction out of you. That's how we do things now, but it wasn't always the case.

Back in the early aughts, you actually had to go out and find something to read. It wasn't just piped into your page. It was an age when men were real men, women were real women, and small furry creatures from Alpha Centauri were real small furry creatures from Alpha Centauri.

Then, on October 7, 2005 (twenty-one years ago today), Google launched Google Reader, which let you subscribe to your favorite blogs without trawling the whole internet to keep up with them. Google shut it down on July 1, 2013, citing declining usage, a shift toward mobile news apps, and no real way to monetize it. Mostly, I think, it was because I liked it.

I spent a few years working on Dismal Threads, a Reddit-like forum where I could create bot accounts, give each one a set of RSS feeds to poll, and have it post anything new it found to the forum. Looking back, I think I built a forum application when what I really wanted was a good, old-fashioned feed reader.

So what would that feed reader look like if I built it today? As it turns out, it would look like this:

feedhouse

What it does

The short version: you pick the sources, it shows you what's new in the order it was published, and nothing ranks your feed for you.

  • Feeds: RSS and Atom, which covers more than you'd think: YouTube channels, podcasts, subreddits, GitHub, Mastodon and Bluesky. Paste a page and Feedhouse finds the feed. OPML import and export, so you can leave whenever you like.
  • Reading: unread and starred, folders, oldest or newest first, and comfortable, compact or card views. For feeds that only send a summary, it fetches the full article. Keyboard shortcuts for the j/k crowd.
  • Read later: save any link, highlight passages, attach private notes, and export your highlights as Markdown for Obsidian.
  • Search: full-text across everything you follow and save. Pin a search to the sidebar and it gets its own unread count.
  • People: follow other readers, share items with a note, and comment. It's the social layer Reader had before Google bolted it onto Google+ and then took it away.
  • On a phone: an installable PWA with offline reading, swipe gestures, pull to refresh and push notifications.
  • Privacy: feed HTML is sanitized on the server, and images load through Feedhouse's own proxy, so publishers never see your IP address.
  • It's built on BoxLang with BoxExpress on the server and React on the front end, backed by MySQL.

Sign-ups are open. Bring your OPML.


If you are ready to follow all of your favorite ColdFusion bloggers you can follow this bundle: https://feedhouse.app/b/toQxcm3YHxnA

How Does Life Unfold? A Landscape Metaphor Comes Into Its Own

Mike's Notes

Excellent article by Phillip Ball in a recent issue of Quanta Magazine.

Important insights from biology. Highly usable within Pipi for fitness landscapes. Could be combined with Hilbert spaces. To be worked on and added in a future minor release.

I'm fascinated. The image below of mouse embryonic development is very similar to how Pipi grows. Must be on the right track.😎

Resources

References

  • The Strategy of the Genes by C.H. Waddington. Routledge. 1957.  ISBN 9781315765471

Repository

  • Home > Ajabbi Research > Library > Subscriptions > Quanta Magazine
  • Home > Handbook > 

Last Updated

16/10/2026

How Does Life Unfold? A Landscape Metaphor Comes Into Its Own

By: Phillip Ball
Quanta: 09/01/2026

Phillip Ball: Contributing Writer.

...

C.H. Waddington’s powerful image of embryonic stem cells specializing on a rolling landscape has captivated biologists since the 1950s. Experimental data is finally confirming, and complicating, his visionary ideas.

In this update to Waddington’s image, a ball (representing a cell lineage) multiplies and specializes into cell types (represented by color) as it traverses a dynamic landscape. This animation was generated from Waddington’s original drawing using an AI tool.

Mark Belan/Quanta Magazine

By the middle of the 20th century, it had begun to seem that biology was almost solved. Charles Darwin’s theory of evolution by natural selection explained how organisms change and adapt. The modern science of genetics showed how it works at the molecular scale. Genes governing the traits of organisms get passed down from parent to offspring, and random mutations create the variations from which natural selection picks the “fittest.” Natural selection and genetics fitted together in what the biologist Julian Huxley christened “the modern synthesis” in his 1942 book. Once it was shown in 1953 that the genes are encoded by DNA, the rest of biology looked like little more than piecing together details.

But not everyone was satisfied. The British biologist Conrad Hal Waddington, known to his friends and colleagues as Wad, thought this focus on genes was all very well. But it wasn’t clear to him, or anyone else, exactly how genes shape the forms and features of organisms — how they reliably generate all the different tissues of the body, in all the right places, during embryonic development. Around the same time that Huxley unveiled the modern synthesis, Waddington presented a novel picture of how this might unfold.

He visualized the developmental process as a landscape with hills and valleys that split every so often like those in a river network. At the very top of the highest hill he imagined a ball, which represented a population of cells in their earliest embryonic form — what we now call stem or pluripotent cells, which have the potential to become any cell type. The progression of the cells towards their fates — to become, say, skin cells, muscle cells, or nerve cells — is like the ball rolling downhill through the landscape.

When the ball reaches a branching point (bifurcation), the model’s “gravity” pulls it to one track or the other: In scientific terms, it must differentiate. Through a particular sequence of such branching decisions, Waddington argued, cells specialize into their mature types, or fates, each expressing a particular set of genes. The cells are restricted to a small number of well-defined states because they are “canalized,” in Waddington’s lexicon: trapped and channeled by the sides of the valley. In this way, a limited number of cell types reliably arise from the activity of an army of genes.

The biologist Conrad H. Waddington’s prescient ideas shaped the modern understanding of gene regulation, epigenetics, and evolutionary developmental biology. He died in 1975.

Walter Stoneman, National Portrait Gallery London

Waddington’s landscape has been “remarkably useful as a conceptual scaffold,” said James Briscoe, a developmental biologist at the Francis Crick Institute in London. “The core ideas — that development is progressive, that cell states are distinct, that bifurcations represent [cell] fate decisions, that canalization implies robustness — all survive.”

“There’s so much richness to some of the concepts Waddington was trying to share,” said Susanne Rafelski, a biochemist at the Institute for Stem Cell and Regenerative Medicine in Seattle.

But the concept was more of a visual metaphor than a representation of an actual biological process. Or so it seemed. In the past several years, researchers have mapped out the real topography of cell-state spaces — in effect, Waddington’s landscapes — from experimental data collected from many thousands of cells over the course of embryonic development. Those analyses are revealing that development is not a mere readout of a genetic program, but rather a dynamic process in which communities of cells build themselves, and the very landscape they navigate, by mutual negotiation and interaction, into an organism.

This cartography of development is now helping researchers understand how identical cells in the early embryo develop into the distinct tissues and cell types of a complex organism. This matters enormously for regenerative medicine and stem-cell engineering, Briscoe said: “If you understand the landscape topology and know where the bifurcations lie, you can in principle design methods that steer cell populations to desired states with precision, rather than by trial and error.”

Waddington’s metaphor, then, could be the key to understanding and reshaping possibilities for what cells, tissues, and embryos can be.

Charting a Landscape

In the 1940s, genetics and embryology were separate sciences; not everyone even believed that genes played a significant role in development. Yet Waddington’s own experiments in embryology, and those of others, convinced him that the formation and patterning of tissues in an embryo were indeed controlled by genes. The cells of different tissues had different groups of genes activated in their chromosomes, he thought. A process of differentiation gradually specialized cells into skin cells, nerve cells, and so on.

Waddington figured that the developmental pathways — for example, the formation of the neural tube from a layer of embryonic tissue called ectoderm, which ultimately develops into the central nervous system — are inevitable once the process has begun, just as water flowing down a river valley is constrained by its surroundings. The path might meander a little, but the valley keeps the river on course. Differentiation corresponds to the branching of a valley, and the final destinations are the mature cell types of the body.

Waddington’s classic drawing of the epigenetic landscape. A ball, representing a pluripotent cell or population, is poised to roll downhill into valleys, each of which represent a specialized cell type, such as a blood cell, liver cell, or brain cell.

From The Strategy of the Genes by C.H. Waddington

Waddington visualized this as a landscape in drawings, but they had “no grounding in physical reality,” wrote Scott Gilbert, a developmental biologist at Swarthmore College in Pennsylvania, in a 1991 essay in Biology & Philosophy. They were useful schematics for thinking about the problem of development, and nothing more.

“Without mathematical content,” Briscoe said, the metaphor “could not distinguish between alternative mechanisms, make quantitative predictions, or be falsified.” As a result, he said, Waddington’s landscape “has sometimes become a cliché rather than a meaningful explanation.”

What, for example, determines the topography of the hills and valleys? In his 1957 book The Strategy of the Genes, Waddington depicted the landscape as he figured it might look from underneath: as a sheet that is tugged into shape by a network of ropes attached to pegs. The pegs represented individual genes, and the ropes their effects on development. Expressing a particular gene — turning it into its corresponding protein — is like pulling on its ropes to change the shape of the sheet.

What determines the landscape’s shape? Waddington sketched a network of pegs and ropes beneath the rolling hills; the pegs are genes, and the ropes are their interconnections. Together they shape the landscape above and represent what we now call gene regulatory networks.

From The Strategy of the Genes by C.H. Waddington

It’s rather more complex than that, Waddington realized, because the ropes are connected in a network. Any one of them might influence the landscape at several points, and any given point on the landscape might be attached to several ropes.

These hidden connections correspond to what researchers now call gene regulatory networks: interactions among genes whereby an increase in the expression of one might change, or regulate, the activity of others. Herein lies the cryptic complexity of development. A given process, such as formation of the neural tube, might be influenced by many interacting genes; there’s no simple relationship between genes (genotype) and the developmental landscape that determines form (phenotype). Gene regulatory networks mediate between them.

It makes no sense, then, to look for genes dedicated to creating specific tissues, organs, or structures in a whole organism, which is one reason Waddington’s metaphor proved useful. The landscape image was “valuable in providing an alternative to a purely gene-centric view of development,” Briscoe said. By emphasizing the landscape’s shape, it pointed “toward system-level properties that cannot be read off from any single gene.”

"Given that the channels and spheres had no physical reality, what was an embryologist supposed to do with them?" - Scott Gilbert, Swarthmore College

Gene regulation wasn’t understood when Waddington first devised his landscape and rope network. A few years later, in the early 1960s, it became clear that one gene could turn another on or off. Researchers, such as the complexity theorist Stuart Kauffman, began to construct simple mathematical models of the networks of gene interactions. But too little was then known about real gene networks to connect abstract theory to experiment. “Given that the channels and spheres had no physical reality,” Gilbert wrote, “what was an embryologist supposed to do with them?”

Answers have begun to emerge over the past two decades thanks to new experimental tools for characterizing cell states. Biologists are now finally becoming able to map experimental data to a real mathematical landscape for differentiation and show just how prescient Waddington was.

Fated Attractors

One way to define the state of a given cell in an embryo is by the expression levels of its genes. These levels can now be measured simultaneously in many cells using a technique called single-cell RNA sequencing, which supplies a snapshot of all the different RNA molecules each cell contains. An RNA molecule (or transcript) is a kind of copy of a gene used to translate it into a functional protein, and generally, more RNA transcripts means higher expression of that gene. Each cell type is characterized by particular gene-expression settings, which are inherited when a cell divides. This ensures that a liver cell will stay a liver cell as it progresses through an organism’s development process.

In principle, RNA-sequencing data can be modeled as a high-dimensional mathematical space in which each axis denotes the number of RNA transcripts of a single gene. Such a plot, with maybe thousands of dimensions to represent thousands of genes, is impossible to visualize, but it can be mathematically projected onto a space with fewer dimensions, usually just two, to produce something like the shadow of a complex 3D object.

On such a plot, called a UMAP (uniform manifold approximation and projection)(opens a new tab), different cell types appear as clusters of points — blood cells cluster together, say, as do cells of the muscle or forebrain — as they share a gene expression profile. Cell lineages follow paths through this map as development proceeds. When the data is mapped through time — in what’s known as a network flow model — it looks very much like a population of cells rolling through a Waddington-like landscape, being channeled along valleys that lead to basins that correspond to distinct cell types.

A Landscape of Embryonic Development

Mark Belan/Quanta Magazine; Modified from  with permission of the authors

We should be wary of supposing, though, that this gene-expression map is literally Waddington’s landscape. Julie Theriot, a biophysicist at the University of Washington, cautioned that single-cell RNA sequencing is not the only or even the best way to characterize cell states. The technique was “mind-blowing” at first, she said, but RNA transcripts don’t map perfectly to gene expression. Plus, when researchers collapse the data into low-dimensional maps, they often do so in ways that reflect prior assumptions about how cells cluster into different types.

Still, it’s clear that, as Waddington supposed, cells undergo changes in state, defined by which genes are active or which proteins are made, as they mature and develop, and that these changes have a trajectory through time that carries them toward a limited number of final states. So how is that landscape of possibilities shaped? What governs the paths it offers?

"We think this reflects something real about how gene regulatory networks are organized." - James Briscoe, Francis Crick Institute

In 2007, the biologist Sui Huang, now at the Institute for Systems Biology in Seattle, described a bifurcation in cell state of the sort proposed by Waddington. He found that blood-forming cells called myeloid progenitor cells differentiate into two specialized types, setting them on course to become red or white blood cells, in a process dominated by two proteins, GATA1 and PU.1. This landscape of cell differentiation can thus be represented with just two values: the concentrations of these two proteins. More GATA1 promotes the formation of red blood cells, while more PU.1 sends the cell toward a white-blood-cell fate.

Huang and his colleagues mapped out the landscape using data from RNA-sequencing experiments and theoretical calculations. At first there is just a single basin, corresponding to the pool of myeloid progenitor cells. But as differentiation proceeds, this basin becomes less stable — less deep — relative to two new adjacent basins, which correspond to the red (high GATA1) and white (high PU.1) blood-cell states. Think of it like a sheet suspended horizontally from its corners, with water pooled in the middle. If you push up on the pool from below, the water flows out sideways toward new, lower pools on either side. These basins are what mathematicians call attractors: states toward which the cells are inevitably drawn, like water following gravity across a landscape.

The biologist Sui Huang has found that blood cell differentiation can be mapped like a real epigenetic landscape, with changes in gene activity altering the shape of the landscape, resulting in an output: red or white blood cell.

Allison Kudla

Researchers have now documented many cell-fate decisions(opens a new tab) that can be described in this way: as changes in gene activity that alter the shape of a landscape. The changes produce new attractors that correspond to stable cell types in the low-lying valleys; unstable gene-activity configurations constitute the high ground.

Briscoe is part of a research group that has pursued the landscape idea using the language of dynamical systems theory, which explores how systems described by sets of interacting variables evolve. “Our work starts from Waddington’s metaphor,” said David Rand), a mathematician at the University of Warwick in the United Kingdom, who collaborates with Briscoe. It’s more than a convenient image, he said: It “reveals something [fundamental] about the structure of developmental systems.”

Combining experiments and theory, they too have found that a small number of key genes drive cell-fate decisions. The rest of the network enacts the decision, as other genes are activated or suppressed farther downstream, but isn’t active in it. “We think this reflects something real about how gene regulatory networks are organized,” Briscoe said.

This makes sense from an evolutionary perspective. For any multicellular organism, the various cell types must be reliably generated and stable. Gene regulatory networks that have deep, well-separated attractors will be selected for, Briscoe said.

These deep wells represent canalization of cell-fate decisions in the way Waddington supposed. The molecular world is noisy, filled with random fluctuations. Two cells of the same type will inevitably have slightly different levels of gene expression at any moment. In the landscape picture, they don’t have to occupy the exact same spot. But so long as a group of cells is in the same basin, they will all follow the same basic trajectory.

“If fate decisions were highly sensitive to any molecular fluctuation,” Briscoe said, “development would not be robust.”

Forces of Nature

Waddington’s alluringly intuitive view left some open questions. What does the height of the landscape actually represent? And what’s the developmental equivalent of time passing as his balls roll down the slopes?

Briscoe and Rand’s dynamical-systems view provides some answers. It suggests that the landscape’s height reflects the stability of the cells’ states, with the least stable states on the highest peaks and the most stable in the lowest valleys. Time, meanwhile, is not literal time, but a kind of “pseudo-time” that reflects how the gene-expression profiles of all the cells change. In theory, all the cells can be ordered along a single pseudo-time axis so that the greater the change in a given cell’s state, the farther along the axis it is. But these changes won’t all be in sync, so there’s no ticking clock that applies to them all at any instant — hence, pseudo-time.

The biologist James Briscoe has found that a small number of key genes determine whether a cell specializes into a certain cell type, such as a brain or liver cell. Those genes then activate or suppress other genes farther downstream in the network.

Dave Guttridge/The Photo Unit

The trouble is that this notion of time doesn’t always work, Rand said. It fits when cells are crossing over high, unstable points in the landscape. But when they are in a low-lying attractor basin, their expression profiles don’t settle into a single, stable pattern but rather seem to evolve more randomly than systematically, as if “time” meanders.

And what plays the role of gravity in this picture? What is the force that moves cells along their development pathway? “In developmental biology, gravity is [equivalent to] the inevitable progression of differentiation in multi-celled organisms, starting from a small number of cell types,” Rafelski said. This process seems to have an inexorable direction and impetus. “Most of the time, cells follow a predictable order in which they differentiate,” Theriot said. But that order is not programmed into the genome(opens a new tab); after all, the cells in an organism all have the same genome. Rather, the cell-fate decisions are made collectively, as cells interact with and communicate with one another through chemical signals that are read at the cell surface, and through the tugging and squeezing on cell membranes that takes place as tissues grow and fold.

“In development, there’s always feedback,” Theriot said, “and things [in the cell] can adjust depending on inputs from the outside.”

"It is as though the landscape is constantly being reshaped by underlying tectonic forces".

So while Waddington’s landscape looked like a static territory waiting to be traversed, the real landscape changes as cells develop. “In our framework, the landscape is a feature of each cell and is not fixed,” Rand said. “Attractors appear and disappear through bifurcations, and the routes connecting them change.” It is as though the landscape is constantly being reshaped by underlying tectonic forces. Waddington’s rope network, you might say, is itself in constant motion, pulling the sheet this way and that.

In this respect, Rand said, Waddington’s picture was incomplete. It was never really a kind of universal gravity that made the ball roll; rather, cell lineages all move through a constantly shifting landscape in the process of life’s unfolding.

In such ways, modern data has both confirmed and complicated Waddington’s powerful metaphor. Combined theoretical and experimental approaches have helped to elucidate the complex but vital process through which the cells of multicellular organisms like us navigate a path from all-purpose, pluripotent stem cells to well-defined and specific tissues. Briscoe, for instance, has found that in neural-tube patterning there are two ways of reaching the same place(opens a new tab) in the landscape — a finding that reconciled previously contradictory observations. His team could not have made sense of their results without the landscape framework, he said.

Huang is now applying the landscape picture to the development of cancers. The traditional perspective is that cancer cells are malfunctioning, generally because gene mutations have damaged cell division so that it proceeds unchecked. It’s a picture that sees cancer as an aberrant state. But Huang regards it as just another attractor in the landscape — albeit a potentially catastrophic one — that can be all too easily accessed by many different routes. In this view, becoming cancerous is just one of the possible things that our cells do: an inevitable consequence, you might say, of being a multi-tissue organism.

This doesn’t mean, however, that there’s nothing we can do about it. Once we view cancer as an attractor state, a new option becomes possible: to guide those cells back out of the cancer basin and into another that is more benign — one where the cells do nothing, undergo spontaneous cell death, or even regain a healthy state. “Rather than just saying we need to kill them all,” Theriot said, “the idea is: Can we drive them to differentiate?”

Such control of landscape trajectories might also be used for tissue regeneration, or for transforming one cell type into another — for example, to regrow damaged nerves. There could be uses in agriculture as well, for selectively enhancing edible parts of plants, Theriot said.

Briscoe said that “the landscape framework provides a rational basis” for this kind of developmental design, opening up the promise of a “generative” biology in which tissues and possibly organisms can be sculpted to order. In that case, Waddington’s landscape model is far more than metaphor — it could be an atlas of a hitherto uncharted terrain.

Mentorship Cafe [GFS Rising Founders]

Mike's Notes

I had to get up yesterday morning at 3am (NZ Time) to attend the Mentorship Cafe organised by Google. I learned a lot from the mentors. Thanks for the help, guys.

Resources

References

  • Reference

Repository

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

Last Updated

16/10/2026

Mentorship Cafe [GFS Rising Founders]

By: Mike Peters
On a Sandy Beach: 15/10/2026

Mike Peters: Mike invented and designed Pipi and founded Ajabbi.

...

Google for Startups (GFS) Rising Founders Community is a global initiative Google created to support high-potential tech startup founders.

I have been attending some of it from New Zealand, as long as the hours aren't in the middle of the night. It has been useful.

Yesterday, there was a 90-minute Mentorship Cafe. I had applied to attend and was successful. There were two 30-minute one-on-one sessions with a mentor. It was excellent; this is what I learned from Georg, Nsikak and Kennedy.

Context

Ajabbi is mission-led, bootstrapped, with no investor funding planned. All profits go to a non-profit foundation. Its SaaS product, Pipi, solves a very hard, expensive problem. There is no competition. The algorithms and maths involved require top-notch talent.

My questions

How do I recruit a remote workforce for the mission? How do I know that I have found the right people? How do I connect directly with Google DeepMind scientists, since connecting Pipi to Gemini will be a 2-way experiment by both teams?

Suggestions from mentors

  • Build a community first.
  • Grad students want a project anyway.
  • Creds on their CV for career building.
  • Internship program.
  • Be associated with a big name (University, etc.).
  • Need to connect to a senior Google scientist who understands what Mike is talking about.

Discussion

  • Ajabbi is using "Honey Traps" to attract people with the right mindset/talent. They all have to prove themselves; all the work is frontier and hard.
  • Pipi doesn't use LLM vectors, skills, transformers, or harnesses. It is based on how a biological cell works, so it uses different algorithms. High-level mathematicians are needed. MCP may not work here.

Actions

  • Update Stealth Mode plan

The Martians

Mike's Notes

The Martians is the working title for a long-term publishing and associated screen project currently in Development.

With help from Google Search AI Mode, here is some historical background on some of the main characters (some of whom appeared in Christopher Nolan's film Oppenheimer). This project will be self-funded by the future Ajabbi Foundation.

This project exists because Pipi uses much of the maths and science these people developed.

I read Ananyo Bhattacharya's excellent book, The Man from the Future: The Visionary Life of John von Neumann, last month while researching Hilbert Spaces to add to Pipi in a future release.

The top secret sneaky plan

As part of the forthcoming Pipi documentation going on the Ajabbi websites, these scientists and mathematicians will be featured alongside their insights, including references to read, embedded video, and Jupyter Notebooks. This will happen early on.

As resources allow, this effort will expand to include other scientists of the period, including Einstein, Boltzmann, Planck, Noether, etc., historical reenactments with actors, and the factual historical factors at play.

This science communication resource will be made freely available to all, and can also be used for teaching, exhibitions, documentaries and historical drama for TV, etc.

This project is well underway. Redworks will be an initial development vehicle once we quickly sort out some minor legal and tax issues.

Resources

References

  • The Man from the Future: The Visionary Life of John von Neumann by Ananyo Bhattacharya. Penguin (2022).
  • Macrae, Norman (1992). John von Neumann: The Scientific Genius Who Pioneered the Modern Computer, Game Theory, Nuclear Deterrence, and Much More. Pantheon Press. p. 33. ISBN 0-679-41308-1.
  • Marx, George (2001). The Voice of the Martians: Hungarian Scientists Who Shaped the 20th Century in the West. Budapest: Akadémiai Kiadó. ISBN 963-05-7830-1. OCLC 48621487.

Repository

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

Last Updated

16/10/2026

The Martians

By: Mike Peters
Redworks: 13/10/2026

Mike Peters: Mike invented and designed Pipi and founded Ajabbi.

...

The Martians is a working title for a publishing and associated screen project under development. It is about how a group of Hungarian Jews revolutionised mathematics and physics between the French Revolution and WW2. After the revolutions of 1848, the slow decay of the Austro-Hungarian Empire led to WWI, then to the Russian Revolution, the Stalinist counter-revolution, anti-semitism and the rise of Hitler. The project ends with the start of World War II.

The sudden explosion of genius from late 19th and early 20th-century Budapest is one of the greatest intellectual mysteries of modern history. Historians generally agree that it wasn't a coincidence, but rather the result of a highly specific "perfect storm" of political, educational, and cultural factors unique to the Austro-Hungarian Empire.

Here are the primary reasons why this specific environment bred such extraordinary minds:

1. The Legendary High Schools (Gimnáziums)

The Hungarian secondary education system at the time is widely considered one of the best in human history. Following reforms in the late 19th century, the state established gimnáziums (high schools) modelled after the rigorous German classical system, but with a heavier emphasis on mathematics and hard sciences.

  • Elite Teachers: Because university positions were limited, many world-class scientists and mathematicians taught at the high school level.
  • The "Fasori" Phenomenon: Schools like the Fasori Evangélikus Gimnázium produced John von Neumann and Eugene Wigner in the exact same generation.

2. A Hyper-Competitive Culture of Math

Hungary turned mathematics into a highly prestigious, nationwide competitive sport.

  • The KöMaL Journal: Founded in 1894, this monthly high school mathematics and physics journal published incredibly difficult, creative problems. Students from all over the country mailed in their solutions, which were graded and published. This created a national, collaborative network of young geniuses who pushed each other to their absolute limits before ever reaching university.
  • The Kürschák Competition: This annual, blind-graded mathematics competition identified the country's top talent, turning young mathematicians into national celebrities within academic circles.

3. Jewish Emancipation and the "Golden Age" of Budapest

Following the Austro-Hungarian Compromise of 1867, Jews in the empire were granted full civil rights. This triggered a massive wave of urbanisation, and Budapest quickly grew into a booming, wealthy metropolis.

  • The New Middle Class: Barred from traditional aristocratic roles like landownership or politics, the newly emancipated Jewish population poured their wealth and energy into education, medicine, science, and industry. Most of the "Martians" came from this highly driven, affluent Budapest Jewish bourgeoisie, where intellectual achievement was viewed as the ultimate status symbol.

4. The "Budapest Coffee House" Culture

Much like Vienna, Budapest developed a vibrant coffee house culture. Intellectuals, writers, artists, and scientists did not lock themselves in laboratories; they spent their afternoons in cafes like the New York Café or Café Centrál. Ideas from physics, psychology, literature, and economics were fiercely debated across disciplines, fostering lateral thinking, intense debate, and intellectual agility.

5. A State of Creative Anxiety

The "Martians" grew up in a world of profound instability. They witnessed the collapse of the Austro-Hungarian Empire, a communist revolution, a Stalinist counter-revolution, hyperinflation, and the rapid rise of virulent anti-Semitism and Fascism.

  • This created what Eugene Wigner called a "feeling of extreme insecurity" and an awareness that everything they owned could be taken away—except what was inside their minds.
  • This background forced them to be adaptable, highly driven, and comfortable with chaos, traits that proved invaluable when they later had to solve unprecedented problems in wartime America.

"The Martians" (Hungarian: A marslakók) was a nickname for a group of exceptionally brilliant Hungarian physicists and mathematicians who emigrated to the United States in the early 20th century. Most were secular Jewish refugees fleeing Nazi expansion and rising anti-Semitism in Europe.

The name originated as a joke among colleagues like Enrico Fermi and Leo Szilárd. When discussing the Fermi Paradox—asking why there is no evidence of intelligent extraterrestrial life—Szilárd quipped that aliens were already here, but they simply disguised themselves as Hungarians. The moniker stuck because these scientists possessed seemingly superhuman intellects, all grew up within walking distance of each other in Budapest, and spoke English with a thick, matching accent.

Core Members of "The Martians"

While the wider group included up to 23 thinkers, the core group of five distinct "Martians" reshaped modern physics, defence, and computing:

  • John von Neumann (1903–1957): Widely considered one of the greatest mathematicians of the 20th century.
  • Leo Szilárd (1898–1964): The visionary physicist who conceived the nuclear chain reaction.
  • Edward Teller (1908–2003): Theoretical physicist known historically as the "father of the hydrogen bomb".
  • Eugene Wigner (1902–1995): Theoretical physicist who won the Nobel Prize in Physics in 1963.
  • Theodore von Kármán (1881–1963): A pioneer in aerodynamics and mathematics.
Others included:
  • Denis Gabor: A physicist who won the 1971 Nobel Prize in Physics for inventing holography.
  • John G. Kemeny: A mathematician and computer scientist who co-developed the BASIC programming language.
  • George Pólya: Mathematician
  • Paul Erdős: One of the most prolific mathematicians in human history, known for his eccentric lifestyle and work in combinatorics and number theory.
  • Cornelius Lanczos:
  • Egon Orowan:
  • Franz Alexander:
  • George de Hevesy:
  • George Olah:
  • John Harsanyi:
  • John Polanyi:
  • Paul Halmos:
  • Paul Neményi:
  • Peter Carl Goldmark:
  • Peter Lax:
  • Valentine Telegdi:

Impact on Science and Mathematics

The Martians did not just contribute to their fields; they laid the bedrock for the technology, national security, and computational infrastructure of the modern world.

  • The Von Neumann Architecture: John von Neumann designed the framework for modern digital computers. He pioneered the system in which data and program instructions are stored in the same memory space—a fundamental structure that nearly all desktop computers, smartphones, and servers still use.
  • Cellular Automata: Von Neumann created the concept of cellular automata, modelling self-reproducing systems on computer screens before the biological role of DNA was even fully understood.
  • The Nuclear Chain Reaction: In 1933, Leo Szilárd conceived the idea of a neutron-driven nuclear chain reaction and patented it.
  • The Manhattan Project: Recognising the threat of Nazi Germany, Szilárd drafted the famous Einstein–Szilárd letter to President Franklin D. Roosevelt, which sparked the creation of the Manhattan Project. Von Neumann, Wigner, and Teller all performed core calculations that made the atomic bomb a reality.
  • Thermonuclear Weapons: Post-WWII, Edward Teller drove the physics and design behind the first hydrogen bomb, fundamentally changing Cold War geopolitics.
  • Aviation & Space Flight: Theodore von Kármán provided the mathematical and scientific foundation for modern aerodynamics. He discovered the Kármán vortex street (fluid dynamics) and helped establish the U.S. Air Force’s research wing.
  • JPL Founding: Von Kármán later co-founded NASA's legendary Jet Propulsion Laboratory (JPL).
  • Game Theory: John von Neumann co-created mathematical Game Theory, publishing Theory of Games and Economic Behaviour. This framework mathematically analyses strategy, risk, and decision-making, transforming modern economics, evolutionary biology, and military strategy.
  • Quantum Mechanics: Eugene Wigner introduced Group Theory into quantum mechanics. His work on the symmetries of atomic nuclei earned him a Nobel Prize.
  • Heuristics and Education: George Pólya wrote How to Solve It, a foundational text that systematically defined how to approach and teach mathematical problem-solving.

SPDX License List

Mike's Notes

A fantastic resource. Will use it to sort out open-source licensing.

"System Package Data Exchange (SPDX, formerly Software Package Data Exchange) is an open standard capable of representing systems with digital components as bills of materials (BOMs).[2] First designed to describe software components, SPDX can describe the components of software systems, AI models, software builds, security data, and other data packages. SPDX allows the expression of components, licenses, copyrights, security references and other metadata relating to systems.[3]

The original purpose of SPDX was to improve license compliance,[4] and it has since been expanded to facilitate additional use cases such as supply-chain transparency and security.[5] SPDX is authored by the community-driven SPDX Project involving key industry experts, organizations, and open-source enthusiasts under the auspices of the Linux Foundation.

The SPDX specification is recognized as the international open standard for security, license compliance, and other software supply chain artifacts as ISO/IEC 5962:2021. As of August 2025, the latest version of the standard has been 3.0.1.[1]" - Wikipedia

Legal advice

Edwin Lim, a lawyer at Hudson Gavin Martin (HGM), is my go-to for licensing advice.

Resources

References

  • ISO/IEC 5962:2021

Repository

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

Last Updated

13/10/2026

SPDX License List

By: 
SPDX: 16/09/2026

...

The SPDX License List is an integral part of the SPDX Specification. The SPDX License List itself is a list of commonly found licenses and exceptions used in free and open or collaborative software, data, hardware, or documentation. The SPDX License List includes a standardized short identifier, the full name, the license text, and a canonical permanent URL for each license and exception.

The purpose of the SPDX License List is to enable efficient and reliable identification of such licenses and exceptions in an SPDX document, in source files or elsewhere.

License Exceptions are commonly found exceptions to free and open source licenses, used with the License Expression operator, "WITH" to create a license with an exception.

The matching guidelines define what constitutes a license or exception match. The license text on the HTML pages here will display omitable text in blue and replaceable text in red (see Guideline #2 for more information).

Explanation of fields used on the SPDX License List

  • License inclusion principles for adding new licenses or exceptions to the SPDX License List
  • Contribute to the project or request a new license
  • Use short identifiers in your source code
  • Github repo
  • Machine readable data files for the SPDX License List

[Example of data]

Note: You can sort by each column by clicking on the column header. By default, the table sorts by the Identifier column.

Full name Identifier FSF Free/Libre? OSI Approved?
BSD Zero Clause License 0BSD Y
3D Slicer License v1.0 3D-Slicer-1.0
Attribution Assurance License AAL Y
Abstyles License Abstyles
AdaCore Doc License AdaCore-doc
Adobe Systems Incorporated Source Code License Agreement Adobe-2006
Adobe Display PostScript License Adobe-Display-PostScript
Adobe Glyph List License Adobe-Glyph
Adobe Utopia Font License Adobe-Utopia
Amazon Digital Services License ADSL
Advanced Cryptics Dictionary License Advanced-Cryptics-Dictionary
Academic Free License v1.1 AFL-1.1 Y Y
Academic Free License v1.2 AFL-1.2 Y Y
Academic Free License v2.0 AFL-2.0 Y Y
Academic Free License v2.1 AFL-2.1 Y Y
Academic Free License v3.0 AFL-3.0 Y Y
Afmparse License Afmparse

Deprecated License Identifiers

SPDX endeavors to never change the SPDX license identifiers. However, sometimes there has been a compelling reason to deprecate a license identifier, such as to accommodate improved SPDX license expressions or when we have found a duplicate license. When a license identifier is "deprecated" on the SPDX License List, it effectively means that there is an updated license identifier and the deprecated license identifier, while remaining valid, should no longer be used. The URL to each deprecated license is retained and those license pages are updated to note the deprecation. Some reasons for deprecation are as follows:

  • Release 2.0 of the SPDX Specification introduced License Expressions that supports the ability to identify common variations of SPDX-identified licenses without the need to define each potential variation as a distinct license on the SPDX License List. This new syntax supports the ability to declare an SPDX-identified license exception using the "WITH" operator (e.g. GPL-2.0-or-later WITH Autoconf-exception-2.0), as well as the ability to use a simple "+" operator after a license short identifier to indicate "or later version". SPDX has defined a list of license exceptions to use after the "WITH" operator. As a result, a number of licenses formerly included on the SPDX License List have been deprecated, and correct usage employs the License Expression syntax as of v2.0.
  • Release 3.0 replaced previous Identifiers for GNU licenses with more explicit Identifiers to reflect the "this version only" or "any later version" option specific to those licenses. As such, the previously used Identifiers for those licenses are deprecated as of v3.0.
  • Other licenses may have been deprecated for the reasons noted.

[Example of data]


Full name Identifier Deprecated as of:
Affero General Public License v1.0 AGPL-1.0 3.1
GNU Affero General Public License v3.0 AGPL-3.0 3.0
BSD 2-Clause FreeBSD License BSD-2-Clause-FreeBSD 3.10
BSD 2-Clause NetBSD License BSD-2-Clause-NetBSD 3.9
bzip2 and libbzip2 License v1.0.5 bzip2-1.0.5 3.16
eCos license version 2.0 eCos-2.0 2.0rc2
GNU Free Documentation License v1.1 GFDL-1.1 3.0
GNU Free Documentation License v1.2 GFDL-1.2 3.0
GNU Free Documentation License v1.3 GFDL-1.3 3.0

Software Engineering at Google

Mike's Notes

Discovered this gem via the DORA Community. You can buy the 602-page book from O'Reilly, and you can read an HTML copy for free online at Abseil.

The book is CC BY-NC-ND 4.0

"About Abseil

Abseil is an open source collection of C++ libraries drawn from the most fundamental pieces of Google’s internal codebase. These libraries are the nuts-and-bolts that underpin almost everything Google runs. Bits and pieces of these APIs are embedded in most of our open source projects, and Abseil aims to bring them together into one comprehensive project. Abseil encompasses the most basic building blocks of Google’s codebase: code that is production-tested and will be fully maintained for years to come.

Our primary purpose in releasing Abseil is to more easily support Google open source projects sharing their C++ code outside of Google. In some cases, Abseil provides pieces missing from the C++ standard; in others, Abseil provides alternatives to the standard for particular use cases we’ve needed in the Google codebase. We denote those cases clearly within the library code we provide you.

Abseil is not meant to be competitor to any standard library code; we’ve just found that many of these utilities serve a purpose within our codebase, and we now want to provide those resources to the C++ community as a whole."

Resources

References

  • Software Engineering at Google curated by Titus Winters, Tom Manshreck, and Hyrum Wright, O'Reilly. 2020.

Repository

  • Home > Ajabbi Research > Library > Subscriptions > DORA Community
  • Home > Handbook > 

Last Updated

12/10/2026

Software Engineering at Google

By: Titus Winters, Tom Manshreck and Hyrum Wright
Abseil: 01/03/2020

Titus Winters: Senior Principal Scientist at Adobe. C++ Libraries Lead for Google. Founder of Abseil (http://abseil.io). C++ Standards Committee member, chair for Library Evolution Working Group (design for the C++ standard library). Google C++ Style Guide co-maintainer.  Teacher, author.

Tom Manshreck: Education engineer with deep programming experience. Experienced Principal Program Manager and Staff Technical Writer. Have worked on both internal and external projects at Google for 19 years, including as a manager of 12 individuals, a tech lead for a company-wide series of internal programming manuals, and external REST/gRPC-based APIs (Maps and Machine Learning APIs). Deep experience in educational efforts of complex internal programming systems, Cloud APIs, Machine Learning, GIS/Geographic information, and the C++ programming language.

Hyrum Wright: Hyrum K. Wright is a Staff Software Engineer at Google, where he has worked since 2012, mainly in the areas of large-scale maintenance of Google's C++ codebase. Hyrum has made more individual edits to Google's codebase than any other engineer in the history of the company.

Camille Fournier: Author, The Manager's Path

...

Foreword

I have always been endlessly fascinated with the details of how Google does things. I have grilled my Googler friends for information about the way things really work inside of the company. How do they manage such a massive, monolithic code repository without falling over? How do tens of thousands of engineers successfully collaborate on thousands of projects? How do they maintain the quality of their systems?

Working with former Googlers has only increased my curiosity. If you’ve ever worked with a former Google engineer (or "Xoogler," as they’re sometimes called), you’ve no doubt heard the phrase "at Google we…" Coming out of Google into other companies seems to be a shocking experience, at least from the engineering side of things. As far as this outsider can tell, the systems and processes for writing code at Google must be among the best in the world, given both the scale of the company and how often people sing their praises.

In Software Engineering at Google, a set of Googlers (and some Xooglers) gives us a lengthy blueprint for many of the practices, tools, and even cultural elements that underlie software engineering at Google. It’s easy to overfocus on the amazing tools that Google has built to support writing code, and this book provides a lot of details about those tools. But it also goes beyond simply describing the tooling to give us the philosophy and processes that the teams at Google follow. These can be adapted to fit a variety of circumstances, whether or not you have the scale and tooling. To my delight, there are several chapters that go deep on various aspects of automated testing, a topic that continues to meet with too much resistance in our industry.

The great thing about tech is that there is never only one way to do something. Instead, there is a series of trade-offs we all must make depending on the circumstances of our team and situation. What can we cheaply take from open source? What can our team build? What makes sense to support for our scale? When I was grilling my Googler friends, I wanted to hear about the world at the extreme end of scale: resource rich, in both talent and money, with high demands on the software being built. This anecdotal information gave me ideas on some options that I might not otherwise have considered.

With this book, we've written down those options for everyone to read. Of course, Google is a unique company, and it would be foolish to assume that the right way to run your software engineering organization is to precisely copy their formula. Applied practically, this book will give you ideas on how things could be done, and a lot of information that you can use to bolster your arguments for adopting best practices like testing, knowledge sharing, and building collaborative teams.

You may never need to build Google yourself, and you may not even want to reach for the same techniques they apply in your organization. But if you aren’t familiar with the practices Google has developed, you’re missing a perspective on software engineering that comes from tens of thousands of engineers working collaboratively on software over the course of more than two decades. That knowledge is far too valuable to ignore.

Camille Fournier

Author, The Manager's Path

CC BY-NC-ND 4.0