Thread

1. itissid · 1790282466 · focus · HN ↗

   very cool. Congrats on the launch. first half of 2026 was the year when every one made such internal tools one way or another. I am happy you guys could build a product out of it.

   The cool thing is even though this tool addresses a few, use case for reducing cognitive load, they happen so frequently that they add up.

   I think they key with cognitive load is that the agents often produce a lot of trace/docs etc, in the end only a small % of the traces really are important to the final changes, because concise changes are typically very small and self contained.

   One thing i see this becoming important with is maintaining internal tooling built using this. I maintain an internal docs system that helps me do designing before i build code, that docs system is completely vibe coded and i can add features to it very fast, but now its all grown up. A challenge then is can i understand just enough about a new proposed change to approve it? That is key to the doc system not becoming a burden in of itself, while maintaining a tight core feature set.

   1. sidharthkmenon · 1790286168 · focus · HN ↗

      > end only a small % of the traces really are important to the final changes, because concise changes are typically very small and self contained.

      yes, totally. i think this is mostly 1 piece of the broader puzzle. we found that, esp. for complex changes where i need to spend my brainpower anyways:

      > A challenge then is can i understand just enough about a new proposed change to approve it?

      whiteboard has been a powerful tool for us! i think much more of this needs to be instrumented as part of a larger system, as you said (we are thinking the same way btw: <a href="https:&#x2F;&#x2F;dev.fast&#x2F;about&#x2F;">https:&#x2F;&#x2F;dev.fast&#x2F;about&#x2F;)

   2. code-sonar · 1790296587 · focus · HN ↗

      [dead]

Unofficial Hacker News client; not affiliated with Y Combinator.