> If you ask developers "why can't I do XYZ", you'll likely get an answer along the lines of "why do you need to do that" or "justify your usecase". This is th

> If you ask developers "why can't I do XYZ", you'll likely get an answer along the lines of "why do you need to do that" or "justify your usecase". This is the difference between application programming and infrastructure programming. When doing app development, it's best to limit scope as much as possible in order to reduce risk. If you don't need it, toss it. On the other hand, infrastructure only exists to reduce overall risk across all apps. It does this by accepting risk and dealing with the gnarly bits so apps don't have to. Put too much opinion into infrastructure, and that pushes that risk onto all of the apps. Often, the apps don't have the leverage to deal with that, so people stop using the infrastructure.