RT @InVisionAppEng: Learn how Freehand routes a diagramming line through an infinite whiteboard canvas in our latest blog post by @panthoma…

Really enjoyed this article. Time spent vs time _well_ spent.

I finally blogged again! I wrote about about our Freehand multi-player architecture and some recent optimizations.

Microservice vs monolith is so often discussed/debated in the SaaS realm. Here's an interesting read that outlines the reasons for converting Istio to a monolith from @christianposta:

@theDiverDK @InVisionApp Good question. It's an engineering level for individual contributors (not management). Generally it means the scope of influence is at the entire company or organization level and there is a larger portion of long term strategy work as opposed to short term tactical work.

@stephanieblack @_havenn I'm so happy for you. Congrats!

Today is my last day at @Strava/@StravaEng. It's been an absolute honor working with everyone here over the past decade. I've made friendships that will last for a long time and I wish you all the best in the years to come. More about what I'm doing next, next week.

Theme of #graphqlsummit so far: caching. It's possible and everyone's doing it.

RT @sangeetan: ⁦@panthomakos⁩ on the story of CD for mobile apps ⁦@Strava⁩ ⁦@ProdEngSV⁩

Anyone have experience or lessons learned from using union types to model common errors (not found, downstream service unavailable) in @graphql schemas? Similar to but for query operations instead of mutation operations.

@BMorearty It was in our use of ActiveRecord. I didn't use bullet in this case. Admittedly I have not used bullet in a while, but we've been replacing or isolating our uses of ActiveRecord in our main app so the gem is less and less useful for us.

@jacobastultz I'll get back to you next month.

@jacobastultz @andyh2 The names don't need to be all that different, but because the namespace is also not used it's confusing. twitter.Future and scala.Future would be clear.

@jacobastultz @andyh2 * that two different implementations of the same concept are referred to by the same name... Promises and Futures might be a close analogy. Similar concepts but the name differentiation helps distinguish the properties of each and expectations when reading code.

@jacobastultz @andyh2 I agree. That both concepts often share the same name in code and docs only makes it more confusing.

@andyh2 The import renaming in Scala clears this up, it's just a bit of a rocky onboarding road.

@BjoernRochel @GraphQL Would like to know more about your experience with Sangria, the makeup of your codebase(s) (monolith, services, etc), how you handle AuthN/Z, if your API is just internal or public as well, how maintainable/performant the code is... I could go on 😂 - my DMs are also open.