Finished softwares should exist
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.
Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech
Read more
- Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
- How I started building softwares with AI agents being non technicalagentic-engineering
- Legible and illegible tasks in organisationsproduct
- L2 Fat marker sketchesdesign
- Writing as moats for humanswriting
- Beauty of second degree probesdecision-making
- Read raw transcriptsknowledge
- Boundary objects as the new prototypesprototyping
- One way door decisionsproduct
- Finished softwares should existproduct
- Essay Quality Rankerobsidian
- Export LLM conversations as snippetsbrowser-extension
- Flipping questions on its headinterviewing
- Vibe writing maximswriting
- How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
- How I build greenfield apps with AI-assisted codingai-coding
- We have been scammed by the Gaussian distribution clubmathematics
- Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
- I was wrong about optimal stoppingmathematics
- Thinking like a ship
- Hyperpersonalised N=1 learningeducation
- New mediums for humans to complement superintelligenceai-coding
- Maxims for AI assisted codingai-coding
- Personal Website Starter Kitai-coding
- Virtual bookshelvesaesthetics
- It's computational and AI everythingai-coding
- Public gardens, secret routesdigital-garden
- Git way of learning to codeai-coding
- Kaomoji generatorsoftware
- Copy, Paste and Citecuriosities
- Style Transfer in AI writingai-coding
- Understanding codebases without using codeai-coding
- Vibe coding with Cursorai-coding
- Virtuoso Guide for Personal Memory Systemsmemory
- Writing in Future Pastwriting
- Publish Originally, Syndicate Elsewhereblogging
- Poetic License of Designdesign
- Idea in the shower, testing before breakfastsoftware
- Technology and regulation have a dance of ice and firetechnology
- How I ship "stuff"software
- Weekly TODO List on CLIcli
- Writing is thinkingwriting
- Song of Shapes, Words and Pathscreativity
- How do we absorb ideas better?knowledge
- Read writers who operatewriting
- Brew your ideas lazilyideas
- Vibescreativity
- Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
- Compound Interest of Private Notesknowledge
- Conceptual Compression for LLMsai-coding
- Meta-analysis for contradictory research findingsdigital-health
- Beauty of Zettelswriting
- Proof of workproduct
- Gauging previous work of new joinees to the teamleadership
- Task management for product managersproduct
- Stitching React and Rails togetherai-coding
- Exploring "smart connections" for note takingknowledge
- Deploying Home Cooked Apps with Railssoftware
- Self Marketing
- Repetitive Copypromptingwriting
- Questions to ask every decadejournalling
- Balancing work, time and focusproductivity
- Hyperlinks are like cashew nutswriting
- Brand treatments, Design Systems, Vibesdesign
- How to spot human writing on the internet?writing
- Can a thought be an algorithm?product
- Opportunity Harvestingcareers
- How does AI affect UI?design
- Everything is a prioritisation problemproduct-management
- Nowlifestyle
- How I do product roastsproduct
- The Modern Startup Stacksoftware
- In-person vision transmissionproduct
- How might we help children invent for social good?social-design
- The meeting before the meetingmeetings
- Design that's so bad it's actually gooddesign
- Breaking the fourth wall of an interviewinterviewing
- Obsessing over personal websitessoftware
- Convert v0.dev React to Rails ViewComponentsrails
- English is the hot new programming languagesoftware
- Better way to think about conflictsconflict-management
- The role of taste in building productsdesign
- World's most ancient public health problemsoftware
- Dear enterprises, we're tired of your subscriptionssoftware
- Products need not be user centereddesign
- Pluginisation of Modern Softwaredesign
- Let's make every work 'strategic'consulting
- Making Nielsen's heuristics more digestibledesign
- Startups are a fertile ground for risk takingentrepreneurship
- Insights are not just a salad of factsdesign
- Minimum Lovable Productproduct
- Methods are lifejackets not straight jacketsmethodology
- How to arrive at on-brand colours?design
- Minto principle for writing memoswriting
- Importance of Whytask-management
- Quality Ideas Trump Executionsoftware
- How to hire a personal doctor
- Why I prefer indie softwareslifestyle
- Use code only if no code failscode
- Personal Observation Techniquesdesign
- Design is a confusing worddesign
- A Primer to Service Design Blueprintsdesign
- Rapid Journey Prototypingdesign
- Directory Structure Visualizercli
- AI git commitscli
- Do's and Don'ts of User Researchdesign
- Design Manifestodesign
- Complex project management for productproducts
- How might we enable patients and caregivers to overcome preventable health conditions?digital-health
- Pedagogy of the Uncharted — What for, and Where to?education
- Future of Ageing with Mehdi Yacoubiinterviewing
- Future of Equity with Ludovick Petersinterviewing
- Future of Mental Health with Kavya Raointerviewing
- Future of Tacit knowledge with Celeste Volpiinterviewing
- Future of Rural Innovation with Thabiso Blak Mashabainterviewing
- Future of unschooling with Che Vanniinterviewing
- Future of work with Laetitia Vitaudinterviewing
- How might we prevent acquired infections in hospitals?digital-health
- The soul searching yearsentrepreneurship
- Design education amidst social tribulationsdesign
- How might we assist deafblind runners to navigate?social-design