They resisted implementing self checkout for years before eventually folding. No digital wallets though, you have to either use plastic or link it to your Amazon account.

The whole dash cart system was a solution in search of a problem IMO. I'm already able to check out about as efficiently as possible. Frontloading the scanning time isn't really an amazing improvement. The store was never crowded enough for it to matter.

My biggest problem with the store was that it was lacking random pantry staples and supplies that you would expect from your primary grocer. Several times I showed up in desperate need of something for a recipe or household task and they just wouldn't have it.

The produce was actually decent quality and competitively priced, but my alternative (the local Ralph's) I think just had some kind of curse or something on it because the produce at that specific location was a consistent level of awful observed over 5 years.

I hope they replace it with a whole foods, much better store IMO.

When I added tab completion for --model that accounts for what --agent is set to, it made it 100x easier to use and I stopped relying on the defaults so much.

It's such a small thing but makes a big difference for discoverability.

The one time I got to work with a QA person, he was worse than useless. He was not technical enough to even use cURL, much less do anything like automated e2e testing, so he'd have to manually test every single thing we wanted to deploy. I had to write up extremely detailed test plans to help him understand exactly what buttons he had to press in the app to test a feature. Sometimes he'd modify the code to try and make testing it easier, break the feature in doing so, and then report that it didn't work. In nearly all cases it would have been faster for me to just test the code myself.

The majority of the time I've worked in orgs where there is no QA team, the devs are expected to own the quality of their output. This works okay when you're in a group of conscientious and talented engineers, but you very quickly find out who really cares about quality and who either doesn't know any better or doesn't care. You will constantly battle management to have enough time to adequately test anything. Every bit of test automation you want to build has to be smuggled in with a new feature or a bugfix.

So really, they both suck, pick your poison. I prefer the latter, but I'm open to experiencing what good looks like in terms of dedicated QA.

  Town            = Central orchestrator / control plane
  Rig             = Project or workspace namespace
  Polecat         = Ephemeral worker job
  Refinery        = Merge queue manager
  Witness         = Worker health monitor
  Crew            = Persistent worker pool
  Beads           = Persistent work items / tasks
  Hooks           = Work queues / task slots
  GUPP            = Work processing guarantee
  Molecules/Wisps = Structured, persistent workflows
  Convoys         = Grouped feature work units