vrosas

I fully agree most big tech companies are pretty bloated. But FWIW a lot of my time at SaaS companies, especially in the B2B space, was spend working on features for larger customers that most others would never use or even see. Like, yeah, product X isn't that complex, but $BigCorp wants to use it in their private cloud, or needs it to be single tenant, or needs these audits done, or want their $Gov client to use it. Now you have a ton of work for zero visible changes.

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.

docs: https://docs.cloud.google.com/billing/docs/how-to/budgets-sp...

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.

> Premature horizontal scaling

I feel like this isn't a thing when it comes to applications. All the decisions you'd make to allow an app to scale sideways are just, like, good design decisions? Even if you never went 1->2 instances. Otherwise every app would just be PostgREST on top of a beefy VM.

Major version upgrades, HA, multi-master, sharding and georeplication are all stories that are not as out-of-the box simple as they should be at this point, IMHO. Then you layer on all the ways devs tend to abuse postgres (stored procedures, pubsub systems, re-indexing hot tables, etc) that will need hours and hours of debate + meetings + committees + design reviews + more meetings to settle. When all along the team probably could have just written the data to something like Firestore and been, like, totally fine?

I've pushed teams to choose Spanner over using Postgres (when already in the GCP ecosystem). It's not really more expensive when you sit down and do the math, you save untold hours of maintenance over the lifespan of the app, and it actually scales without fuss.

People and the news doing a great job scapegoating Google instead of the administration that renamed it in the first place.

Give Cloud Run a try if you haven't. It's basically serverless done right.

I feel like I'm the only person on HN that doesn't have any major (or cliche) problems with GCP, even after using it for a decade at this point. Like it's not perfect and I've hit weird roadblocks along the way but I've dabbled AWS and I currently use Azure at work and those are hilariously bad in their own ways, people just seem to kind of be used to it?

Their excuse is called Azure and if you’ve ever had to deal with it you’d know it’s an amazing(ly awful) excuse to have.

Agreed. At some point to have to stop hugging your ops team and start firing them.

3.6+ have been fine for me. They still introduce bugs but at least they don’t make you wait an hour for them like Claude does.

The problem is, when the context window grows, Claude tends to forget these kinds of rules. It will then do whatever it wants. I had to outright ban comments in the global claude.md, the local claude.md AND write a hook to catch any that still slipped through.

I have been a full-time go developer since 2015 and I have quite literally never written a line of generic go code. I can't even recall seeing any written at any {job} since they've been introduced...

Why would you say something so controversial yet so brave?

I've blown away by flash 3.6's speed while Opus chugs along for _hours_ on similar tasks. I've gotten into a opus designed -> gemini implemented -> opus reviewed dev cycle recently.

> For a major blockbuster, tax incentives equate to tens of millions of dollars, freeing up money for name-brand actors, elaborate set pieces, and unremarkable CGI effects.

Love the dig at the end.