For me it was similar, but I think it was more about a lack of a natural friction. Normally when coding there was the "hit" of seeing something work, but the actually planning/coding/debugging would eventually wear me out, so I'd stop for the day. Now it can all just be endless "hit" of success and nothing that makes me feel tired or annoyed.
The reason I believe this is because I recently went through a really annoying battle with Claude trying to get it to stop being so strict with its sandbox. I wanted it to simply load some sanitized text from a source online, and it just would not do it. The sessions when I was sorting that out were so much easier to stop and moderate than the ones where everything just kept flowing effortlessly.
I remembered enjoying the book, so having not read it in a long time, I tried sharing Surely You're Joking with my kids at bedtime.
That chapter wasn’t the only thing I ended up skipping or heavily editing.
* Picking a room at Los Alamos with a window facing the women’s housing, but being disappointed that a tree or something blocked his view. (Wasn’t he also married at this point?)
* Starting a new Uni faculty position and hanging out at student dances, dismayed that girls would stop chatting & dancing with him when they learned he was a prof and not a fellow student.
* Hanging out at strip clubs to practice his drawing skills.
* Considering a textbook sales rep’s offer to help him find “trouble” in Vegas.
So maybe that one chapter turns around some at the end, but it’s not the only cringe-worthy moment in the book, and I can see why some people may have an overall negative opinion.
If I were going to do this with my kids now that they are teens, I wouldn’t filter as much and use the more questionable events as points of discussion.
I was reading this the other day looking for ideas on how to test query retries in our app. I suppose we could go at it from the network side by introducing latency and such.
However, it’d be great if there also was a proxy or something that could inject pg error codes.
Nice! I worked on something similar as an undergrad project years ago, setting up beams with different orbital angular momentum characteristics. Was a lot fun working in the lab. Sadly I didn’t have the focus/grit to finish writing a paper (sorry Dr. Singh). Side note, this was in 2007 and the folks in our optics lab would check the location of beams by grabbing from the stacks of ancient punchcards lying around and waving them next to the apparatus.
This paper has a pretty similar setup, but adds a spatial light modulator (like a DLP projector that can control phase as well as brightness).
What is wild to me is that the researchers here are able to create a beam where the angular moment changes as you move away.
An approach we've done is to use Postgres' "create database foo2 template foo1" syntax to essentially snapshot the db under test at various points and use those to rollback as needed.
I naturally have a hard time stopping when almost done with something, but with AI everything feels "close" to a big breakthrough.
Just one more turn... Until suddenly it's way later than I thought and hardly have time to interact with my family.