Out of curiosity: how much did you need to steer Claude while working on this project, and how long did it have?

Asking partly because I see "Co-Authored-By: Claude Opus 4.7 (1M context) ", and partly because I keep hearing "so what do you do with all these agents", and this is a good example of what people do with all these agents.

But when the probability theory class started, everyone found themselves in one of two groups: those who could reliably draw "ξ", or those who instead drew some random snaky thing which probably does not even have a proper Unicode representation. I spent half an hour finally memorizing how the damn thing is actually written to move myself from the latter group to the former.

I would suggest that there is a much, much older technology than pub/sub that can be used for such kind of data transfer: it's UDP, documented in 1980.

I can't stop thinking how overcomplicated our software engineering reality is so we need to reinvent layers and layers of stuff on top of the other stuff. We must make applications for browsers; browsers disallow basic network communication for the code they execute; so sending a chunk of data from a client to a server becomes a real adventure.

Far from that, unfortunately. A lot of Google public APIs predate AIPs and it's practically impossible to fix them and make them compliant. Possibly the worst offender is the Compute Engine API [1], which, to the best of my knowledge, is REST only (no gRPC), uses its own conventions related to page size / next page token, and, in general, is special in many ways. One of the ways it's special is its size: its definition in Google's own Discovery format [2] is a 6MB JSON.

It's an extremely difficult problem to standardize multiple APIs produced by multiple teams, and then keep the new changes compliant. Google did a great job, but it's still very far from the perfect state.

[1]: https://docs.cloud.google.com/compute/docs/reference/rest/v1 [2]: https://www.googleapis.com/discovery/v1/apis/compute/v1/rest - warning: 6 megabytes JSON

[edit: typo]

Which is a very similar approach to any serious code. If you just hired a very clever, enormously knowledgeable intern, and they wrote a bunch of code for you overnight, you would probably review it.

Yes, in some cases, either hobby projects or throwaway code, you could just take it and use it as is, and I surely do, for the code no one cares about. But at work, I would rather review it.

A little bit less than twenty years later, few years after moving to the US, my family and I were driving somewhere near Sonoma, CA, enjoying the views, and someone in the car said something like that this looks like that Windows background. Quick check with Google, and sure enough, we were less than a mile away. We didn't stop, but surely got some photos.

The actual place is a vineyard now.

One of the latest things I made with Claude was a tool that allowed me to move a bunch of very low traffic Cloud Run services to a single VPS without losing any of the Cloud Run benefits such as easy Docker-based deployment and automatic certificate provisioning. I thought about making something like that for quite some time, and Claude finally made it possible, which makes me quite happy.

The fun thing here is that no other soul genuinely cares about it, or any other code I might publish. The code, especially AI generated, is so cheap that if anyone wants to repeat my steps to get rid of Cloud Run services, they will probably vibe-code their own tool instead of figuring out how to use mine, just like I did that instead of spending time on learning Dokku or similar solutions.

So, yes, 10x and more, but no one cares about the result, which makes the whole 10x measurement less useful.

[1]: https://www.techradar.com/vpn/vpn-privacy-security/russias-m...

There is a web version (it's Flutter so it was easy to make one), but parents use the app much more often.

To request unlisted distribution for your app, send it for review as usual, then file a special form [1], and mention that in the review notes.

Source: I struggled with Guideline 4.2 when I tried to publish an app showing the bell schedule and other local information for the neighborhood school. Its audience is, indeed, not of Apple scale: the school parents living nearby. Apple refused it as 4.2 and only agreed to publish it as unlisted, which I was okay with, because sharing the link between the parents was not a big deal. Google had no problems with publishing the Android app normally though.

[1]: https://developer.apple.com/support/unlisted-app-distributio...

So, my personal rule is: if I implemented a feature with Claude, I'll ask it to commit the code and it will add Co-Authored-By. If I made the change manually, I'll commit it myself.