On the surface, this is correct. However, "long-term" in my experience starts showing within a month of development.
That is: If you rushed and prioritised immediate results, you will begin to stumble and lose pace within a month.
Not doing clean code/architecture and other practices (like TDD, CI/CD, etc.) from the start is sensible only if a project is estimated to not last longer than a couple of months. That is - if the entire feature set can be completed after a couple of months and there are no new feature requirements after that. Ever.
I have never seen a project like that except prototypes & demos.
For further reading, check out these two articles by Martin Fowler:
On the surface, this is correct. However, "long-term" in my experience starts showing within a month of development.
That is: If you rushed and prioritised immediate results, you will begin to stumble and lose pace within a month.
Not doing clean code/architecture and other practices (like TDD, CI/CD, etc.) from the start is sensible only if a project is estimated to not last longer than a couple of months. That is - if the entire feature set can be completed after a couple of months and there are no new feature requirements after that. Ever.
I have never seen a project like that except prototypes & demos.
For further reading, check out these two articles by Martin Fowler:
martinfowler.com/bliki/DesignStami...
martinfowler.com/articles/is-quali...