Designing for Concurrency: the Hilbert’s Hotel Problem in Go
A concurrent solution may turn out to be more elegant and easier to reason about than an equivalent sequential algorithm.
Designing & Managing for ResilienceInfoq
Grab Redesigns Counter Service Storage for 50% Lower P99 LatencyInfoq
The Async Multiprocessing Has Sound Foundations in Linux, But Further Testing is NeededInfoq
AI Agents with Cloud Credentials Are Outrunning Billing Guardrails Built for Human-Speed MistakesInfoq
How to Develop Software Engineering Skills in the Age of AIInfoq
CodeGuardian: a Model Context Protocol Server for AI-Assisted Code Quality Analysis and SecurityInfoq
Oso Unbundles Security AuthorizationThenewstack
Go on App Engine: tools, tests, and concurrency - The Go Programming LanguageGo
Go Concurrency Patterns: Context - The Go Programming LanguageGo
Go Concurrency Patterns: Pipelines and cancellation - The Go Programming LanguageGo
Some Things You Oughta Know When Working with Viewport UnitsCss Tricks
MotherDuck Builder Office Hours - July 21Motherduck
100x Defect Tolerance: How Cerebras Solved the Yield Problem - CerebrasCerebras
Troubleshooting .NET automatic instrumentation issuesOpentelemetry
What is Root Cause Analysis?Datadoghq
Introducing Origin Shield Concurrency Limits and QueueingBunny
The Problem with Transatlantic Data TransfersThenewstack
Beyond API Security Testing: Runtime ProtectionThenewstack
Designing a User Interface to Represent Complex Tree DataRetool
GPU autoscaling on Kubernetes with KEDA: Building an external scalerCncf
