I am a Senior Full-Stack Engineer. My main experience is in Java/Spring + TS/JS/Angular/Vue and DevOps but I love new technologies and software architecture, standards and engineering.
Yes, initially. But with time the high code coverage and quality leads to lower technical debt and thus leads to much less development time.
I have worked in low quality with no unit tests legacy solutions and I have worked in enterprise software that applied TDD with high code coverage (80%+) and the much lower technical debt led to that in the legacy solution I what to take almost a week to develop what I can develop in an afternoon with TDD.
TDD payoffs in the long run and that's why it only makes sense if the project will be a long term one and not some side project. And for startups developing their MVP, TDD won't make a lot of sense as they need that initial speed boost more than higher maintainability in the long run.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, initially. But with time the high code coverage and quality leads to lower technical debt and thus leads to much less development time.
I have worked in low quality with no unit tests legacy solutions and I have worked in enterprise software that applied TDD with high code coverage (80%+) and the much lower technical debt led to that in the legacy solution I what to take almost a week to develop what I can develop in an afternoon with TDD.
TDD payoffs in the long run and that's why it only makes sense if the project will be a long term one and not some side project. And for startups developing their MVP, TDD won't make a lot of sense as they need that initial speed boost more than higher maintainability in the long run.