Survivorship Bias: Why Success Stories Can Lead You Astray

·1 views

Survivorship bias is a cognitive blind spot that causes people to learn only from those who succeeded while ignoring the far larger group who failed doing the same thing. The concept gained prominence through WWII statistician Abraham Wald, who warned the military against armoring planes based on damage patterns seen only on returning aircraft — the planes that crashed told a different story. This bias pervades everyday advice, from startup culture and investment tips to career and relationship guidance, where visible success stories vastly outnumber the silent failures. Because unsuccessful people rarely write books, give interviews, or appear on podcasts, the pattern of risk-taking appears to be a reliable formula for success when it often is not. Experts suggest countering the bias by actively seeking failure stories, asking about base-rate success percentages, and questioning the true odds behind any celebrated success narrative.

Read the full story at DEV Community

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

Discussion (0)

Builder Design Pattern Solves the Monster Constructor Problem in Python

A software team at a scientific publishing company faced a growing complexity problem while building a manuscript submission system that required 13 constructor parameters. The initial class design led to what developers call the 'monster constructor' problem, where positional arguments become unreadable and context-free. Attempts to fix it using default None parameters introduced a new issue: mandatory fields like title and authors could be silently skipped, causing downstream failures. Adding inline validation to the constructor made the code even more bloated and harder to maintain. The Builder design pattern is presented as a cleaner solution that separates object construction from validation, enforces required fields, and improves readability at the call site.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Ethereum Foundation cuts 20% of staff as L2 growth strains base layer value

The Ethereum Foundation announced in June 2026 that it would eliminate approximately 54 positions, representing a 20% workforce reduction, alongside a roughly 40% budget cut. The Foundation cited a need to refocus on its most critical priorities, while several senior leaders had already departed in the months prior. Despite Ethereum's strong institutional standing — bolstered by ETF approvals and widespread adoption as a smart contract standard — a growing share of on-chain activity and revenue is being captured by Layer-2 networks rather than the base layer. Many L2s operate with independent tokens and ecosystems, meaning less economic value flows back to ETH itself. Analysts and observers note a broader shift in developer sentiment, with more teams choosing rival chains that offer faster iteration cycles and clearer product narratives.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Nylas Agent Accounts Let HR Bots Own a Mailbox and Automate Onboarding

Developers can use Nylas Agent Accounts to give an AI-driven HR agent its own dedicated mailbox, such as hr@yourcompany.com, enabling it to send and receive emails autonomously. The agent handles a structured onboarding checklist: sending welcome emails, requesting forms like the I-9 and direct-deposit documents, and booking orientation once signed forms are returned. Inbound replies are surfaced via webhooks filtered by a unique grant_id, allowing the application to detect and extract attachments programmatically. Unlike shared inboxes or mail rules, this approach gives the agent a real calendar identity so orientation invites and RSVPs route through a single, auditable account. The setup requires a Nylas application, API key, a verified sending domain, and a publicly accessible HTTPS endpoint for webhooks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Timezone Bug in a Calendar App Reveals a Deeper Developer Mindset Problem

A software developer on DEV Community illustrates how focusing too early on technical implementation — rather than user-facing behaviour — can introduce subtle but serious bugs. The example centres on a hypothetical calendar app where clicking a date marks the wrong day as a holiday, a fault reproducible only in certain timezones such as Tokyo. The root cause is a mismatch between how two developers interpreted the same Date object: one treating it as local time, the other serialising it using UTC methods. This discrepancy means a date like March 1st at midnight in Tokyo is saved as February 28th in UTC, shifting the marked holiday by one day. The author uses this case to argue that developers must fully understand the business and user requirements of a feature before writing any code.

0 comments Read more at DEV Community