- The ONE chart every developer MUST understand by Blaine Osepchuk
- Reverse Interview - a list of questions which may be interesting to a tech job applicant by Stanisław Pitucha
- Why is DevOps Important? by Jérôme Petazzoni
- How Complex Systems Fail - 20 years old document by Richard I. Cook , University of Chicago
- An Engineer’s Guide to a Good Night’s Sleep by Nicky Wrightson
- Never Alone On Call by Deirdre Mahon
- Systems Thinking in Practice by Ryan Frantz
- The Power of “Yes, if”: Iterating on our RFC Process by Tanya Reilly
- DNS and the Art of Making Systems "Just Complex Enough" by Alex Wilson
- Network Architecture Design for Microservices on GCP by Raphael FRAYSSE
- Mistake that cost thousands (Kubernetes, GKE) by Gajus Kuizinas
- Instrumentation Quality Scores: Guiding You to Better Telemetry Data by Valjean Clark
- I test in prod by Charity Majors
- Should You Build An API Gateway In-House? by Michał Trojanowski
- Confirmation Bias: How your brain wants to wreck your code by Matt Eland
- DynamoDB, explained. by Alex DeBrie
- AWS Lambda Cold Start Language Comparisons, 2019 edition by Nathan Malishev
- How to Manage a Manager? by Yegor Bugayenko
- Data Is a Toxic Asset by Bruce Schneier
- Google feedback on TypeScript 3.5 by Evan Martin
- Golang: Programming with errors by Peter Bourgon
- Java: Bean Validation Anti-Patterns by Tom Hombergs
- Roguelike Tutorial - In Rust by Herbert Wolverson
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (0)