Obsessing over personal websites

Shreyas Prakash headshot

Shreyas Prakash

Intended Audience—For those of us who have attempted to make a personal website of their own and have guilt-tripped over making multiple updates every year

I’ve been obsessed with my personal website. It’s not even about the views and impressions which I’m receiving. I have one subscriber on my mailing list from my website, and compared to internet writer standards, I am virtually non existent. 

Yet, I care deeply about this little corner on the internet. It’s a place where I optimise for depth over engagement and audience-building.

It’s my resume, my business card, my store, my directory, as well as my own personal magazine. It’s that one place online that I completely own and control.

As David Perell puts it, it’s one’s own intellectual real estate.

I’m obsessed with it enough to keep revamping my website every year. Just like the corporate re-branding exercises we’re familiar with, I do my own rebranding for my personal website. I reflect on what is NOW my personal brand. I sometimes redo the styling, the fonts and the formatting from scratch and start with a clean slate. I sometimes redo my writing based on my current thinking style and philosophy.

Previously, my favourite font of choice was Karla, then I switched to Poppins, Assistant, Inter, Helvetica Neue and now I’m falling in love with antique serif types (such as the one you see here in this blog)

Every time, I looked back at my previous work as depicted in my website, it felt shitty, and poorly done. But that was the whole point. The new version of yourself would never be satisfied with the previous work you’ve put in. I think @reidhoffman’s “If you’re not embarrassed by the first version of your product, you’ve launched too late” applies well here.

I now had newer updated standards. My personal website updates have mapped my personal evolution over time, as well as my current standards of quality work.

My first website was a Tumblr blog containing a roll of all my photos under one roof. Back then, I identified myself as a photographer, and wanted to showcase this skillset to the world. Slowly, with more and more experiences, the labels which I used to define myself changed. Four years back, I was labeling myself as a ‘UI/UX designer’, and tried to showcase my love of design through my portfolio site on Wix. The objective of this site was to help in job conversions. I wanted recruiters to look at my website and ask for an interview. My way of achieving this was to put mountains and mountains of work online, and in public.

Whenever there was a reference to my previous work, I mapped the portfolio project links to keyboard shortcuts to make it easier to share with the headhunters on chat windows. And whenever I got an opportunity, I shared my screen, and took them through my work reel. I’d obsessively documented my work and my projects. And I was proud of it all.

 A sure shot way to demonstrate my competence and core skills. Share widely, engage with peers. Debate/collaborate with folks who approach me through my website. Leave behind a legacy online.

And I waited for job offers to roll in. And it did!

My current role as a Product Manager at Noora Health was a result of this building-with-my-garage-door-open-stint.

I had my skin-in-the-game as well as my soul-in-the-game.

This year, I wanted to revamp my personal website with a focus on writing. I’ve been lately viewing writing as a form of thinking, and I wanted to condense and crystallize my ideas into one roof. I redesigned my website again with this brief in mind.

Ghost website now pointing to blog.shreyasprakash.com

This was a setup I was satisfied until I realised how all those javascript animations and micro-interactions were killing the load time and performance of the website. It was at this junction that I discovered this site.

I wanted to make my site more ‘simple’. So, I dumped the earlier direction of a ‘13 megabyte parallax-ative home page prepping for some awwward banner on the top corner of my site’. I just used simple HTML5 tags, deleted all the complex JS and checked the performance speed again.

The site was just 8KB, and had a 100% performance rating as per Google PageSpeed Insights

My current website reflects a lot of my ideals here. I dumped my original plan of making it more ‘designerly’, and went for simplicity instead. Simplicity is the ultimate sophistication.

Simple not just on the front-end, but on the back-end too. The front end blog is hosted on Ghost, an open-source platform for publishing blogs. The blog currently points to blog.shreyasprakash.com, and I have wrapped it on my personal domain as an external wrapper. I’ve been an aspiring founder/hacker, and have started to care about why and how my blog/website is setup. Also planning to setup a /now page to talk a bit more about my daily diaries and current updates. It would serve more as a one-to-many social network where I could post more ephemeral updates. 

I’m inspired by Derek Sivers to eventually migrate my email service provider as well as my file storage on a digital ocean droplet. Let’s see how it goes!

Instead of routing my internet friends to an external site, I want them to land on my website first. I’ve started to think long term and have come to a realisation that individuals last longer than companies. With the emergence of ChatGPT and other large language models, even a giant like Google is actively contending with significant competitive pressures. This situation highlights that no company, regardless of its size, is shielded from market challenges and competitors.

I want my website to be a definitive place to get everything I create. I will still continue to put stuff on some other company’s sites (such as Twitter tweets). However, they would be secondary copies and not the primary source.

Eventually, I want this to be my ‘root’. I can fork it wherever I want.

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

Read more

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