Subscribe for more: [ Ссылка ] — Treating velocity and maintainability as separate concerns is a mistake. Your shipping velocity is directly correlated to how maintainable your code is.

Read this on my blog: [ Ссылка ]

Further reading:
- [ Ссылка ]

Chapters:
0:00 - How do you balance velocity vs. maintainability in a codebase?
0:13 - What the fastest teams' codebases have in common
0:46 - Building for maintainability
1:29 - Why maintainability *is* velocity
2:05 - "Cleaning up tech debt later" is a lie
2:48 - Treat maintainability as a facet of velocity
3:09 - Taking shortcuts causes compounding slowdowns

свернуть