Blog topic
Opinion
-
AgentsCoding Agents Are Only as Good as the Signals You Feed Them
An agent's output is only as good as its feedback loop. Lessons from harness engineering and Stripe's Minions, a hierarchy of feedback signals and why they belong in the platform.
-
The Great AWS Outage: The $11 Billion Argument for Kubernetes
Why the October 2025 AWS outage makes the case for Kubernetes as a cloud-agnostic layer, why multicloud is usually a trap, and why the bigger payoff is isolated test environments for every PR.
-
Why 90% of Microservices Still Ship Like Monoliths
Why most microservice teams still batch changes into monolithic releases through shared staging, what that costs, and how testing each change in isolation lets services ship independently.
-
Why Coordinating Microservice Changes Is Still a Mess
Three common ways teams test changes that span services, why each one hurts, and how a multitenant shared environment with request routing lets in-flight PRs across services be tested together.
-
How to Understand and Improve Your Developer Experience
How to find out what your developers' experience really is, through a holistic view and regular audits, then improve it by protecting flow, building connection and speeding up feedback.
-
Are you Delivering on Developer Experience?
Three ways poor developer experience holds teams back: developers rarely reach flow, collaboration suffers and feedback is low quality. Surveys of developer sentiment make it visible.
-
How to Improve and Measure DevEx in Your Organization
Nine ways to improve developer experience, from standardized environments to incident management and developer autonomy, and how to measure the results with metrics and qualitative assessments.
-
How to Be an Effective Platform Engineering Team
Four challenges platform engineering teams face, from adoption versus completeness to vendor lock-in and proving value with DORA metrics, with lessons from Stitch Fix, Uber and Netflix.
-
7 Reasons Developer Experience is a Strategic Priority
Seven reasons developer experience belongs on the leadership agenda: productivity, innovation, hiring and retention, lower costs, culture, faster response to the market and less risk.
-
How to reduce pain during development on a microservice architecture
The pains of developing on microservices (debugging, local dependencies, slow deploys, costly mocks) and fixes that help, such as Lyft's routing of test requests through shared staging.
-
The struggle for developers to collaborate on microservices
Why features that span several microservices are hard to build and test together, where subsets, Docker Compose and namespaces fall short, and why a service mesh that routes test requests helps.
-
Why the SDLC Workflow is Broken with many Microservices
The five stages a change passes through when a developer owns a few of many microservices, why shared staging turns the last one into a bottleneck, and three steps to fix the workflow.
No matching posts found.
Stay in the loop
Get the latest updates from Signadot