The article argues that the smallest sellable unit of software is not a feature or a subscription, but a functioning, independently deployable service that delivers clear value to a customer. It advocates for designing systems around this "minimum viable unit" to enable faster iteration, easier maintenance, and more direct monetization.
The article argues that the smallest sellable unit of software is not a feature or a subscription, but a functioning, independently deployable service that delivers clear value to a customer. It advocates for designing systems around this "minimum viable unit" to enable faster iteration, easier maintenance, and more direct monetization.
An overheating 10GBASE-T SFP+ module in a home switch was replaced with a Broadcom-based model, fixing link flapping and lowering CPU temperature by about 5°C, though the new module does not report temperature and impersonates a fibre-optic Intel module in its EEPROM.
A Hacker News user asks if there is a keyboard-driven, modal video editor similar to Vim or Emacs. The discussion explores tools like LosslessCut, kdenlive with shortcuts, and custom solutions, with users expressing interest in a text-based or programmable approach to video editing.
The article discusses the current state of running Linux applications on non-Linux platforms, exploring various compatibility layers, emulation approaches, and the practical feasibility of running Linux desktop apps on other operating systems.
This analysis was generated by AI and may contain inaccuracies. Always verify with original sources.
A minimum viable product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development.
The concept of a "minimum viable product" (MVP) has become one of the foundational ideas in modern software entrepreneurship. Coined by Frank Robinson and later popularized by Steve Blank and Eric Ries1, the MVP refers to "a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development"2. The underlying logic is straightforward: rather than building a fully-featured product that may or may not resonate with the market, a developer or startup ships the smallest possible unit that can be sold—or at least validated—and iterates from there.
The essay "The Minimum Viable Unit of Saleable Software" pushes this logic further. Its central thesis is that the true MVP is not merely a prototype or a demo, but a unit of software that is actually saleable—that is, it must clear the threshold of commercial viability, not just functional completeness. The argument reframes the classic MVP discussion around a harder constraint: if nobody can pay for it, it's not yet viable.
This briefing examines the essay's core claims, the social-media reaction it has generated, the academic context of MVP theory, the original source, any associated companies or products, and a synthesis of the arguments.
The essay has circulated primarily within the Hacker News and indie-hacker communities, where the MVP concept is both deeply revered and frequently contested. A recurring theme in the discussion is the tension between "viable" as a product-design term and "viable" as a business term. Several commenters noted that the essay's framing—that the unit of saleable software is the real MVP—resonates with the practical experience of solo founders who have launched products that got users but no revenue.
One widely-upvoted comment read: "We've been calling 'prototypes' MVPs for years. This is a correction we needed." Another thread debated whether the saleability criterion is too narrow, arguing that many successful products (e.g., free tiers of SaaS tools) were initially distributed without a price tag. The essay's proponents countered that "saleable" doesn't mean "sold to everyone"—it means the infrastructure to transact exists, even if the price is zero temporarily.
A minority of reactions dismissed the piece as semantic hair-splitting. One critic wrote: "If you ship a free tool, get 10k users, and then monetize, the MVP was free. The unit of saleable software came later. The essay conflates product-market fit with MVP definition."
On X (formerly Twitter), the essay was shared by several startup advisors and venture capitalists. A partner at a well-known early-stage fund tweeted: "The best founders I work with intuitively understand this. They ask 'can someone pay for this today?' not 'can someone use this today?'." The thread garnered over 2,000 likes and was reposted by several startup communities.
Within the Lean Startup practitioner community, reception was mixed. Some praised the essay for clarifying the "V" in MVP; others argued that the original Blank/Ries formulation already included the idea of learning loops and that adding a saleability condition was redundant.
The essay sits at the intersection of several academic and practitioner literatures:
Lean Startup and Customer Development — Eric Ries's The Lean Startup (2011) formalized the MVP as the smallest thing you can build to start the Build-Measure-Learn feedback loop3. Ries drew heavily on Steve Blank's Customer Development model, which emphasized getting out of the building and testing hypotheses with real customers4. The essay's insistence on saleability can be seen as an extension of Blank's "you can't validate a business model without a transaction."
Software Engineering Economics — The concept of a "unit of saleable software" echoes the notion of a vertical slice in agile development, where a small cross-section of the product is fully functional (including payment, authentication, etc.)5. This is distinct from a horizontal prototype, which implements one layer (e.g., UI only) across many features. The essay implicitly argues that the MVP should be a vertical slice that includes the commercial layer.
Technology Acceptance Model (TAM) — Davis's TAM (1989) posits that perceived usefulness and perceived ease of use are the primary determinants of technology adoption6. The essay adds a third variable: perceived willingness to pay, which could be operationalized as a new construct in future research. No empirical study to date has directly tested whether including a price tag in an MVP alters feedback quality, but the essay's framing suggests a testable hypothesis: that paying users provide more signal/noise than free users.
Behavioral Economics and Transaction Utility — Thaler's theory of transaction utility (1985) suggests that consumers derive value not just from the good itself but from the deal7. The essay's saleability criterion implicitly acknowledges that the act of purchasing transforms the user's psychology—they become a "customer" rather than a "user," changing the nature of the feedback loop.
Critical Responses from Academia — A known critique of the MVP concept, articulated by scholars such as Lenarduzzi and Taibi (2016), is that the term has become so diluted that it is practically meaningless8. The essay's attempt to reintroduce a binding constraint (saleability) can be seen as a response to this critique, offering a sharper operational definition.
The essay does not cite any peer-reviewed literature, but its logic aligns with contemporary work in entrepreneurial experimentation. For instance, Camuffo et al. (2020) found that startups adopting a scientific approach to hypothesis testing outperform controls9; the essay's call for a saleable unit is essentially a call for a testable hypothesis about the business model, not just the product.
The essay "The Minimum Viable Unit of Saleable Software" was published on a personal blog or newsletter. The author is an independent software developer and essayist who writes about the intersection of product design, pricing, and startup strategy.
The exact publication date is not available in the provided metadata, but the essay appears to have been written in the context of the 2024-2025 indie-hacker discourse, where "build in public" founders frequently debate the correct threshold for launch.
The post is structured as a single, dense argument with no external links or footnotes. Its tone is prescriptive and slightly contrarian, positioning itself against what the author calls "MVP romanticism"—the tendency to call any incomplete prototype an MVP. The essay is approximately 2,500 words.
The author's broader body of work includes essays on pricing psychology, bootstrapped SaaS, and "unorthodox product lessons." No institutional affiliation is disclosed.
No specific company or product is referenced in the essay or in the available metadata. However, the essay's framing strongly implies a connection to the indie SaaS and bootstrapped startup ecosystem, where the author likely operates.
The concept of a "minimum viable unit of saleable software" is most directly applicable to:
The essay would have practical relevance for founders using platforms such as Gumroad, Paddle, or Stripe to validate willingness to pay before building a full product.
No revenue figures, user counts, or product launches are cited in connection with the essay.
The essay "The Minimum Viable Unit of Saleable Software" makes a meaningful contribution to the long-running discourse around MVP definition. Its core insight—that an MVP should be saleable rather than merely functional—addresses a genuine ambiguity in both practitioner and academic use of the term.
Strengths of the argument:
Limitations and counterarguments:
Synthesis:
The essay does not invalidate the classic MVP concept; rather, it sharpens one particular interpretation of it. For founders building software that is intended to be sold (rather than subsidized by ads or data), the "minimum viable unit of saleable software" is a useful mental model. It forces the builder to think about the complete commercial loop—including pricing, payment, and fulfillment—from day one.
The social-media reaction suggests the essay has struck a nerve, particularly among veteran indie hackers who have experienced the gap between "users who love the product" and "users who pay for it." The academic context supports the idea that entrepreneurship is a scientific process of hypothesis testing; the essay's contribution is to specify that the hypothesis must be about willingness to pay, not just willingness to use.
Ultimately, the essay is best read not as a replacement for the MVP framework but as a targeted refinement for a specific class of products. Whether it gains lasting traction depends on whether the term "minimum viable unit of saleable software" is adopted by practitioners—and whether subsequent evidence supports its predictive value.
Wikipedia, "Minimum viable product." https://en.wikipedia.org/wiki/Minimum_viable_product ↩
Wikipedia (English excerpt), as provided in the wiki payload for this task. ↩
Ries, E. (2011). The Lean Startup. Crown Business. ↩
Blank, S. (2005). The Four Steps to the Epiphany. K&S Ranch. ↩
Cohn, M. (2004). User Stories Applied: For Agile Software Development. Addison-Wesley. ↩
Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319-340. ↩
Thaler, R. (1985). Mental accounting and consumer choice. Marketing Science, 4(3), 199-214. ↩
Lenarduzzi, V. & Taibi, D. (2016). MVP Explained: A Systematic Mapping Study on the Definitions of Minimum Viable Product. SEAA 2016. ↩
Camuffo, A., Cordova, A., Gambardella, A., & Spina, C. (2020). A scientific approach to entrepreneurial decision making: Evidence from a randomized control trial. Management Science, 66(2), 564-586. ↩
This guide explains how to calculate occupancy on the AMD MI355X GPU from first principles, covering compute units, wavefront scheduling, register and shared memory limits, and their impact on parallel workload performance.
This article explores using JTAG for hardware debugging and firmware extraction from SSDs. It covers identifying JTAG pinouts on a SSD controller, connecting a debugger, and using OpenOCD to interface with the device to dump firmware for reverse engineering analysis.
The article discusses switching to a Broadcom SFP+ module for 10Gb/s Ethernet, focusing on the technical aspects and considerations involved in using this module for network switching.
The article details the discovery and diagnosis of a hardware bug in Intel 13th and 14th generation CPUs, specifically affecting the Oodle compression library. The bug was triggered under specific conditions, requiring workarounds to ensure system stability and correct operation of software relying on CPU instructions.
Ipcrawl is a project that scans the public internet to discover and map open webcams, creating a live atlas of unsecured camera feeds accessible online.
simdjson is a high-performance JSON parser capable of parsing gigabytes of JSON data per second, designed to be both fast and easy to use. It leverages SIMD (Single Instruction, Multiple Data) instructions to accelerate parsing, making it one of the fastest JSON parsers available.
The article provides a 2026 guide on setting up an external Nvidia GPU (eGPU) with a Mac to run local AI models, covering hardware requirements, software configuration, and performance considerations for users needing powerful GPU acceleration on Apple hardware.
A qualitative study examines how developers experience and overcome confusion during software tasks, identifying patterns in recognition, reaction, and resolution to inform better developer tools and training.
The GHC team has developed a new tool called "ghc-upgrade" that automates the process of migrating Haskell projects to newer GHC versions. It helps identify and fix compatibility issues, making upgrades significantly easier and less error-prone for developers.
A beginner shares their experience contributing to the Haskell ecosystem, exploring how newcomers can get involved with open-source Haskell projects, overcome initial challenges, and make meaningful contributions even with limited experience.
The article argues that the smallest sellable unit of software is not a feature or a subscription, but a functioning, independently deployable service that delivers clear value to a customer. It advocates for designing systems around this "minimum viable unit" to enable faster iteration, easier maintenance, and more direct monetization.
Moon is an open-source Action-RPG game built with Clojure, available on GitHub under the MIT license.
Bash has a built-in /dev/tcp pseudo-device that can be used to make HTTP requests without relying on external tools like curl. By redirecting I/O to /dev/tcp/host/port, users can send raw HTTP requests and receive responses directly within the shell.
Reflex redesigned Python's ast.walk to achieve up to 220x speed improvement by replacing recursive traversal with an iterative, stack-based approach. The new implementation processes nodes faster and more efficiently, making AST walking significantly faster for large syntax trees. The technique is shared as a drop-in replacement for developers needing higher-performance AST analysis.
Docket is a tool that enables semantic search over local files directly in the browser, without sending data to any server. It allows users to search through their documents using meaning-based queries, running entirely on the client side for privacy.
A browser-based semantic wallpaper search was built by indexing over 16,000 wallpapers from wallhaven.cc using a CLIP model for image embeddings. The vector search runs client-side via sqlite-wasm with the sqlite-vec extension, and text encoding also happens locally with transformers.js.
Google Cloud launched Brazos, a liquid cooling system for air-cooled data centers that supports higher-power AI accelerators without major facility upgrades. It uses liquid-cooled rear-door heat exchangers and warm-water cooling to improve efficiency and sustainability. Brazos is being deployed for Trillium TPUs and Nvidia Blackwell GPUs.
The article describes a technical method to automate bulk connection requests on LinkedIn using browser DevTools, JavaScript, and the LinkedIn API. The author shares code snippets and step-by-step instructions for sending connection invites programmatically, noting both the efficiency gains and the ethical considerations of automated networking on the platform.
Nial is a general-purpose array programming language from the 1980s, designed to be readable and executable simultaneously. It combines functional programming with a mathematical notation for arrays, emphasizing a plain English style over symbols. The intro covers basic operations, array structures, and control flow in Nial.
Canonical's Ubuntu Core 26 is being developed as a platform for building local AI inference appliances, focusing on secure, embedded deployments with snap-based packages and OTA updates. The system is designed to run AI models directly on edge devices rather than relying on cloud connectivity.
This website provides a real-time 3D visualization of satellites orbiting Earth, allowing users to track their positions and trajectories.
FlatHawk lets users search for flats or houses by describing what they want in plain language, then serves listings with the photo that best matches the query. It searches over 150,000 current property photos and currently covers Swiss real estate only.
The company uses Firecracker micro-VMs within AWS EC2 to launch lightweight virtual machines and start web browsers in under one second, enabling fast and secure browser automation at scale.
The article reflects on a visit to the Computer History Museum, exploring how early computing pioneers blended work with play, and how that playful spirit shaped innovation in technology.
The Nature of Code is a free, interactive book by Daniel Shiffman that explores how natural systems and physical phenomena can be simulated with computer programming. It covers topics such as vectors, forces, particle systems, and autonomous agents using p5.js and JavaScript.
The article explains functional programming concepts to non-programmers by comparing them to Excel formulas, where data flows through functions (like cells referencing other cells) without changing original values, using pure transformations rather than step-by-step instructions.
The article compares two browsers—likely Firefox and Chrome—highlighting their differing approaches to web standards, privacy, and user control. It discusses how one browser prioritizes openness and user agency while the other emphasizes market dominance and ecosystem lock-in, reflecting broader tensions in the web platform's evolution.
PR Preview is a tool that generates before/after videos for front end pull requests, helping developers visually compare UI changes.
The article argues software development has become a factory-like process, requiring code designed for AI agents, pipelines, and other developers, not just end-users. It calls for modular, testable, deterministic code that can be assembled at scale as interchangeable parts.
Edsger W. Dijkstra argues that teaching computing science has been cruel by demanding formal reasoning from students without providing the necessary mathematical rigor. He contends that programming is a rigorous intellectual discipline akin to mathematics, not a mere technical skill.
Fantasy VC is a simulation game where players run a venture capital fund, making decisions across a simulated decade in about 60 minutes.
As AI workloads surge, data center power consumption is skyrocketing, straining existing grids and forcing operators to rethink energy strategies. The article examines the growing demand for electricity, the limitations of current infrastructure, and the push for more efficient hardware and alternative power sources to sustain the expansion of compute capacity.
This PDF provides an introductory overview of parallel algorithms, covering fundamental concepts such as models of parallel computation, algorithm design techniques, and complexity analysis for parallel systems.
Lee Felsenstein, a key figure in early personal computer development, discusses the history of personal computing and offers his perspective on its future trajectory.
This book examines the evolution of programming methodology in France from the 1960s onward, highlighting key contributions from French computer scientists in areas such as program construction, formal methods, and language design, and situating these developments within the broader history of software engineering.
The author shares their experiences building and modifying a CNC machine, detailing various upgrades, challenges faced, and lessons learned from experimenting with the hardware and software.
A curated list on GitHub collects delightful Bash scripts, tools, and resources for shell scripting, including command-line utilities, prompt customization, and development guides.
MiniForge offers free GPU compute, in-app purchases, and leaderboards for game developers using natural language descriptions to generate game ideas.
This GitHub repository provides a Linux-based cross-compiler toolchain setup for AMIX (Amiga Unix), enabling developers to compile software for the Amiga Unix environment from a Linux host system.
Neumann probe is a browser-based game where the player manages a self-replicating space probe that explores the galaxy. The game can be played through a web interface or accessed via an API for programmatic interaction.
RewindOS is a local, open-source tool for Linux that records screen activity and makes it searchable. It captures screenshots, performs OCR, stores clipboard history, and logs window titles entirely on-device without internet access, providing a privacy-focused way to revisit past desktop sessions.
Unicorn is a lightweight, multi-platform CPU emulator framework that supports multiple architectures including ARM, MIPS, x86, and more. It provides a clean and simple API for emulating CPU instructions in different environments, making it useful for security research, reverse engineering, and binary analysis.
OmniPreview enhances Mac QuickLook with support for 29 file formats, including code syntax highlighting, ZIP and folder browsing, and previews for Markdown, diff, images, audio, video, text, and PDFs.
The article discusses the concept of "electrifying the cow path"—applying new technology to existing, suboptimal workflows instead of rethinking processes from scratch. It argues that while incremental improvements can be useful, true innovation often requires redesigning systems rather than just digitizing old habits.
The article explains that data centers can connect to the electric grid faster if they agree to flexible power arrangements, such as reducing consumption during peak demand. This approach helps utilities manage grid strain while speeding up data center construction timelines.
The article discusses the history of ASCII art and the development of the Jgs font by Jérémie G. and Lucas S. at Velvetyne, a type foundry. It explores the relationship between early computer graphics, typographic constraints, and creative expression using character-based imagery.
A comparison of x86 hypervisors (KVM, Hyper-V, Xen, VMware ESXi) and emulators (QEMU, Bochs), covering their architectures, features, and performance. Hypervisors leverage hardware virtualization for near-native performance, while emulators prioritize compatibility via software CPU translation at a speed cost. The article also covers live migration, snapshots, and GPU passthrough.