# Why software engineering teams should prioritize a sustainable pace over speed

DevFeed: [Why software engineering teams should prioritize a sustainable pace over speed](<https://devfeed.tech/articles/the-negative-split-software-engineering-effect-32335.md>)

Original publisher: [Read original article](<https://newsletter.manager.dev/newsletter/the-negative-split-software-engineering-effect>)

Author: Anton Zaides

Published: 2026-05-05T06:01:00Z

Content type: opinion

Language: en

Sources: [Manager.dev](<https://devfeed.tech/sources/manager-dev.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Development](<https://devfeed.tech/topics/development.md>), [ai-coding](<https://devfeed.tech/topics/ai-coding.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [cursor](<https://devfeed.tech/topics/cursor.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

## AI overview

The article uses the idea of a negative split in distance running to argue that software engineering teams should begin at a sustainable pace instead of pursuing speed immediately. It warns that rushing can create technical debt and architectural shortcuts that eventually slow teams down.

## Source excerpt

Engineering teams don't need to 'just go faster' - the technique behind the sub-2-hour marathon