vrosas

I can't even get a managed redis instance in Azure EUS2 right now...

Cloud run was added this morning, which is how I was alerted to it. So presuming they're still building it out.

I feel for the wine growers, but as an avid wine consumer I'm looking forward to better deals.

There are a lot of places where channels look like the correct primitive but may actually be overkill. One of my favorite examples is collecting results from a group of goroutines. If you know the number of results up front, you can just define a slice and give each thread an index of the slice to write to (and a waitgroup of course). No channels, no mutexes, and completely thread safe.

Channels are honestly one of the most over-used things in Go. I've been writing Go professionally since 2015 and I honestly rarely use them. Programmers new to Go love to shovel them in everywhere because "why use Go if you're NOT going to use channels?" and I have to say sorry, no - write it serially, then determine if it breaches your SLOs, THEN determine if concurrency fixes it.

Followed quickly by "Redeploying with more log lines", the next logical step.

Yes, but I dangerously allow claude and codex, too...

The CLI version of agy is great. Have you tried it?

I've worked with a lot of "smart" engineers over my career with whom autoscaling is a completely foreign concept, or a half-baked concept at best. My favorite is devs pushing to migrate to k8s because it "scales" and won't hear a single thing otherwise.

Americans would rather die than give up their air conditioned bubbles on wheels. I've wondered why someone hasn't tried manufacturing an enclosed go kart with AC and enough trunk space for a few groceries.

You're going to look very silly taking a call on that.

I was recently looking for a new running watch but couldn't for the life of me figure out what Garmin's higher end watches do to justify being over $1000. Like, ok, better battery life... but besides that?

This thread is just PR people from other watch brands astroturfing.