Median SaaS product lifespan on SaaSHub's graveyard drops from about 4 years to 1.5

·1 views

SaaSHub's product graveyard, which tracks the status and lifespan of hundreds of thousands of products, showed median lifespan holding near four years for a long period. A sharp decline in 2026 has reportedly brought that median down to roughly 1.5 years. The author attributes the drop to cheap, AI-assisted software creation, which lets many people release products quickly and abandon them when they prove unviable or fail to attract customers. The author argues that distribution and marketing now matter far more, and speculates the trend may continue or that users may eventually build their own tools, leaving a few large platforms dominant.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Why Rewriting a JSON File in Place Can Leave Readers With Broken Data

A developer's page-building script repeatedly failed with JSONDecodeError because it read a JSON index while another script was rewriting it. Testing on Linux with Python 3.10.12 showed that open(path, 'w') truncates the file before new data is written, so readers often saw empty or partial content. Killing the writer mid-write also left a corrupted fragment with no intact version to fall back on. Writing to a temporary file and then swapping it in with os.replace eliminated the broken reads in the same test. The author notes three related pitfalls to watch for: a temp folder on a different filesystem, file permissions, and symlinks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Unpinned CI actions and runaway concurrency prompted a zoned pipeline redesign

A team's CI pipeline suffered two costly failures in one quarter: a mutable action tag that was silently changed to push commits, and a concurrency misconfiguration that queued over 1,100 jobs and exhausted weeks of runner quota. To address these, they split the pipeline into an untrusted pull request zone with read-only permissions, no secrets, and aggressive cancellation, and a trusted publish zone limited to main that inherits secrets and never cancels mid-flight. Third-party actions are now pinned to commit SHAs with version comments for readability. The redesign also included disabling persisted checkout credentials and keying the browser cache on the lockfile, plus an agent smoke test to catch session-handoff failures that unit tests miss.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

agent-doctrine: Open-Source Prompts for Getting AI Agents to Ship Tested Code

The sisig.ai team has open-sourced agent-doctrine, a set of prompts, role definitions and skills meant to make AI coding agents produce tested, mergeable pull requests. Every agent follows the same pipeline of scouting, gating, planning, implementing, reviewing, consolidating, verifying and shipping. Before any edit, the lead agent must answer fifteen questions from a TENETS.md file with evidence, such as the smallest correct change and the blast radius. Users choose a fast mode, which keeps the gate and per-diff review, or a rigorous mode, which adds plan simplification, adversarial review and approval before code. The project is MIT-licensed, requires Git and Bun, and rewrites global agent instructions, so users are advised to back up their configuration first.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Claude 3.5 Sonnet, GPT-4o-mini, or Gemini 1.5 Pro: Testing Chatbots for E-Commerce Support

A developer guide argues that the best chatbot API for e-commerce support should be chosen by testing with real support tickets rather than relying on generic leaderboards. It recommends Claude 3.5 Sonnet for the most natural conversational quality, GPT-4o-mini for faster, budget-friendly deployments, and suggests testing Gemini 1.5 Pro before deciding. The author proposes scoring label accuracy, escalation decisions, required output format, and tone separately, and running each test more than once to avoid relying on single responses. The article also advises designing the API boundary so the chosen model can be swapped without rewriting the triage workflow.

0 comments Read more at DEV Community