The whole world is just the snake eating its own tail

02 Jul 2026

Shreyas Prakash headshot

Shreyas Prakash

When we see two events, A and B, our natural tendency is to place a succinct left-to-right arrow —>, in between two events A and B. It hardly crossed my mind sometimes that A and B could be feedback loops. A could effect B, and B could effect A, and the effect of B effecting A, could effect the effect of A effecting B…. . Why complicate things isn’t it? We will just leave it as it is, after all simplicity is the ultimate sophistication..

Okay, enough of abstractions, let’s talk specifics:

  • I see a thing called a “problem”, and another thing called a “solution”, and I imagine the problem leading to the solution, or so the thinking goes.

  • I see a person being “religious”, and a set of rituals called “practice”, and I imagine the belief came first and the practice merely expressed it.

  • I see “aging” and “disease”, and I imagine aging as the background condition, while diseases are the foreground enemies we are meant to defeat.

As you could notice from the above examples, I kept mistaking the loop, for a A —> B type line.

Most of what we see around the world don’t work in a capital “L” linear way. by the end of this essay, I hope I’ve driven the point around self reinforcing feedback loops strong enough..

And even August Kekule, the German chemist famous for the discovery of the Benzene ring, had made the same mistake (but he did learn from his mistake, and was able to unearth the chemical structure of Benzene). He thought the benzene was a linear chain of carbon atoms, but the mathematics of the chemistry didn’t just add up if it were to be a linear chain.

To him, this was an unsolved enigma, a ghost in the molecular machine. So he was taking a sweet nap on a rocking chair in front of the Victorian fireplace, when inspiration struck him:

And in that sudden hallucinogenic drift, he noticed the benzene atoms dancing, whirling like a molecular conga line, before cooling into a ring and biting its own tail. The mythical ouroboros appeared.

How many of us are making a similar such mistake? Are we all mistaking the loop for a line? Could this visual of a snake eating its own tail, serve as metaphysical guide for us to think through reality and how everything is connected? Let’s look at these patterns in more detail:

problem  solution

In my first career arc of being an “fresher”, an inexperienced product newbie, 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 —>, from the problem and into the solution..

Jumping into “solutions” prematurely, before understanding the problem was also considered to be offensive in some circles.. as we have not thought through the problem completely, and that we’re not qualified to take such a serious move so early. This was the designerly equivalent of the cardinal sin.

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 be educated enough to know this..

Timing through solutions can help us think through the problems which can also help us think through better solutions.. while working on a recent creative experiment, I spent much more time cooking up multiple variations of the concepts through prototypes. I could have also gone the problem definition route first, doing informational interviews first, and assess which pain points are more important, and after all that, I could have then considered possible solutions. But the reality was quite zigzaggy. Those prototypes then served as better tools for enquiry helping me reach traction and momentum through them, the image of the double-diamond which is flashed left, right, and centre as a part of the designers indoctrination program across various universities seldom withstands contact with reality, this theory wrinkles and perishes with usage, as like other processes, this is also not a linear conveyor belt style causality..

belief  practise

I also then realised that I make the same mistake in other aspects too — bidirectional pairs, unidirectional pairs. This topic keeps coming up again and again..

Let’s talk about belief and practise. Tanya Luhmann, the American professor explores the relationship between belief and practise in her book—How God becomes real. She describes herself as “anthropologist of mind”. In her quest to understand the way people represent thought itself, and the way those culturally varied representations shape the most intimate experience of life itself.

This is Nielsen describing his own experience reading this book:

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.

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.

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 Hindu japa 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. How ironic, but I will get there.

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, unless cultivated with practise:

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 makes 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..

aging  disease

Now, the thinking here is Ageing → Disease, that as we age:

  • DNA damage accumulates.

  • Cells become senescent (they stop dividing but release inflammatory molecules).

  • Mitochondria become less efficient.

  • Stem cells lose their ability to repair tissues.

  • Chronic low-grade inflammation (“inflammaging”) increases, leading to more diseases, and ultimately death.

But now, increasingly, scientists are thinking that it is rather: Ageing ↔ Disease, instead of merely, Disease → Ageing.

With this U-turn in the direction of arrows, we have this bet that ‘aging itself is a disease’ which can be treated. And that part just blew my mind. We now have scientists trying to reverse the age of human cells, and we now have clinical trials trying to prove this in full swing. Newlimit is one such company, working in this bleeding edge of longevity with this same thesis.

“And by combating ageing itself as a disease, they want to combat all diseases.”

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. Brian Armstrong’s company just raised $435M to do this.

What excites me from all this latest development in tech is not the fact that the age 120 stops being a fixed ceiling, or the fact that cellular reprogramming gives potential pathways to 150 years on average, but the fact that this all started with a smart framing of a statement that got flipped on its own head: “that ageing is a disease”.. who would have thought?

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..

To me, most of the smartest ideas out there starts with a unique counter-positioned framing, a view that shakes the world view, this creates a literal tear in the space-time continuum and leads to innovation, as a side effect..

I will keep hunting for more such co-creative systemic loops. And I hope to find more. After all, the whole world is just the snake eating its own tail…

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

Read more

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