ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
vnprc71d ago
is it an antipattern to write a spec and implement it twice yourself to get the spec merged?
๐Ÿ’ฌ 7 replies

Replies (7)

Pete Winn ๐Ÿ”†71d ago
Now youโ€™re thinking
0000 sats
vnprc71d ago
it's a serious question! i have never written a (successfully merged) spec before. seems like the key goal is to disambiguate any possible misunderstanding of the important implementation details while leaving the rest of the decisions up to the implementor. does this require two different individuals to implement it? if an llm is implementing it, are two different prompts sufficient?
0000 sats
vnprc71d ago
i'm overthinking it, just write the damn code and push out the PR
0000 sats
YODL36d ago
Where'd you go? :(
0000 sats
Pete Winn ๐Ÿ”†71d ago
Yep. The spec is only relevant if a second person (and more) want to build it. Just build useful stuff the specs will sort themselves out if theyโ€™re needed.
0000 sats
vnprc71d ago
i have undertaken the task of writing and implementing the spec, as requested by the team > the specs will sort themselves out if theyโ€™re needed they are needed and i am the guy to make it happen
0000 sats
Pete Winn ๐Ÿ”†71d ago
See ๐Ÿ‘€ - its working! > they are needed and i am the guy to make it happen
0000 sats