It can be a very bad thing or an acceptable payment for developer velocity, based on what's your business priorities with the project. I have a couple of issue

It can be a very bad thing or an acceptable payment for developer velocity, based on what's your business priorities with the project. I have a couple of issues that I worked on that started exactly like this: front-end developer implemented a feature based on GraphQL, but when we deployed this feature, we quickly disabled it after receiving alerts from production database, and re-enabled it back only after backend developer (me) went and worked on database indexing. But for my team, at the current point of the project's development, this scenario is a net positive overall, because we're exactly in "move fast and break things" mentality, which suits our product and our place in the market. If our project would require a lot of 9s, or worked with very confidential data, or had 10s of millions of daily users, we would have completely different internal procedures and development practices: much safer and much slower. Also, I wrote about this exact problem in another thread under this post: https://news.ycombinator.com/item?id=25014918 https://news.ycombinator.com/item?id=25014918