Thread

1. asdev · 1790279593 · focus · HN ↗

   I think the issue with this type of product is it creates an N+1 source of truth for teams alongside their other tools. Inherently, this will get out of date as a project progresses. You could have an agent update based on changes, but that would likely degrade the design doc/artifact into unintelligible slop which wouldn't be useful in the future. This is a behavioral/structural problem of software design in general, which I don't think can be solved by software. Perhaps if this is mainly focused on collaboration at design time, but then that begs the question if teams will really want this tool versus using Notion, Linear, Google Docs.

   1. cannonpalms · 1790303136 · focus · HN ↗

      I see this fitting into my workflow more ephemerally. That, or I will use screenshots in some of my existing documentation so it can all rot in one place.

      When using an agent for development, I find that I REALLY miss being able to "see" the shape of the code in my head while I work, and I find that I get bombarded with so much information that I cannot keep track of what the code looks like. This has led to me having to get back to people async on questions they have on a call, etc., because I can't remember exactly how i made something work in the end!

      I will be using this to make sure I understand my own output at a depth I can remember, and I will be using it to do the same for reviewing complex PRs or diving into new parts of the codebase.

Unofficial Hacker News client; not affiliated with Y Combinator.