Every darn thing is a kekulean loop if you notice it

Shreyas Prakash headshot

Shreyas Prakash

the problem and solution co-creative loop

In my first career arc of being an inexperienced product practitioner, I used to think of the problem and the solution as a traditional waterfall.

You think of the problem, define the constraints, check. Head to explore solutions. Check. Finalise the solution. Check. And then pass it on, and move on to the next problem <> solution. It was supposed to always point right —>

It took me that entire decade and a Masters education in design methodology to help me realise that it seldom works that way, in reality. Problem and solution pairs are having a kekulean dance with each other, eating each others tail, biting and pouncing at each other until they end up with a better problem and solution pair.

There is a co evolution which we miss noticing. In retrospect, it felt fairly obvious and I was scrutinising myself as to why I needed a masters education in design theory for me to realise this trivial aspect of life.

the belief and practise co creative loop

After all, life is nothing but problem solving right? How can I get this all wrong for something so fundamental?!

I also then realised that I make the same mistake in other aspects too. I have been mistaking bidirectional pairs for unidirectional pairs the whole time.

I’ll give another example of such a mistake from my most recent reading of the book review of Tanya Luhrmann’s How God Becomes Real by Michael Nielsen:

Tanya explores the relationship between belief and practise in this book. I used to think that people who are “religious” by spirit, also do practise a lot of rituals because they’re religious. Atleast that was the notion I was used to hearing. However, Tanya explores a different dynamic where she suggests that practise itself by virtue of practise — practise instils belief.

Tanya M. Luhrmann has written a beautiful book exploring this question, “How God Becomes Real: Kindling the Presence of Invisible Others”. The book explores the idea that much of the purpose of religious practice is to help practitioners believe. This inverts conventional wisdom, with Luhrmann taking seriously the possibility that sometimes people aren’t worshipping because they believe, but rather believing because they worship. More generally: Luhrmann makes a compelling case that there is a much more complex relationship between belief and religious practice than you might naively suppose, and she explores some of that relationship.

Personally, I come from the other side of the spectrum where I want to be religious for some reason, and I lack embedding some rituals in my day to day. This thought that religion and practise are a co-evolutionary loop gives me great hope. I’ve envied my mom, and my sister in the way they have cultivated their faith through practise: which involves chanting Hanuman chalisa, Vishnu sahasranaamam, Lalitha sahasranaamam etc and various other mantras in the evenings as a part of their daily/weekly/occasional puja rituals.

Right now, It’s 6:15 PM at dusk, an auspicious time usually meant for evening prayers, and here I am talking about the process of Bhakti (practise of worship), rather than doing the practise itself. Religious belief isn’t something that’s easily attained or endowed with, and it’s hard to tilt towards a religious worshipper from a somewhat-agnostic mode:

Let me review a few of the moves Luhrmann makes in setting up her project. She points out, convincingly, that religious belief usually isn’t something easily attained, despite the fact that many theories of religion “presume that belief is direct and unproblematic – that in most cultures, people simply take spirit and the supernatural to be there. That doesn’t make sense. Gods and spirits cannot be seen. You cannot shake their hands, look them in the eye, or hear their voice when they speak. It seems odd to assume that people just take for granted that they are present.”

I find it weird when I say this, but knowing this theory has actually made me more religious. It has given me more meaning to what’s interpreted as practise.

From the day I read this book review article on the co-evolutionary loop phenomenon exhibited by religion and practise, I am not able to unsee these patterns applied across everywhere. And there are more..

the aging and disease co-creative loop

#todo https://x.com/brian_armstrong/status/2061853377483493421?s=46

I sometimes wonder if it’s a cognitive psychology flaw where we mistake such systemic effects.

if you’re under 50, cellular reprogramming drugs are how you’ll live to 150.

even if we cure every disease on Earth, that still wouldn’t get you there on its own.

the oldest person who ever lived, jeanne calment, made it to 122, and in almost 30 years nobody has come close to beating her.

120 is just the natural human limit.

so while curing diseases can keep you healthy right up to that limit, it can’t actually extend the limit.

but what if you treated aging itself as a disease, and cured that?

that’s exactly what brian armstrong’s company just raised $435M to do.

NewLimit is working on something called cellular reprogramming.

in plain terms, every cell carries a set of instructions that decide how young or old it behaves

NewLimit uses RNA to switch on the combinations that make an old cell start acting young again.

they already have a prototype that does this to human liver cells, healing the liver faster after injury and speeding up recovery from alcohol damage.

the first human trial is set for 2027.

now, to be clear, solving aging is unfathomably hard.

this first liver drug is one cell type in one organ, and reversing aging across an entire body is a much bigger problem than repairing the liver.

but the reason it’s even on the table now is AI.

there are more possible combinations of those cellular instructions than any human could test by hand in a billion years

but machine learning is what lets you search that space and find the few that actually make a cell young again.

that’s the bet NewLimit is built on.

so the liver is the proving ground. once you can safely reset the age of human cells there, 120 stops being a fixed ceiling.

cellular reprogramming is the real path to 150, and if you can keep resetting the clock, there’s no obvious reason it has to stop there…

closing thoughts

It’s all in an ultimate evolutionary loop. And we fail to realise the systemic complexity hidden underneath the everyday narratives.

Most of us are primed to think linearly with “X causes Y” logic, but we have to adopt a systems thinking lens, and I’m trying to train myself here with the notion that everything is a system (X causes Y, which feedback’s into X again..), and it’s not easy..

I will keep hunting for more such co-creative systemic loops. And I hope to find more.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. My agentic engineering workflow (step by step)agentic-coding
  2. Keep hunting for co creative systemic loopsdesign-thinking
  3. Keep hunting for co creative loops
  4. Every darn thing is a kekulean loop if you notice itdesign-thinking
  5. Hammock driven developmentagentic-coding
  6. Peculiar ways number three fits into our funny little brains
  7. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  8. How I write essays in 2026writing
  9. Authority in the guise of evidencecritical-rationalism
  10. Map is not the territoryphilosophy
  11. Self hypnosis as a manifestation ritualmeditation
  12. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  13. How I prepare for tough negotiations nowadaysnegotiation
  14. When should we steelthread somethingproduct-development
  15. How to become a polyglot
  16. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  17. Healthy conflict in teams have a tipping pointteam-building
  18. Deslopify AI writingwriting
  19. How I started building softwares with AI agents being non technicalagentic-coding
  20. Read raw transcriptsknowledge
  21. Legible and illegible tasks in organisationsproduct
  22. L2 Fat marker sketchesdesign
  23. Writing as moats for humanswriting
  24. Beauty of second degree probesdecision-making
  25. Boundary objects as the new prototypesprototyping
  26. One way door decisionsproduct
  27. Finished softwares should existproduct
  28. How I periodically rank my rough draftsobsidian
  29. Flipping questions on its headinterviewing
  30. Vibe writing maximswriting
  31. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  32. How I build greenfield apps with AI-assisted codingai-coding
  33. We have been scammed by the Gaussian distribution clubmathematics
  34. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  35. I was wrong about optimal stoppingmathematics
  36. Thinking like a shipmental-models
  37. Hyperpersonalised N=1 learningeducation
  38. New mediums for humans to complement superintelligenceai-coding
  39. Maxims for AI assisted codingai-coding
  40. Personal Website Starter Kitai-coding
  41. Virtual bookshelvesaesthetics
  42. It's computational everythingtrends
  43. Public gardens, secret routesdigital-garden
  44. Git way of learning to codeai-coding
  45. Kaomoji generatorsoftware
  46. Copy, Paste and Citeai-coding
  47. Style Transfer in AI writingai-coding
  48. Understanding codebases without using codeai-coding
  49. Vibe coding with Cursorai-coding
  50. Virtuoso Guide for Personal Memory Systemsmemory
  51. Writing in Future Pastwriting
  52. Publish Originally, Syndicate Elsewhereblogging
  53. Poetic License of Designdesign
  54. Idea in the shower, testing before breakfastsoftware
  55. Technology and regulation have a dance of ice and firetechnology
  56. How I ship "stuff"software
  57. Writing is thinkingwriting
  58. Song of Shapes, Words and Pathscreativity
  59. How do we absorb ideas better?knowledge
  60. Read writers who operatewriting
  61. Brew your ideas lazilyideas
  62. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  63. Compound Interest of Private Notesknowledge
  64. Conceptual Compression for LLMsai-coding
  65. Meta-analysis for contradictory research findingsdigital-health
  66. Proof of workproduct
  67. Gauging previous work of new joinees to the teamleadership
  68. Task management for product managersproduct
  69. Beauty of Zettelswriting
  70. Stitching React and Rails togetherai-coding
  71. Exploring "smart connections" for note takingknowledge
  72. Deploying Home Cooked Apps with Railssoftware
  73. Repetitive Copypromptingwriting
  74. Questions to ask every decadejournalling
  75. Balancing work, time and focusproductivity
  76. Hyperlinks are like cashew nutswriting
  77. Brand treatments, Design Systems, Vibesdesign
  78. How to spot human writing on the internetwriting
  79. Can a thought be an algorithm?product
  80. Opportunity Harvestingcareers
  81. How does AI affect UI?design
  82. Everything is a prioritisation problemproduct-management
  83. Nowlifestyle
  84. How I do product roastsproduct
  85. The Modern Startup Stacksoftware
  86. In-person vision transmissionproduct
  87. How might we help children invent for social good?social-design
  88. The meeting before the meetingmeetings
  89. Design that's so bad it's actually gooddesign
  90. Lessons learnt interview prepping for product rolesinterviewing
  91. Obsessing over personal websitessoftware
  92. English is the hot new programming languagesoftware
  93. Better way to think about conflictsconflict-management
  94. The role of taste in building productsdesign
  95. Dear enterprises, we're tired of your subscriptionssoftware
  96. Products need not be user centereddesign
  97. World's most ancient public health problemsoftware
  98. Pluginisation of Modern Softwaredesign
  99. Let's make every work 'strategic'consulting
  100. Making Nielsen's heuristics more digestibledesign
  101. Startups are a fertile ground for risk takingentrepreneurship
  102. Insights are not just a salad of factsdesign
  103. Minimum Lovable Productproduct
  104. Methods are lifejackets not straight jacketsmethodology
  105. How to arrive at on-brand colours?design
  106. Minto principle for writing memoswriting
  107. Importance of Whytask-management
  108. Quality Ideas Trump Executionsoftware
  109. How to hire a personal doctormental-models
  110. Why I prefer indie softwareslifestyle
  111. Use code only if no code failscode
  112. Self Marketing
  113. Personal Observation Techniquesdesign
  114. Design is a confusing worddesign
  115. A Primer to Service Design Blueprintsdesign
  116. Rapid Journey Prototypingdesign
  117. Visualise detailed file structures on CLIcli
  118. Do's and Don'ts of User Researchdesign
  119. Design Manifestodesign
  120. Complex project management for productproducts
  121. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  122. Pedagogy of the Uncharted — What for, and Where to?education
  123. Future of Ageing with Mehdi Yacoubiinterviewing
  124. Future of Tacit knowledge with Celeste Volpiinterviewing
  125. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  126. Future of Equity with Ludovick Petersinterviewing
  127. Future of work with Laetitia Vitaudinterviewing
  128. Future of Mental Health with Kavya Raointerviewing
  129. Future of unschooling with Che Vanniinterviewing
  130. How might we prevent acquired infections in hospitals?digital-health
  131. The why to endure any howentrepreneurship
  132. Design education amidst social tribulationsdesign
  133. How might we assist deafblind runners to navigate?social-design