Operationalizing Chaos Engineering with GitOps
By executing chaos tests, changes can be verified. This calls for chaos experiments to be tied with standard GitOps flows.
FireHydrant: Managing Incidents Without the ChaosThenewstack
How Argo CD and OpenShift Enable GitOps for DevelopersThenewstack
Push vs. Pull in GitOps: Is There Really a Difference?Thenewstack
Kong Applies Machine Learning to Microservice ManagementThenewstack
Refactoring Is Not Bad, Until It IsThenewstack
Accessibility as an Essential Part of the Inclusive Developer ExperienceThenewstack
Pancakes Are Delicious and Data Centers Are for Free StuffThenewstack
Lessons Swift Designer Chris Lattner Has Learned about LeadershipThenewstack
Transform and Future-Proof Your Architecture with MACHThenewstack
Selecting the Right Database for Your MicroservicesThenewstack
Cloud Systems: Deploying to Amazon ECSPulumi
Platform Engineering & DevOps Series Kickoff AnnouncementPulumi
Introducing New Slimmer Docker ImagesPulumi
How to serve trillions of tokens for trillion-parameter coding agentsModal
Practical Uses for AI in Your Data WorkflowsMotherduck
Data Council 2025Motherduck
Ship It: Dinner & Drinks on a BoatMotherduck
Spatial Data Management with DuckDB ft. MattForrestMotherduck
MotherDuck Builder Office Hours - July 21Motherduck
Duck Duck Stream: How to Efficiently Load Data into DuckLake with EstuaryMotherduck
