Home

Finished softwares should exist

Shreyas Prakash headshot

Shreyas Prakash

24 May 2025

Some blockbuster software products should just end the cycle of endless iteration.

The conversation around product development needs to take seriously the idea of “finished” software, alongside the more common belief that “software is never perfect and always needs improvement.”

These are two different schools of thought and have a lot of friction to coexist with each other. I lean toward the second, but I still wish more people explored the first.

I see three variations of the “finished software” idea:

  • Freeze model: a clean, final version is frozen and maintained by the community.

  • Modular architecture: a stable core with optional plugins, like Obsidian or Figma, allows for open-ended customization without bloating the base.

  • Dynamic software: the standard model, where new features are added continuously under the banner of ongoing development.

My guess is that it evolved through sales-driven development: Every time a potential enterprise client would have asked the JIRA team for one more additional feature, the team would have been a “yes man”, to close the deal. Over time, everything would have added up to become what it’s today. Personally, using JIRA feels like there are 10 different traffic lights across 10 different roads with cars honking at each other, and you’re exactly at the inter-intersection.

It’s a get death by a thousand cuts. My sincere hope in writing this, was a public plea that no software should end up like JIRA. It’s a version of Ashby’s Law: increased complexity demands more control, and eventually the system collapses under its own weight.

One product can’t serve all use cases forever. When you try to make the same software work for startups and Fortune 500s, you end up bloating it for one group and alienating the other.

To keep software “finished,” you need a philosophy of refusal. You need to say no — even when it costs you. There is an optimal stopping point.

But saying no is hard. Additions look like growth. Subtraction doesn’t. And almost no one wants to stop, because the economics of growth, customer segmentation, and sales strategies reward motion, not stasis.

I wish Slack, Gmail and Google had just frozen. Instead, it kept going, adding agents and LLMs into every nook and corner of the app it could find. I doubt that will stop.

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