Life as a developer has taught me to take the other side of your argument. I'd disagree on this. Once you release something to the wild you need to have robus

Life as a developer has taught me to take the other side of your argument. I'd disagree on this. Once you release something to the wild you need to have robust controls in place to prevent one person or group of people from using all your resources. I wouldn't release a product that doesn't have rate limiting of some kind, of which a captcha is one way to rate limit. Always trust people to push the boundaries of your app as far as they possibly can. I have yet to build a system where someone doesn't. And that includes tools I've built for inhouse users:( Whether intentionally or not, they always find a way to push the boundaries:)