Public gardens, secret routes
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
2025
- Legible and illegible tasks in organisations
- L2 Fat marker sketches
- Writing as moats for humans
- Beauty of second degree probes
- Read raw transcripts
- Boundary objects as the new prototypes
- One way door decisions
- Finished softwares should exist
- Essay Quality Ranker
- Export LLM conversations as snippets
- Flipping questions on its head
- Vibe writing maxims
- How I blog with Obsidian, Cloudflare, AstroJS, Github
- How I build greenfield apps with AI-assisted coding
- We have been scammed by the Gaussian distribution club
- Classify incentive problems into stag hunts, and prisoners dilemmas
- I was wrong about optimal stopping
- Thinking like a ship
- Hyperpersonalised N=1 learning
- New mediums for humans to complement superintelligence
- Maxims for AI assisted coding
- Personal Website Starter Kit
- Virtual bookshelves
- It's computational everything
- Public gardens, secret routes
- Git way of learning to code
- Kaomoji generator
- Style Transfer in AI writing
- Copy, Paste and Cite
- Understanding codebases without using code
- Vibe coding with Cursor
- Virtuoso Guide for Personal Memory Systems
- Writing in Future Past
- Publish Originally, Syndicate Elsewhere
- Poetic License of Design
- Idea in the shower, testing before breakfast
- Technology and regulation have a dance of ice and fire
- How I ship "stuff"
- Weekly TODO List on CLI
- Writing is thinking
- Song of Shapes, Words and Paths
- How do we absorb ideas better?
2024
- Read writers who operate
- Brew your ideas lazily
- Vibes
- Trees, Branches, Twigs and Leaves — Mental Models for Writing
- Compound Interest of Private Notes
- Conceptual Compression for LLMs
- Meta-analysis for contradictory research findings
- Beauty of Zettels
- Proof of work
- Gauging previous work of new joinees to the team
- Task management for product managers
- Stitching React and Rails together
- Exploring "smart connections" for note taking
- Deploying Home Cooked Apps with Rails
- Self Marketing
- Repetitive Copyprompting
- Questions to ask every decade
- Balancing work, time and focus
- Hyperlinks are like cashew nuts
- Brand treatments, Design Systems, Vibes
- How to spot human writing on the internet?
- Can a thought be an algorithm?
- Opportunity Harvesting
- How does AI affect UI?
- Everything is a prioritisation problem
- Now
- How I do product roasts
- The Modern Startup Stack
- In-person vision transmission
- How might we help children invent for social good?
- The meeting before the meeting
- Design that's so bad it's actually good
- Breaking the fourth wall of an interview
- Obsessing over personal websites
- Convert v0.dev React to Rails ViewComponents
- English is the hot new programming language
- Better way to think about conflicts
- The role of taste in building products
- World's most ancient public health problem
- Dear enterprises, we're tired of your subscriptions
- Products need not be user centered
- Pluginisation of Modern Software
- Let's make every work 'strategic'
- Making Nielsen's heuristics more digestible
- Startups are a fertile ground for risk taking
- Insights are not just a salad of facts
- Minimum Lovable Product
2023
- Methods are lifejackets not straight jackets
- How to arrive at on-brand colours?
- Minto principle for writing memos
- Importance of Why
- Quality Ideas Trump Execution
- How to hire a personal doctor
- Why I prefer indie softwares
- Use code only if no code fails
- Personal Observation Techniques
- Design is a confusing word
- A Primer to Service Design Blueprints
- Rapid Journey Prototyping
- Directory Structure Visualizer
- AI git commits
- Do's and Don'ts of User Research
- Design Manifesto
- Complex project management for product
2022
2020
- Future of Ageing with Mehdi Yacoubi
- Future of Equity with Ludovick Peters
- Future of Tacit knowledge with Celeste Volpi
- Future of Mental Health with Kavya Rao
- Future of Rural Innovation with Thabiso Blak Mashaba
- Future of unschooling with Che Vanni
- Future of work with Laetitia Vitaud
- How might we prevent acquired infections in hospitals?