Public gardens, secret routes

Shreyas Prakash headshot

Shreyas Prakash

When you land on a site, you are treated with various hyperlinks. Based on the UX choices you make, you might end up preferring one over the other. You might get the job done, and head back to your earlier Chrome tab. Nothing out of the ordinary. It’s an internet search as usual.

But what about those pages which have no visible links on the site you just searched. It’s hidden in plain sight, but still useful in certain contexts.

To give a direct example, I was having this huge creative tension on what I should keep on my personal website — should I be selling something? Pitching an idea? Or shrink myself into an entity valuable for corporates offering my skills? 

In Rob Hendle’s essay titled ‘I’m a Poem not a software’, he encounters a similar tension on the aspects of one’s personality that ought to be represented — as a personal site can be anything the person wants to be.

A personal website sits on the blurry line between a corporate entity and a skate park. Because a personal website has everything in its future; career connections and maybe weirdo web friends out there, potential ad money to be squeezed out of it or analytics to be siphoned. These constraints and incentives push our websites to be reserved or fabulous and there’s really no right answer here since a personal website can be anything we want it to be.

And in this blurry line between a corporate entity and a skate park, I decided that my site should be a more dignified version of a skate park where ideas could sprawl and run astray. But I still had a tight knot in my stomach to resolve this conflict — a way in which I could access some professional stuff such as cv, portfolio etc through hidden routes. 

In the context of websites, a ‘route’ refers to a specific URL path that corresponds to a page or resource on the site. It is part of the website’s structure, allowing users to navigate to different sections. So for instance, if you see the ‘now’ link on a site and click on that, you are taken to the site.com/now page. /now is a route of this page.

A hidden route refers to the ones that exist but are not displayed. Hidden routes are often used for purposes like private access, testing, or administrative functions and are not linked or visible in the site’s navigation. The easiest way to find these out is to check the website’s sitemap: Look for a sitemap.xml file, often found in the footer or robots.txt file, which lists all pages on the site. Another way is to examine the source code: right-click on the page and select “View Page Source” to look for hidden links in the HTML.

 A hidden route is public, but not public enough as it’s not visible.    Perfect use case for all the professional resources I want to make semi-public such as the routes— /cv, /portfolio, /work etc

In some sense, I’m intrigued by the concept of a public garden with secret routes. And these secret routes provide me with this malleability to communicate our personal/professional versions to the right audience through the means of a site.

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

2026

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?