>Culture matters. The “Hack” and “Move fast and break things” culture must make it very hard for developers to focus on quality. Every now and then productio

>Culture matters. The “Hack” and “Move fast and break things” culture must make it very hard for developers to focus on quality. Every now and then production questions the business value for this. Recently my company released a new game feature and we had to throttle it back in a hacky way immediately as user did not like it. However the database calls and code are still being executed. Now the business does not want us to revert the code (or re-implement the throttle in proper way ) as they see no business value in that and fear of breaking other things as part of this "unnecessary" code changes. I tried to explain that we just stopped the feature as it was an emergency as we did not have time to revert and re-push the server. This feature was well tested (not a brand new feature ) so we did not have a throttle . We found a hack and manage to stop the feature so that users are not outraged. May be the right decision was not to tell about the hack to the business at all. They would have have to wait till we revert the code properly and re-push the server. But as an engineer you worry about the product as well, we I could not resist .