March 6, 2023

Linear Developer Experience

Most software operates in non-static systems; it is designed to grow in some way — more users, more data, more features, and so on. If scale is an expected outcome of these applications, engineering teams should also expect the tools they use to build them to adopt a similar philosophy. The result is a linear developer experience, one that continues to provide a delightful, predictable experience for developers in lockstep with a growing codebase.

While the application grows quantitatively (more models, controllers, views, etc.), it remains the same qualitatively (the architecture of the application is still expressed as models, controllers, views, etc.). In other words, even though your application gets bigger, your developer experience does not change. Hence, the application's developer experience grows linearly. 

Until you hit the tipping point! Just one more requirement, just one more feature, a small quantitative change that triggers a significant qualitative change, the straw that breaks the camel’s back, the last drop that overflows the barrel. 

…At this point in time, when most software runs in the cloud and on the edge, integrates with multiple and various third-party APIs, and executes processes that run from a few seconds to many days, I should demand libraries, frameworks, and platforms that offer a linear developer experience—one that I will not outgrow as my project scales.

The Linear Developer Experience, Temporal

Funding

Archetype, a provider of usage-based billing software for APIs, raised $3.1m in Seed funding.

Spade, an API for transaction enrichment, raised $5m in Seed funding.

Qwak, a machine learning operations platform, raised $12m in Series A1 funding.

ProsperOps, an autonomous cloud cost optimization platform, raised $72m in funding.

Temporal, an  open source platform that ensures the successful execution of services and applications, raised $75m in Series B funding.

Wiz, a cloud security startup, raised $300m in funding.