Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Ingredient overlap between 26 world cuisines, measured over 1,956 well-known dishes described in 7 languages. Provenance — read this first: the dishes are real, well-known dishes, but their ingredient lists were written by a large language model and verified by a second model pass, not transcribed from cookbooks. This dataset therefore measures how a language model represents 26 cuisines, under a single consistent describer, rather than how people actually cook. A manual audit found ingredient/dish mismatches in about 7% of entries. It should not be cited as an ethnographic record. Four tables: 26 cuisines with dish counts and country centroids; 958 canonical ingredients with names in 7 languages; a bipartite cuisine-to-ingredient graph of 3,164 rows; and all 289 cuisine pairs with overlap share, great-circle centroid distance and a land-border flag. The distance and border columns support the obvious test. Across all pairs, Pearson r between overlap and distance is -0.33, and -0.28 after removing every pair sharing a land border. The 14 pairs that share a land border average 2.01% overlap against 0.63% for the 275 that do not, and the closest quarter of pairs averages 1.26% against 0.39% for the farthest quarter. A handful of pairs resist this, and the strongest link in the corpus is one of them: Ethiopia-Philippines at 8,993 km, ahead of every land-border pair. Mexico-Philippines lands at 13,844 km and UK-US at 6,952 km. This is not an artefact of corpus size — size correlates with overlap at only -0.18, and Vietnam (52 dishes, 0.40% mean overlap) sits at the bottom while Mexico (52 dishes, 0.85%) sits near the top. Version 2.0.0 adds Russian and Ethiopian cuisines (24 to 26) and reflects a duplicate-removal pass on the corpus.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.