kjgkjhfkjf

Given the sums of money involved, it's hard for me to take these highly publicized heroic resignations at face value.

Perhaps it would be simpler to make all non-essential cookies illegal. I cannot imagine why any reasonable person would want to accept non-essential cookies, other than in the course of following a path of least resistance.

I wish Cloudflare provided a paved path for user auth.

Better Auth seems to be the most common recommendation for Typescript applications, but there currently doesn't seem to be an official integration with Workers either from Better Auth or from Cloudflare.

I currently use Supabase to avoid having to set up my own user auth on Workers, but I would much prefer to use D1 etc.

I like the concept. It's fun. Feedback:

1. The ball seems a bit soft. I suggest you get a real golf ball and putter and see how they behave, if you haven't already.

2. It would be nice if the camera positioned automatically so that it's roughly in the direction the ball should go on the next shot.

3. There were a bunch of flying yellow blobs. I was not sure what they were supposed to be.

The script to create the benchmark numbers appears to be inserting 100 batches, not 10. (The benchmark numbers in the table appear to be consistent with the text, so I guess the actual script used to create them was correct.)

When I left Google in the mid 2010s, there were a couple unusual constraints: 1. They had the majority of their code in a vast++ monorepo. 2. There was a policy that forbade having code from this monorepo on your laptop.

Most companies and projects have orders of magnitude less code, and don't restrict where that code can be stored. It's interesting to learn about Cider and the other things Google built to address their unusual situation, but it's worth keeping in mind that their approach probably isn't ideal in ~most modern dev scenarios.

Markdown is much easier to write quickly than HTML. Situations where I write Markdown quickly include writing messages on Slack and for AI chatbots. I wouldn't want to use HTML in either of those cases.

Seems like it would be simpler to give the agent tools to issue ChromaDB (or SQL) queries directly, rather than giving the LLM unix-like tools that are converted into queries under the hood using a complicated proprietary setup.

It seems like the author feels like a fraud because they successfully made a contribution without learning anything.

The quality of a contribution is not a function of how much you learned or grew while you made it. Learning and growth are part of your compensation for making the contribution. The author is not a fraud for not learning anything. If anything, it seems like they should feel short-changed!

When voluntarily making contributions to open-source projects, everyone should of course feel free not to use AI tools if they want. However, I would argue that using AI tools is a valuable skill itself, and worth practicing.

> if you have a job where you create complexity for others, you will be found out

This explains the panic. It describes most roles in big tech.

The article seems to conflate complexity and scalability, but there's a kernel of truth to its premise. The larger the tech company, the more maddening the processes tend to be. Maybe the next generation of AI-enabled companies will be smaller and less bureaucratic.