Migrating Netflix to GraphQL Safely

Re:Migrating Netflix to GraphQL Safely by scotty79 on Monday June 19, 2023 @01:06PM (#36393574)

> So you've reached a point where working together collaboratively is such a burden that you've adopted technologies to circumvent that activity.

On braindead busywork, yes. Please automate everything about it as soon as possible, including communication.

> This suggests that GraphQL adoption is a sign of impending business stagnation. This does in fact align with my experience around GraphQL.

That very well might be. But stagnation understood as predictably churning an app after an app.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by andrewprock on Monday June 19, 2023 @11:06PM (#36399257)

In my experience, braindead busywork is largely non-existent. Yes, there are times when you'll have to do something easy that conforms to code requirements and standards. But when the frontend needs to update something that is coming from a server, there is a real opportunity to discover, illuminate, and even solve architectural issues.

Sometimes that solution is to use GraphQL to make it easier to manage client implementation fan-out and requirement diversity. But GraphQL is never a substitute for communication and collaboration.

[ Parent | on HN ]

Re:Migrating Netflix to GraphQL Safely by scotty79 on Tuesday June 20, 2023 @05:21AM (#36401556)

> In my experience, braindead busywork is largely non-existent.

Lucky you. In corporate environments I worked at it took easily half of the time.

[ Parent | on HN ]