I love the effort to help modernize go code! I feel like it might have been better if they leveraged the Analyzer framework to get this stuff into `go vet` and `go fix`, which would be infinitely easier for LLMs and developers alike to use.
Alternative take: I have not met a serious craftsperson software engineer who did not deeply care about some KPIs. They might not have called them KPIs, but there were numbers they tracked constantly.
In the example of being asked what testing KPIs to tracked, why wouldn’t they include:
- Flake rate
- Test run time, a large component of CI lag
Those will vary vastly depending on where you live. Gas and insurance are high where I live, and even though the environment is harsh on cars (winters with salt), maintenance has never been much.
This is pretty standard for specification documents, probably more accurate to say AI sounds like them than the other way around.
Ignoring the particular technologies used (OAuth/JWT) it looks like they’re adding more auth to the devices themselves; think two computers connected to the same network switch not being able to impersonate each other.
reply