Make the change easy, this might be hard. Then make the easy change.
ridget opened this issue · comments
Sometimes your design choices suck. Sometimes you get an opportunity to fix them.
Let's take a walk through a less than optimal design choice, why it was a bad decision in hindsight, and how we refactored our way out to a better place in order to deliver a new feature.
We're going to learn about everything from maintaining a good separation of concerns, pre-planning, refactoring techniques, and building rock solid API's with GraphQL in Ruby. Phew.
Did I mention all this was only for 2 fields?
As a new developer petrified by design decisions i'm very interested in this.