Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
You're definitely right, the complexity of rollbacking a feature or change varies. And going into any major change it useful to consider "How would you roll things back?" In this case, the feature was a query change (and introducing new classes to help build that query). That made the rollback easy.
Were I to "migrate liquid tags usage" in production that would be a far more complicated rollback plan, because those tags uses are stored in the database.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You're definitely right, the complexity of rollbacking a feature or change varies. And going into any major change it useful to consider "How would you roll things back?" In this case, the feature was a query change (and introducing new classes to help build that query). That made the rollback easy.
Were I to "migrate liquid tags usage" in production that would be a far more complicated rollback plan, because those tags uses are stored in the database.