> it can just be building a minimal chess quickly using methods/frameworks that are not easily extensible to future requirements related to chess.
You should not build something you do not need if you know it is wrong and you will not need it.
That is just wrong.
Many engineering managers do this to “show progress” but this is because they are bad at their job.
On the other hand, if you need it so the UI team has a mock to work against (so that they can explore what interfaces they really need), it isn’t debt at all.
You should not build something you do not need if you know it is wrong and you will not need it.
That is just wrong.
Many engineering managers do this to “show progress” but this is because they are bad at their job.
On the other hand, if you need it so the UI team has a mock to work against (so that they can explore what interfaces they really need), it isn’t debt at all.