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. milanb · 1790281207 · focus · HN ↗

      I think you’re on the money with the problem of maintaining (another) source of truth.

      Speaking from personal experience, I still find myself reaching for Whiteboard. It’s helpful when it’s critical for me as a developer to understand the implementation, which is certainly not every change!

      In the future, we want to deliver a hosted product that addresses the N+1 concern you raised. The problem with the existing tools is that plans don’t stay up to date with what the agent decided to implement, and the back-and-forth that happens after the initial prompt isn’t captured. We believe a single whiteboard canvas can be used to capture not only a plan at design time, but what happens after.

Unofficial Hacker News client; not affiliated with Y Combinator.