4 ms·
to answer your question — YAGNI i’ve seen plenty of questions like this over the years and they invariably lead to premature optimisation nightmare land. buil
by dijksterhuis 2y ago
to answer your question — YAGNI
i’ve seen plenty of questions like this over the years and they invariably lead to premature optimisation nightmare land.
build (or write the docs, in this case) for what’s needed today. what’s needed tomorrow is tomorrow dijksterhuis’ problem.
half the time i’ve been the one asking that question. so it’s not like i’ve been a saint in avoiding this trap.
- apexalpha 2y ago>build (or write the docs, in this case) for what’s needed today. what’s needed tomorrow is tomorrow dijksterhuis’ problem. But LLMs exist today...
- dijksterhuis 2y agobut not everyone is relying solely on an LLM for documentation. humans are still the primary audience for documentation. if it ever gets to a point where no human is reading the docs, worry about it then (or close to no humans). just because a new frontend framework gets released doesn’t mean we should all start switching to it today. it’s the same principle.