curious_curios

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

Improv believe it or not.

Though with gas, maintenance, insurance on top of the car payment, that $700 is probably the floor of car ownership.

Many of the open weight models are trained on outputs from these models (distillation)

I would love for this book to be updated with all the work on adding generative AI to the software engineering workflow at Google.

The Enchiridion is perhaps the most distilled and practical manual of practical stoic philosophy and one I wish I had discovered earlier in life.

While cool sounding, the project is two weeks old and contains lots of made up terms. It’s safe to say it’s a figment of an AI’s imagination.

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.

Reading between the lines I suspect the following:

- We’ve already demonstrated breaking 2048-bit RSA in tightly controlled lab environments

- It’s expected that will be possible at scale by 2029

- The US expects to have around 2 years of supremacy in the space before adversaries catch up

“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”

- Bjarne Stroustrup

Whoever wants to write the underlying engines for virtually every browser: Apple and Google. They both have their agendas that they try to push via them.

If their experience mirrors my own there will be a follow up post, “Why having 50 individuals on your cap table is a pain, I should have gotten them into a syndicate”