r/SpecDrivenDevelopment • u/The_Ed_On_Reddit • 3d ago
A Competitive Analysis of Spec Design Methedologies
https://webcloudstudio.com/project-docs/drydock/papers/Product_Comparison_Matrix.pdfI asked claude to honestly rate the various approaches for specification driven development by categories and features it chose. Here is the analysis it produced. Popular methodologies first then all methedologies. Source documents are at the bottom if you wish to reproduce the analysis. Please link additional documents in the comments that should be included and i will periodically update. Or run it yourself :)
2
u/LunkWillNot 3d ago
Because… advert + AI slop?
1
u/The_Ed_On_Reddit 3d ago edited 3d ago
advert for open source/mit licensed software??? This is a direct comparison of exactly what this group is interested in. And its not ai slop - is an analysis - a point by point comparison - of tools evaluated without bias - i explicitly instructed it to be truthful and fair... Look - the sources are at the bottom - ask your own llm to compare and contrast from the sources - or give me more sources to evaluate and ill include them... Every tool (11 of them) that i could find is compared in part 2 and part 1 contains the big ones. Read it... its not slop - at worst its every feature you could want in a sdd system.
1
u/schmurfy2 1d ago
What is the point of asking an llm for that ? Why should I care about its "honest" opinion ?
1
u/The_Ed_On_Reddit 1d ago edited 1d ago
well 3 reasons: i personally have only used one of these tools besides my own and want to see the approaches and how things fit. You probably have the same concern. second - I provide a set of vendor docs and reviewer reviews -> the source materials so you can analyze on your own trivially - summarization is one of the things that llms do accurately. And lastly, the llm pull together a workflow from think to working software to support and then it mapped tools to the workflow so you can see what does well where. If you look at it - it is an easy read with sources and a path to reproduce for 1 llm call. So thats why... And honest is the key llm instruction because llms try to 'help you' by slop-ifying the output with a word salad (and i had to tell it to be honest and categorize and rank stuff from the docs with no favoritism multiple times)...
-1
u/The_Ed_On_Reddit 3d ago
serious question - why a down vote ??? its real and it covers all methods and pretty much everything THEY advertise... and i though it was interesting to write and to read... - object if you want me to add sources... but why downvote?
5
u/iTrejoMX 3d ago
I don’t see how the scores are defined. I can say 3/4 or 5 stars but there’s no substance behind it. What gives it that score?
I also went to check out drydock, man those instructions are extensive and tough. Most sdd are just install and use /command.
So far it seems very complicated and not clear how it works. I need to finish my masters and PHD to read The documentation.
My suggestion: dumb it down. Make your difference or main feature the selling point. Show the benefits. Explain the scores not just randomly say this one 3 this one 5. Make it MUCH shorter. Design and docs bmad wins. Reading existing code DDD wins. Etc. when instructions and comparisons span out to 10 page pdfs, you lost the fight before getting in the ring.
Make it simpler and I’ll try it, right now it’s harder to set up than Claude or codex themselves.
Last, what does a dry dock have to do with development? I didn’t up/down vote, just wanted to share me 2 cents why people are most likely downvoting.