I don't really think the tone or the examples of this presentation are all that useful, and while the advice slide[1] seems well-intended, I just think most of

I don't really think the tone or the examples of this presentation are all that useful, and while the advice slide[1] seems well-intended, I just think most of it is only really known post-hoc because reality is not so clean cut. When talking about the speed of computers I also think we should acknowledge the speed of thought - the ease of implementing ideas: the fact that there are so many dependencies means you can quickly make something. But useful prototypes quickly become products, so I can understand some of the author's frustrations. [1] Advice slide: Avoid features that add disproportionate cost Implement things at the right level Understand and minimize dependencies whenever possible Maintain your dependency tree religiously. Examine it regularly Don't use dependencies just to be lazy: understand the costs Finalize your changes before they land, not after