... agent writes the code who s actually testing it? Do you still go through edge cases and user scenarios manually, or are you also delegating please break my app to another agent now? Has testing become more systematic and automated in your workflow, or you just moving faster with fewer guardrails (and let users break

... loud failures and inherits a latency problem for the quiet ones, which means the breaker needs the same retroactive re-binding we built earlier: when a previously-"fine" outcome later reveals itself as bad, it has to be able to reach back, retrigger the breaker

... product discovery changes as teams grow. At small scale it s fast and intuitive, but at larger scale it often becomes fragmented, slow, or disconnected from the actual system. From your experience-what s the first thing that breaks in discovery workflows when teams scale? Comment from Maya Elor(@maya_elor): @sunshinemiller  Totally agree, the drift from real user signals is exactly what we keep seeing. What s interesting is that it s rarely just a data problem ... ... build phase, which is exactly what we re trying to do with Athena by continuously carrying that signal through the process, not just capturing it upfront. Comment from Sunshine Miller(@sunshinemiller): @maya_elor Usually the first thing that breaks

... found 2 potential bugs and fixed them. We started feeling safe again. Then at 3am, our site went down. Claude had updated a core dependency to the latest version. It worked in test. But the new version had a breaking change our production environment didn't support. No human would have made that mistake. Day 6: The blame game. We spent the morning restoring the site. Asked Claude what happened. It explained the dependency logic perfectly. It acknowledged the mistake ... ... command, and it worked. It s important to describe the problem clearly and provide plenty of details. Comment from Mateusz M ynarski(@mateusz_mlynarski): I use Claude's code daily, and you're right. It fixes some things but breaks

... Figma plugin for testing multilingual UI earlier in the design workflow. The focus is simple: help teams see whether a screen still works after translation, especially when layout, mixed-language content, and UI consistency start to break down. The idea behind it is the same one that keeps me building it: your design should hold up in every language. If you re building a product, you re already building for a global market. Would love feedback from anyone working ... ... treating text in isolation. Context-aware within each screen Labels, actions, and values are interpreted more accurately in their UI context. More reliable translations Fewer subtle mistranslations especially for short or ambiguous UI text. Better layout fit without breaking

... open to full-time, part-time, freelance, etc. How to get in touch Drop your post below and feel free to reach out to others in the thread Below are some opportunities from the latest issues of The Breakpoint. [1] [2] [3] [4] No affiliation here. Also, most of them are hiring across the board. @Kilo Code is hiring a Senior Software Engineer, remote EU @Knock is hiring a Platform Engineer, hybrid NYC @Laravel is hiring a Technical Support Engineer ... ... More open roles in the previous editions: Hiring? Looking for work? [Startup Roles February 2026] Hiring? Looking for work? [Startup Roles January 2026] Hiring? Looking for work? [Startup Roles December 2025] Hope it helps! Keep it up [1]: The Breakpoint

... Meow world, welcome back to The Breakpoint, a weekly thread on all things dev tools on Product Hunt. The latest Recent dev-first products launched on the site @1Code is an open-source Cursor-like UI for @Claude Code @Recent.dev notifies you about the latest changelog updates in real-time @cubic launched 2.0 to help you read, trust, and merge AI-generated code @Sled lets you run your coding agent from your phone with your voice - powered by @Layercode @Simpl ... ... thread, Ilia is discussing prompt engineering best practices: how/where to save and organize your prompts, how to improve them overtime, depending on the models. Contributions highlight the importance of a spec-driven approach, starting with the expected outcomes then breaking

... doing so felt wrong on a human level because we were motivated by the idea of going on a fun, ambitious journey together. But it also felt illogical on a strategic level. Most startups fail because the cofounders break up more so than failing to find  product-market fit . (source = I made it up, but it s extremely common and often business problems can be traced back to dysfunction at the top) Therefore, I d argue you should just ... ... minimize the risk of you and your cofounder breaking