Skip to content

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

Open
@ridget

Description

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?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions