4 ms·
Exactly - YAGNI essentially says you don't need TODOs littering your code. You can cross that bridge if and when you get there. Your disclaimer is interesting.
by taylodl 9y ago
Exactly - YAGNI essentially says you don't need TODOs littering your code. You can cross that bridge if and when you get there.
Your disclaimer is interesting. What's more useful than a code base littered with potentially useless TODOs is a codebase containing an explicit set of assumptions agreed upon by the product stakeholders, product owner and implementation team. Then when some aspect of that implementation was influenced by one of those assumptions, say your n=200 and the assumption was n<=500, then you can reference the assumption right there in your code. Then if at some later point in time that assumption should change you can easily find all the code needing to be revisited.