The linear developer experience

What this post added

This post introduces the concept of a 'linear developer experience' for complex distributed systems, advocating for frameworks that treat workflow orchestration as 'distributed systems as a service'. It argues that such systems should handle state persistence, retries, error recovery, and timing automatically, allowing code to remain a readable sequence of steps. This approach aims to avoid the 'tipping point' where developer experience deteriorates as systems scale, contrasting it with traditional event-driven architectures and distributed choreography that can lead to infrastructure bloat and debugging challenges.