20 years working on the same software product

Original Article ↗ Hacker News Discussion ↗

IP, Power Asymmetry, and Legal Threats

  • The Sony TV-show mockup episode sparked discussion about how large media companies freely appropriate small developers’ work yet aggressively enforce their own IP.
  • Commenters note that even sending a serious legal letter is expensive; much of the weight comes from a lawyer’s credentials (e.g., “JD” after the name) rather than the letter’s content.
  • Several argue this asymmetry is systemic: copyright law and litigation capacity function as weapons favoring rich entities over individuals.

Algorithms and Problem Complexity

  • Readers ask whether the product still uses a genetic algorithm and if a globally optimal solver (MIP/IP) would be better.
  • The author confirms GA is still used, optimized for thousands of seats and real-world constraints (proximity, couples, alternating genders).
  • Others point out that most combinatorial optimization approaches risk local optima and that seating is often overconstrained anyway.

Business Model, Scale, and “Lifestyle Business”

  • Many are inspired by a long-lived, niche, non-VC product that reliably supports a family.
  • The licensing model: perpetual license per major version with discounted paid upgrades is widely praised as user-friendly and more trustworthy than pure subscriptions.
  • On scale: ~$300k ARR is seen as realistically reachable solo; $1M ARR is “hard but possible” in exceptional niches; $10M ARR as a solo founder is viewed as effectively unattainable.
  • Some dislike the term “lifestyle business,” others find it useful to distinguish profit-driven, owner-controlled companies from growth-at-all-costs startups.

Desktop Software, Electron, and UI Toolkits

  • Strong nostalgia for native desktop apps that work offline and don’t bundle entire browsers.
  • Sharp criticism of Electron as wasteful and symptomatic of “skill issues,” countered by arguments that cross-platform web tech is rational given SDK complexity, distribution friction, and hiring realities.
  • Several note that modern native UI APIs (Windows/Linux especially) are painful for animations, drag-and-drop, and styling, which nudges teams toward web stacks.
  • Frameworks like Qt and newer toolkits (e.g., Slint, SwiftUI) are cited as attempts to bridge this gap, but feature-complete, powerful desktop UI frameworks are seen as rare.

Trust, Longevity, and Single‑Founder Risk

  • Commenters contrast a 20-year, one-person product with frequently short-lived VC-funded services that vanish after acqui-hires or pivots.
  • Skeptics emphasize mortality and “key person” risk; defenders note that stable desktop software continues to run even if the business ends, whereas SaaS dies as soon as the server or billing stops.
  • Business-continuity planning and potential later sale of the business are suggested as mitigations.

Marketing, Piracy, and Practicalities

  • Some wonder why the product doesn’t appear higher in search results and suggest modest ad spend; the author explains long experience with PPC, noting that rising bid prices have eroded ROI.
  • A leaked license key incident leads to a tangent on piracy: small changes to make piracy harder can still significantly affect sales, even for solo developers.

Niches, Underserved Markets, and Career Aspirations

  • Multiple commenters say this is their “dream career”: a small, focused product that deeply serves a niche without chasing unicorn-scale outcomes.
  • It’s noted that many such micro-ISVs stay solo intentionally (to avoid people-management and tech churn) and thus rarely hire.
  • There’s discussion that many developer demographics (e.g., “young men”) build for markets they understand, leaving other demographics—like older or less tech-savvy users—under-served and potentially rich in opportunities.