marwatk

I've been experimenting with omp because:

- it allows different models within one session via roles (I only have API, so pay per token)

- it's much more likely (ime) to use the LSP over grep for determining how code fits together

But I agree a 20k+ starting context is way overkill.

I find it's very hard to get information on harnesses people are using. I have to stay model agnostic so I avoid claude, codex, cursor, etc. I've used and tried opencode, which worked well, but obviously lacks the above features.

Does anyone have a resource for following what people are actually being productive with? With so much vibe going on it's hard to separate the wheat from the chaff.

Such frequent interventions means you need very reliable cell service. In times of heavy congestion (concerts, etc) that doesn't seem feasible.

Hardware tokens (Yubikeys, etc) are signed by their vendor. They support attestation which allows q site to disallow vendors not in a white list. Some banks (Vanguard was/is one) actually enforce this preventing all but a handful of hardware keys from working with their 2FA.

> Regardless, the fact that companies raise their prices in response to shortages is not only defensible but desirable.

Gouging is good. I'm sure they'll be lowered again when supply stabilizes. Any time now.

RedHat spends a lot of time back-porting security updates to older software (e.g. RHEL7). Stream is always only the latest RHEL version, I believe.

The whole point of RHEL is the long term support (the back-porting), which is what they're going to stop publishing.

Even if we fixed all of the above, changing jobs would still require uprooting your family. In an era where you worked for one company for life it made sense. Today I don't think it's feasible.

Yep, this is why LIDAR is so helpful. It takes the guess out of "is the surface in front of me flat?" in a way vision can't without AGI. Is that a painting of a box on the ground or an actual box?

I've read the assertions section a few times and I still don't understand the argument. How is:

  if got == nil {
    t.Errorf("blog post was nil, want not-nil")
  }

Better than

  assert.NotNil(t, got, "blog post")

? They seem to suggest that you lose context, but their "Good" examples are similarly devoid of context.

The bigger issue is that returning the error without wrapping provides zero context and after a crash you're stuck trying to figure out which of a hundred calls to Write was responsible for "write error" or some other equally ambiguous message that's nearly impossible to track down.

So you have to resort to a poor man's stack trace: if err != nil { return fmt.Errorf("my thing: %w", err) }

(We use wrapcheck via golangci-lint to enforce it because not having context for an error has bitten us so many times)

In things like rest APIs you need them quite a bit to distinguish between a value being the zero value and not present at all. Most libraries I've seen have an IntPointer or similar function exposed globally.

This prevents me (a Tello user) from getting the new phone. There are only like 3 US MVNOs that support eSIM. I wonder how long that will remain the case now that the writing is on the wall. I tried Google Fi eSIM a while back prior to traveling and even after working on the phone with Google support they had to ship me a physical SIM to bootstrap the eSIM.

This is addressed in the article:

> A critical limitation in the IRS’s ability to audit millionaires is the availability of IRS revenue agents. Only this class of auditors, given sufficient training and experience, are qualified to examine complex tax returns – the types of returns typically filed by high-income individuals and large-scale businesses.

> With severe budget constraints, IRS has tended to trade off the replacement of revenue agents with hiring more tax examiners. These certainly are paid less, but they are also less knowledgeable. While revenue agents used to outnumber tax examiners, this has slowly shifted over time.