3 ms·
But that repurposing/removal is exactly what's avoided if you follow through with the SEF framework he outlines. I have to push back on the idea that token cos
by reg_dunlop 4mo ago
But that repurposing/removal is exactly what's avoided if you follow through with the SEF framework he outlines.
I have to push back on the idea that token costs balloon when using TDD within the context of a strong framework such as Jason has laid out here.
If the feature is repurposed/removed/refactored....I'd argue the specification wasn't well thought out prior to burning into tokens.
We're so eager to do a lot of the wrong things quickly, when it may serve us better to do a more precise thing slowly.
- zuzululu 4mo agoYou cant spec out what you dont know, scope, requirements change from real world feedback
- reg_dunlop 4mo agoThen adjust the specs with the scope and feedback. I fail to see the argument you're making... Features aren't made in a vacuum. If specs are made/written....with the information available now...then it's better than not writing specs. Writing specs with incomplete information is better than not writing specs with incomplete information.