Back

@raiderrobert Not for long, eh.

I guess it depends on definitions
- TODO list items of low to medium import
vs
- Decisions made to ship code fast that we'd not have done if we didn't have resource and time constraints.

Agile = ship often, live with some tech debt
Waterfall = ship it when perfect, tech debt never happens. (Except this is a fantasy, without feedback from shipping code, you can't find the pain points to fix, you just think it will be perfect)

@raiderrobert only if it has no useful functionality

@raiderrobert IMO you intentionally introduce tech debt during the prototyping phase and pay that debt during the refactoring.

Intentionally, because abstracting too early is even worse.

And yeah. You maintain the code base by balancing these two (prototyping and refactoring).