Live data from Hacker News

Cloudlflare builds OAuth with Claude and publishes all the prompts

github.com

471–480 of 552 posts

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#471

Earlier quoted context omitted.

> Still saves a lot of time vs typing everything from scratch Probably very language specific. I use a lot of Ruby, typing things takes no time it's so terse. Instead I get to spend 95% of my time pondering my problems (or prompting the LLM)...

It can create a whole dashboard view in elixir in a few seconds that is 100 lines long. No way I can type that in the same time.

In my experience the problem is never creating the dashboard view (there's a million examples of it out there anyway to copy/paste), but making sense of the data. Especially if you're doing anything even remotely novel.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#472
post #388

Earlier quoted context omitted.

That's "just" more statistics though.

Are you good in math definitions or is this an opinion? For me a compressed model learning rules through statistics is not statistics anymore. Physic rules are not statistics.

Of course they are. Force has a strong correlation with mass times acceleration. Objects at rest have a high chance of being observed to remain at rest. And so on.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#473

Earlier quoted context omitted.

Depends on what you're doing. For example when you're writing something like React components and using something like Tailwind for styling, I find the speedup is close to 10X.

Isn’t this because the LLMs had like a million+ react tutorials/articles/books/repos to train on? I mean I try to use them for svelte or vue and it still recommends react snippets sometimes.

I put these in the Gemini Pro 2.5 system prompt and it's golden for Svelte.

https://svelte.dev/docs/llms

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#474

Earlier quoted context omitted.

> Still saves a lot of time vs typing everything from scratch Probably very language specific. I use a lot of Ruby, typing things takes no time it's so terse. Instead I get to spend 95% of my time pondering my problems (or prompting the LLM)...

It can create a whole dashboard view in elixir in a few seconds that is 100 lines long. No way I can type that in the same time.

If you're making a dashboard view your productivity is zero, making it faster just multiplies zero by a bigger number.

Edit: this comment was more a result of me being in a terrible mood than a true claim. Sorry.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#477

Earlier quoted context omitted.

Isn’t this because the LLMs had like a million+ react tutorials/articles/books/repos to train on? I mean I try to use them for svelte or vue and it still recommends react snippets sometimes.

I put these in the Gemini Pro 2.5 system prompt and it's golden for Svelte. https://svelte.dev/docs/llms

I do this and it still spits out react snippets regardless like 40% of the time... I feel like unless you are doing something extremely basic this is fine but once you introduce state or animations all these systems death spiral.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#478
post #445

Earlier quoted context omitted.

Completely agree with you. I was working on the front-end of an application and I prompted Claude the following: "The endpoint /foo/bar is returning the json below ##json goes here##, show this as cards inside the component FooBaz following the existing design system". In less than 5 minutes Claude created code that: - encapsulated the api call - modeled the api response using Typescript - created a re-usable and res…

The thing is... does your code end there? Would you put that code in production without a deep analysis of what Claude did?

(GP) I wouldn't, but it would get me close enough that I can do the work that's more intellectually stimulating. Sometimes you need the people to do the concrete for a driveway, and sometimes you need to be signing off on the way the concrete was done, perhaps making some tweaks during the early stages.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#479

Earlier quoted context omitted.

> No it doesn't. Typing speed is never the bottleneck for an expert How could that possibly be true!? Seems like it'd be the same as suggesting being constrained to analog writing utensils wouldn't bottleneck the process of publishing a book or research paper. At the very least such a statement implies that people with ADHD can't be experts.

> How could that possibly be true!? (I'll assume you're not joking, because your post is ridiculous enough to look like sarcasm.) The answer is because programmers read code 10 times more (and think about code 100 times more) than they write it.

I wasn't joking, it's a bottleneck sometimes, that's it. It's a bottleneck like comfort and any good tool is a bottleneck, like a slow computer is a bottleneck. It's silly to suggest that your ability to rapidly use a fundamental tool is never a bottleneck, no matter what other bits need to come into play during the course of your day.

My ability to review and understand intent behind code isn't a primarily bottleneck to me actually efficiently reviewing code when it's requested of me, the primary bottleneck is being notified at the right time that I have a waiting request to review code.

If compilers were never a bottleneck, why would we ever try to make them faster? If build tools were never a bottleneck, why would we ever optimize those? These are all just some of the things that can stand between the identification of a problem and producing a solution for it.

Re: Cloudlflare builds OAuth with Claude and publishes all the prompts

#480

Earlier quoted context omitted.

I just wanted to say thanks so much publishing this, and especially your comments here - I found them really helpful and insightful. I think it's interesting (though not unexpected) that many of the other commenters' comments here show what a Rorschach test this is. I think that's kind of unfortunate, because your experience clearly showed some of the benefits and limitations/pitfalls of coding like this in an object…

I find reviewing AI code less mentally tiring that reviewing human code. This was a surprise to me! Until I tried it, I dreaded the idea. I think it is because of the shorter feedback loop. I look at what the AI writes as it is writing it, and can ask for changes which it applies immediately. Reviewing human code typically has hours or days of round-trip time. Also with the AI code I can just take over if it's not do…

Thank you so much for your detailed, honest, and insightful response! I've done a bunch of AI-assisted coding to varying degrees of success, but your comment here helped me think about it in new ways so that I can take the most advantage of it.

Again, I think your posting of this is probably the best actual, real world evidence that shows both the pros and cons of AI-assisted coding, dispassionately. Awesome work!

Post reply on HN