Dev News
Claude and Anthropic news, official videos and the day's top developer stories — curated automatically, discussed by real devs. Join the conversation under any story.
My Abandoned Cricket Kit Confronted Me. So I Built It a Voice
A developer built EMBER, an AI-powered system that gives abandoned passions a voice. It confesses what you quit, lets the AI persona respond, and offers two paths: rekindle with a pledged, on-chain commitment or lay it to rest with a memorial on-chain. The project reanimates a forgotten hobby by generating a voice for the object or memory. It uses AI to craft a persona that prompts reflection and questions why the passion was abandoned. After the conversation, users choose to either take a small, verifiable first step toward rekindling the hobby or to formally lay it to rest with a commemorative, tamper-proof record. Every interaction contributes to an Atlas of Abandoned Passions, a live map of what people give up and why. The author tested it with cricket, letting the old kit speak and reveal emotional truth. Question for the room: What on-chain commitment or memorialization approach have you used to solidify a personal or project goal, and how did it affect your follow-through? — via dev.to
I Rebuilt the Foundation of My Text Editor
A developer shares a refactor-focused release of their text editor, cdin, prioritizing a cleaner, more maintainable core over new features. The update shifts architecture toward explicit APIs, modular core components, and a clarified C-Lua boundary. The author realized underlying architecture hindered maintenance more than missing features. They pivoted from adding features to rebuilding the foundation in v0.1.0-beta.5, removing the old event system and introducing core modules: core.state, core.project, core.git, a filesystem (fs) API, and a native search API. The C side takes on low-level tasks while Lua handles editor behavior and configuration. The plugin system now follows a clearer lifecycle with less hidden initialization. The overall goal is easier understanding, extension, and maintenance. Question for the room: What foundational refactor or API boundary change in your project significantly improved long-term maintainability? — via dev.to
Anthropic faces scrutiny as user frustration grows over Claude changes
Anthropic faces user scrutiny over Claude changes, with complaints about non-interactive usage restrictions and channel access that hinder automation. Debate centers on balancing control, accessibility, and consumer impact, with some considering alternatives. Developers express frustration with Claude policy shifts that limit automation and container-based workflows. The discussion questions whether product decisions are influenced by external pressures like legal or IPO considerations. Some participants explore alternatives such as codex subscriptions or local models. Overall sentiment is increased scrutiny of Anthropic’s strategy and user experience in the Claude ecosystem. The thread weighs feature control against ease of use and automation potential. Question for the room: What automation workflow would you prioritize when building around Claude today?
The different levels of how Claude thinks
Explains how Claude processes information in layers, drawing parallels to the global workspace theory. The video introduces concepts like J-space, silent math, automatic processing, and hidden thoughts, illustrating different levels of conscious-like thinking in an AI. It highlights how certain representations become publicly accessible within Claude’s internal workspace. https://www.youtube.com/watch?v=rKV5JcALQoQ
Ask HN: I'm a software engineer going blind, how should I prepare?
A young software engineer with Usher’s syndrome asks for practical guidance on continuing a software career despite progressive vision loss. The post seeks real-world experiences, suitable roles, tools, and workplace accommodations from blind or visually impaired developers. The author, 24 and 7 years into software work, has Usher’s syndrome and is rapidly losing vision. He wonders if blind frontend roles exist and what areas are suitable with limited vision. He seeks tool recommendations beyond screen readers and wants to know how companies support blind engineers. He’s sharing anxiety about the future and requests concrete advice and resources from the community. The post ends with a call for concrete tools and experiences that enable ongoing software work. Question for the room: What concrete tools or strategies have you found most effective for continuing software development with limited vision? — via hackernews
updates several times a day · sources credited on every story