Pretty sure you did it well. Most don't
-
-
Replying to @PaulDJohnston @jtopper
Thanks :) but I also legitimately want to understand where others are failing
1 reply 0 retweets 0 likes -
Replying to @southpolesteve @jtopper
The failure generally comes from seeing GraphQL as a magic bullet to stop front end people from annoying back end people by giving them a way of accessing data without having to create an endpoint over and over. I get it. But 1/x
2 replies 0 retweets 1 like -
What generally happens is that either the front end devs overstep their bounds and do complex things and cause issues or the back end devs don't foresee something that seems obvious to the front end and end up with load/bottleneck issues. 2/x
1 reply 0 retweets 0 likes -
If the team is well managed and aligned then all good. If not then... You're storing up issues down the line. Technical debt in some form. It can be avoided but it is a problem.
1 reply 0 retweets 0 likes -
Replying to @PaulDJohnston @jtopper
This tweet could apply to literally any technology. People seeking Magic Bullets will always have a bad time
1 reply 0 retweets 0 likes -
Replying to @southpolesteve @jtopper
Good point. I'm applying it here though. And no tech team ever thinks it applies to them btw
1 reply 0 retweets 0 likes -
Replying to @PaulDJohnston @jtopper
and? serverless brings new benefits but also new challenges. There are some good resources out there about emerging best practices. Sticking to those will help you deal with challenges and derisk adoption.
1 reply 0 retweets 0 likes -
whoops! Typed serverless but meant graphql
1 reply 0 retweets 0 likes -
Replying to @southpolesteve @jtopper
"emerging best practices" on the day I write a "serverless best practices" blog post...
1 reply 0 retweets 0 likes
I wrote mine last yearhttps://gist.github.com/southpolesteve/08edb6a481c07f66eb71e4df619827ae …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.