I think people are afraid to read the documentation for postgres. You can start it up in milliseconds. Fast enough and light enough to run one copy for every test case in your test suite, or whatever you're using it for. (mkdir /tmp/whatever; initdb -D /tmp/whatever --no-instructions -A reject -c listen_addresses= --auth-local=trust --no-sync -c fsync=off -c unix_socket_directories=/tmp/whatever -U postgres --no-locale; postgres -D /tmp/whatever) Now you have a test database that behaves exactly like production because it's exactly like production. (OK, turning fsync off makes it a lot faster than production, so be careful.)

I don't feel safe with any one single point of failure. "Your credit card bounced", "you thought it was dev", "you got hacked", etc. are all the same problem to me and no cloud provider solves those merely by setting up an account.

(And yes, my workstation has a clear case and LED RAM. Yes, I'm an idiot. Whenever Windows applies an update late at night, I wake up if it turns back on. I don't know what I was thinking when I built that thing, but never again.)

So, I approach it in good faith, but I do get upset when people say "I'll ask claude". You need to be the intermediary, I can also prompt claude and read back the result. If you are going to hire an employee to do work on your behalf, you are responsible for their performance at the end of the day. And that's what an AI assistant is. The buck stops with you. But I don't think people understand that and that they don't understand they aren't adding value. At some point, you have to use your brain to decide if the AI is making sense, that's not really my job as the code/doc reviewer. I want to have a conversation with you, not your tooling, basically.

So if AI scribes mean "less double booking" then that's kind of a win/win. Less patient time is wasted. Doctors can make more money by seeing more people on a given day. Seems fair.

I do use the browser version on occasion. I have no strong feelings one way or the other there. I like it better than Google search in many cases, but probably just search more often.

Sometimes Claude can be a little weird. I was asking it about some settings in Grafana. It gave me an answer that didn't work. I told it that. "Yeah, I didn't really check, I just guessed." Then I said, "please check" and it said "you should read the discussion forums and issue tracker". I said "YOU should read the discussion forms and issue tracker". It consumed 35k tokens and then told me the thing I wanted was a checkbox. It was! I am not sure this saved me time, Claude. I am not experienced enough to say that this is a deal breaker. While this is burned into my mind as an amusing anecdote, it doesn't ruin the service for me.

My coworkers have noticed a degradation and feel vindicated by some of the posts here that I link. A lot of them are using Cursor more now. I have not tried it yet because I kind of like the Claude flow and /effort max + "are you sure?" yield good results. For now. I'm always happy to switch if something is clearly better.

https://tinygo.org/docs/reference/lang-support/

And parts of the stdlib that don't work:

https://tinygo.org/docs/reference/lang-support/stdlib/

The Space Shuttle sure blew up a lot for something with that much process applied.

The establishment likes to pat the establishment on the back but ordinary people seem to know what's up. In my minimal experience, anyway.

(One thing to keep in mind... grand juries really are a cross-section of the population, whereas lawyers get to select jurors after talking to them, so there is some selection bias on ordinary juries that grand juries don't have.)

It isn't the most powerful computer in the world but I never ran into any problems... so it's probably an OK compromise for most people, especially in the world where RAM is scarce because of AI datacenter buildouts.