Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the change easy, this might be hard. Then make the easy change. #140

Open
ridget opened this issue May 3, 2018 · 1 comment
Open

Comments

@ridget
Copy link
Member

ridget commented May 3, 2018

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?

@jawdinmorris
Copy link

As a new developer petrified by design decisions i'm very interested in this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants