Gates' 'Human Reserved' Idea: Meaningful Oversight or Just a Human Rubber Stamp?

·2 views

Bill Gates has proposed the concept of 'Human Reserved' roles, arguing that certain tasks — such as delivering terminal diagnoses or caring for the elderly — should remain under human responsibility even when machines could technically perform them. He compares this to nature reserves, where society deliberately protects areas from development despite their technical availability. However, critics point out a core flaw: designating humans as decision-makers means little if those individuals lack the time, expertise, or authority to genuinely challenge an AI's recommendation. In such cases, the human becomes a 'meatproxy' — someone who lends formal legitimacy to a decision already effectively made by a machine. Gates' original essay acknowledges this complexity, advocating for hybrid models where AI augments human capability rather than simply replacing human presence in a workflow.

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)

AI Coding Assistants Are Reshaping How Developer Documentation Should Be Written

AI coding assistants are transforming the developer journey by often consuming API documentation before a human developer ever does, making documentation quality more critical than before. Developer Relations professionals are being urged to write clearer, more complete docs — with concrete code examples, explicit error messages, and well-structured READMEs — so both humans and AI agents can act on them correctly. Vague instructions and happy-path-only documentation leave gaps that confuse both developers and AI tools trying to complete real software tasks. Rather than creating a separate category of 'AI documentation,' the recommendation is to raise the overall standard of developer experience so content is unambiguous and actionable. The core DevRel question for 2026, the article argues, is whether documentation is clear enough for both humans and machines to use without guessing.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Gate DeFi Protocol Rated High-Medium Risk as $6.6B TVL Faces Liquidity Vulnerabilities

A DeFi security assessment dated September 2, 2026, evaluated Gate, a cross-chain liquidity aggregation and yield-optimisation protocol currently holding approximately $6.65 billion in total value locked across Ethereum and multiple Layer 2 networks. The protocol received an overall risk rating of 7 out of 10, driven by concerns over liquidity concentration, with 71% of TVL held in just three core vaults. Analysts identified flash-loan-driven vault drains and oracle manipulation on low-liquidity L2s as the most significant threat vectors, with simulations showing a potential loss exceeding $500 million if a core vault were targeted. Additional risks include a short 24-hour governance timelock for a protocol of its size, cross-chain bridge exposure covering 22% of TVL, and a re-entrancy vulnerability in reward-distribution hooks. The findings were based on on-chain data analysis and a review of smart-contract source code audited by CertiK in 2023.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How One Tech Team Built a Multi-Region Routing System in Under 2 Months

A technology team expanding their Australia-based platform to the United States faced a tight two-month deadline to build a multi-region routing system on Cloudflare Workers. The core challenge was that simply routing users by geography was insufficient, as logged-in users could be travelling or using VPNs, and admins needed seamless access to both regional clusters from a single account. Teaching materials shared across regions added further complexity, since a link created in one region needed to be accessible to users in the other. The team chose not to shard their Firebase authentication service to avoid redirect loops between regions, while opting to shard other databases like Neo4j for simplicity. The result was a purpose-built routing layer designed to balance latency, data consistency, and cross-region usability across two distinct Kubernetes clusters.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

CQRS Pattern Explained: Separating Read and Write Models for Scalable Systems

CQRS, or Command Query Responsibility Segregation, is a software design pattern that separates the models used to update and retrieve data in an application. Coined by Greg Young and rooted in Bertrand Meyer's Command-Query Separation principle, it addresses performance and complexity issues that arise when a single data model handles both reads and writes. In a CQRS architecture, commands handle state-changing operations with strict validation and business rules, while queries fetch pre-aggregated, denormalized data without side effects. This separation allows write storage to be optimized for transactional integrity while read storage is tuned for fast, UI-friendly data retrieval. The pattern is particularly valuable as systems scale in complexity and throughput, where a unified CRUD model can lead to lock contention, unwieldy joins, and compromised domain boundaries.

0 comments Read more at DEV Community