There is definitely some smoke and mirrors to this. I watched a stationary train next to me get about a kilometre away before it started moving in real life.
You are wrong that increasing projects have no cost; many services have project based costs (Cloud Armour rules cannot be used cross project at the base tier), many services (mostly observeability) degrade significantly cross project, the Google Cloud Console _sucks_ cross project.
You are also wrong in saying there are no projects that could reasonably have a safe api key made unsafe by this exploit.
One example, a service that has firebase auth must publish the key (Google's docs recommend). Later, you add gen ai to that service, managing access using IAM/service accounts (the proper way). You've now elevated the Firebase Auth Key to be a Gemini key. Really undeniably poor from Google.
One question, has the GDS stance on Javascript softened, namely progressive enhancement being essentially mandatory [1], since I last worked with you? Is the target for more controlled user groups, non-govuk projects, or do you do SSR to give a usable first HTML response?
On the best practices, as noted by others, there are probably classes in your standard lib/ commons lib that cover this stuff better than storing in integers (e.g. BigDecimal in Java and Python Decimal have precision and rounding mode concepts built in).
Something I've found valuable is on is managing euler units/ratios (e.g. proportions 10^1, percentages 10^-2, basis points 10^-4) . Enforcing a standard that all interchange, data storage has either the same scale, _or is stored with its scale (and not in the name)_ will reduce errors hugely significantly.
Unfortunately cloud domains domains are going to managed by Squarespace.
> Since Google Domains is the underlying domains registrar for Cloud Domains, there are some important changes that we want to share with you.
> What do you need to know?
Upon closing of the Squarespace-Google Domains transaction, Squarespace Domains will become the registrar for your domains managed by Cloud Domains.
I had similar issues with a different VPN/Proxy at an earlier role. I solved with https://github.com/sakai135/wsl-vpnkit and trusting the root certificate of the proxy on the rancher desktop WSL2 vm (Assuming you're on Windows as I was).
Docker desktop pays for itself by solving these issues though IMO (I wasn't able to get a licence at the old role however)
A slightly different beginner lacto ferment is turnip + beetroot "pickle". 9 parts turnips, 1 part beetroot, 2% salt of combined turnip + beetroot + water, all by weight.
Super tasty, not spicy, can be done in 5 days, fermentation kicks off quickly due to sugar content in beets so you get quick feedback.
I don't view that as a loss. JSON by itself is just a string with no context information so either the context is in the programmer's head, in a human-readable document, or in a schema file.
Adding a schema to it seems natural to me (as someone who prefers strong-typing), and the JSONSchema implementation seems pretty lightweight and sensible.
I'd go even further down the mining XML's legacy route and add better XPATH2.0 + XQuery - style support. XQuery was a great tool, so expressive. Though it did spawn XQueryX [1] which I'm still unsure whether it was a joke or not.
> but you definitely have to work within the constraints of the system. If you try to push the boundary too much on what's "expected" it becomes painful very quickly
I've dealt with that pain before with other tools (promoting DataDog montiors + dashboards comes to mind). This area seems like it'll be even more painful so I'll definitely be filtering by that critereon.
> On the last question...
My particular use case would be for some human checkpoint in an otherwise-automated system. I'd hope to pull in all the contextual information, provide the decision-maker with a text box and an approve/reject decison.
> Worst part here is I feel like this is really often something that will come with using the product. Often the use cases documented and sold really seem like all you'll need.
Yeah, that's what worries me about low-code. I know it'll be a bit of a slog to do all these full-code, but it's a known quantity.