Live data from Hacker News

Cloudlflare builds OAuth with Claude and publishes all the prompts

github.com

41–50 of 552 posts

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

#41
post #10

This is exactly the direction I expect AI-assisted coding to go in. Not software engineers being kicked out and some business person pressing a few buttons to have a fully functional app (as is playing out in a lot of fantasies on LinkedIn & X), but rather experienced engineers using AI to generate bits of code and then meticulously reviewing and testing them. The million dollar (perhaps literally) question is – coul…

> but rather experienced engineers using AI to generate bits of code and then meticulously testing and reviewing them.

My problem is that (in my experience anyways) this is slower than me just writing the code myself. That's why AI is not a useful tool right now. They only get it right sometimes so it winds up being easier to just do it yourself in the first place. As the saying goes: bad help is worse than no help at all, and AI is bad help right now.

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

#42
post #24
post #17

Earlier quoted context omitted.

He is quoting from the project readme. I wrote all this text.

Thanks for weighing in here If I might make a suggestion, based on how fast things change, even within a model family, you may benefit from saying Claude what . I was especially cognizant of this given the recent v4 release which (of course) hailed as the second coming. Regardless, you may want to update your readme to say It may also be wildly out of scope for including in a project's readme, but knowing which of th…

I believe it's important to say when AI was used so heavily in building a library -- it would feel dishonest to me to claim I wrote it all myself. I also think it's just a pretty interesting thing to know about. So I think it belongs in the readme. (But I'm not making a moral judgment on what anyone else does.)

It was almost entirely Claude Sonnet 3.7. I agree I should add the version to the readme.

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

#43
post #10

This is exactly the direction I expect AI-assisted coding to go in. Not software engineers being kicked out and some business person pressing a few buttons to have a fully functional app (as is playing out in a lot of fantasies on LinkedIn & X), but rather experienced engineers using AI to generate bits of code and then meticulously reviewing and testing them. The million dollar (perhaps literally) question is – coul…

The million-dollar question is not whether you can review at the speed the model is coding. It is whether you can trust review alone to catch everything.

If a robot assembles cars at lightning speed... but occasionally misaligns a bolt, and your only safeguard is a visual inspection afterward, some defects will roll off the assembly line. Human coders prevent many bugs by thinking during assembly.

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

#44
post #28
post #24

Earlier quoted context omitted.

Thanks for weighing in here If I might make a suggestion, based on how fast things change, even within a model family, you may benefit from saying Claude what . I was especially cognizant of this given the recent v4 release which (of course) hailed as the second coming. Regardless, you may want to update your readme to say It may also be wildly out of scope for including in a project's readme, but knowing which of th…

> It may also be wildly out of scope for including in a project's readme The entire point of the repository seems to be to invalidate/validate the thesis if LLMs are good enough to be pair programmers right now. Removing it from the README makes no sense in that context.

This library is a core component of our MCP framework, it's not just an experiment.

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

#45
post #10

This is exactly the direction I expect AI-assisted coding to go in. Not software engineers being kicked out and some business person pressing a few buttons to have a fully functional app (as is playing out in a lot of fantasies on LinkedIn & X), but rather experienced engineers using AI to generate bits of code and then meticulously reviewing and testing them. The million dollar (perhaps literally) question is – coul…

> Not software engineers being kicked out ... but rather experienced engineers using AI to generate bits of code and then meticulously reviewing and testing them.

But what if you only need 2 kentonv's instead of 20 at the end? Do you assume we'll find enough new tasks that will occupy the other 18? I think that's the question.

And the author is implementing a fairly technical project in this case. How about routine LoB app development?

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

#46

From this commit: https://github.com/cloudflare/workers-oauth-provider/commit/... === "Fix Claude's bug manually. Claude had a bug in the previous commit. I prompted it multiple times to fix the bug but it kept doing the wrong thing. So this change is manually written by a human. I also extended the README to discuss the OAuth 2.1 spec problem." === This is super relatable to my experience trying to use these AI tool…

This to me is why I think these tools don't have actual understanding, and are instead producing emergent output from pooling an incomprehensibly large set of pattern-recognized data.

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

#48
post #27

Congrats and thanks for sharing, both the code and the story. Which Claude plan did you use? Was it enough or did you feel limited by the quotas?

This was mostly Claude Code, which runs on API credits. I think I spent a two-digit number of dollars. The model was Sonnet 3.7 (this was all a couple months ago, before Claude 4).

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

#49
I’ve tried building a web app with LLMs before. Two of them went in circles—I'd ask them to fix an infinite loop, they’d remove the code for a feature; I’d ask them to add the feature back, they’d bring back the infinite loop, and so on. The third one kept losing context—after just 2–3 messages, it would rebuild the whole thing differently.

They’ll probably get better, but for now I can safely say I’ve spent more time building and tweaking prompts than getting helpful results.

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

#50

[flagged]

Just put a form on a website and you will see why... CloudFlare provides the solution, not causing the problem.

> CloudFlare provides the solution, not causing the problem

Isn't CloudFlare infamously known for refusing to take action against clients who are causing the problems (e.g. DDoS services that make use of CloudFlare's services)?

Post reply on HN