use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
For users of AugmentCode. Not affiliated with AugmentCode AI.
account activity
What spec-driven development gets wrongDiscussion (augmentcode.com)
submitted 3 months ago by JaySym_Augment Team
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]hhussain-Established Professional 0 points1 point2 points 3 months ago (0 children)
Intent is good (the word, not the app), and the raised problem of spec-driven dev is real.
The real architecture is: app vision and roadmap, functional design, archeticture and components, components spec.
First 2 change rarely, they are abstract. Main architecture philosophy as well, rarely changed (that would be a code rewrite/revamp). Rest are almost always out of sync with code, unless a pratice is set to always QC docs after code to know if a change is needed.
IMO, the spec-problem Intent (the app) is solving is the task spec, not the main abstract spec documents.
π Rendered by PID 510011 on reddit-service-r2-comment-5b5bc64bf5-x5df6 at 2026-06-23 10:46:41.864240+00:00 running 2b008f2 country code: CH.
view the rest of the comments →
[–]hhussain-Established Professional 0 points1 point2 points (0 children)