Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google Cloud Fundamentals — The Hard Way: A Break-and-Fix Learning Series

Overview Most cloud onboarding tutorials optimize for one outcome: getting a resource into a RUNNING state as fast as possible. That approach teaches syntax, but it doesn't teach the skill that actually matters in production — diagnosing a system when it's not behaving as expected, using only logs, metrics, and a hypothesis-driven process of elimination. This eight-part series takes the opposite…

This eight-part series takes a different approach to cloud onboarding tutorials by focusing on teaching the skill of diagnosing issues in production systems, rather than just getting resources into a running state quickly. Each post in the series demonstrates provisioning a piece of Google Cloud infrastructure using the gcloud CLI, introducing a realistic failure mode, and then walking through the diagnostic process to identify and remediate the issue.

The series assumes familiarity with IaaS/PaaS fundamentals and provides a simple reference architecture that can be broken in controlled ways for practice.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Low Latency and “Fast Enough”

What is low latency? Why is it different from domain to domain? And what is “fast enough”? Everybody wants their application to have low latency. This is obvious. The real question is: how low ?

  • Low latency varies by application and business case
  • Latency-sensitive flows divided into user experience, backend processes, and competing systems
  • Goal is to be "fast enough" for specific business case

What Is a Flaky Test? Why It Costs More Than the Bug It Was Meant to Catch

A flaky test passes and fails on the same code. Nothing changed between the two runs except timing, ordering, or something outside the test that nobody was thinking about.

  • Flaky tests pass and fail unexpectedly on same code.
  • Caused by timing issues, order dependence, shared state.
  • Addressed by fixing underlying issue, not just increasing timeouts.

More from Tuesday 1 September →