Are you arguing that you can keep velocity while building up technical debt? The company "smartly" using libraries might stuck maintaining a monster of depende

Are you arguing that you can keep velocity while building up technical debt? The company "smartly" using libraries might stuck maintaining a monster of dependencies that only ever was meant to be an MVP. It will require 10x more engineers and while they might move fast at the beginning, they will only slow down over time. The company minimizing their dependencies and paying attention to their stack will be able to add complexity over time without breaking a sweat. Their costs will be 10th the cost, and they will be able to run profitably. I am not anti-library or anything, but e.g. adding sci-py to your python project just because you need a gaussian function in one place in your code is just lazy. Managing dependencies wisely is one of the hardest thing in software development. It's right after cache invalidation and naming things ;)