Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kentonv
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
23 ms
·
361.
▲
by
kentonv
1y ago
> We also have to take their (Cloudflare’s) word for it that this is actually code of an equal quality to what they’d get by another method. There’s reason to believe it was not, given the beginner nature of the security defects that hav
362.
▲
by
kentonv
1y ago
I have only claimed that for this particular project it worked really well, and was much faster than writing by hand. This particular project was arguably a best-case scenario: a greenfield project implementing a well-known standard again
363.
▲
by
kentonv
1y ago
> It's possible kiitos has (or had?) a higher standard in mind for what should constitute a senior/"lead engineer" at Cloudflare and how much they should be constrained by typing as part of implementation. See again h
364.
▲
by
kentonv
1y ago
> The code that any current-gen LLM generates, no matter how precise the prompt it's given, is never even close to the quality standards expected of any senior-level engineer, in any organization I've been a part of, at any poi
365.
▲
by
kentonv
1y ago
I have actually had that thought, too. I feel bad being rude to an LLM even though it doesn't care, so I add words like "please" and sometimes even complement it on good work even though I know this is useless. Will I learn
366.
▲
by
kentonv
1y ago
> We disable the CORS headers specifically for the OAuth API Oops, I meant we set the CORS headers, to disable CORS rules. (Probably obvious in context but...)
367.
▲
by
kentonv
1y ago
Yes, it's part of our MCP framework: https://blog.cloudflare.com/remote-model-context-protocol-se...
368.
▲
by
kentonv
1y ago
I can think of books I used to learn software engineering when I was younger which, in retrospect, I realize were not very good, and taught me some practices I now disagree with. Nevertheless, the book did help me learn, and got me to a poi
369.
▲
by
kentonv
1y ago
I did actually use the LLM to write tests, and was pleased to see the results, which I thought were pretty good and thorough, though clearly the author of this blog post has a different opinion. But TDD is not the way I think. I've nev
370.
▲
by
kentonv
1y ago
I included the prompts because I personally found it extremely illuminating to see what the LLM was able to produce based on those prompts, and I figured other people would be interested to. Seems I was right. But to be clear, I had no idea
371.
▲
by
kentonv
1y ago
I agree that most code reviewers are pretty bad at spotting subtle bugs in code that looks good superficially. I have a lot of experience reviewing code -- more than I ever really wanted. It has... turned me cynical and bitter, to the point
372.
▲
by
kentonv
1y ago
I put in the implicit grant because someone requested it. I had it flagged off by default because it's deprecated.
373.
▲
by
kentonv
1y ago
Free reviews by domain experts are great. I didn't think of that, though. I didn't have an agenda here, I just put the note in the readme about it being LLM-generated only because I thought it was interesting.
374.
▲
by
kentonv
1y ago
Hi, I'm the author of the library. (Or at least, the author of the prompts that generated it.) > I’m also an expert in OAuth I'll admin I think Neil is significantly more of an expert than me, so I'm delighted he took a pa
375.
▲
by
kentonv
1y ago
Did you actually read the commit history? My prompts specify very precisely what should be implemented. I specified the public API and high-level design upfront. I let the AI come up with its own storage schema initially but then I prompted
376.
▲
by
kentonv
1y ago
I don't agree. The AI largely does the boring and obvious parts. I'm still deciding what gets built and how it is designed, which is the interesting part.
377.
▲
by
kentonv
1y ago
What do you mean by "one degree removed from 100% pure vibe coding", then? The definition of vibe coding is letting the AI code without review...
378.
▲
by
kentonv
1y ago
I'm fairly confident that it's not just plagiarizing because I asked the LLM to implement a novel interface with unusual semantics. I then prompted for many specific fine-grain changes to implement features the way I wanted. It se
379.
▲
by
kentonv
1y ago
That's exactly what I thought, too, before I tried it! Turns out it feels very different than I expected. I really recommend trying it rather than assuming. There's no learning curve, you just install Claude Code and run it in you
380.
▲
by
kentonv
1y ago
I spent about 5 days semi-focused on this codebase (though I always have lots of people interrupting me all the time). It's about 5000 lines (if you count comments, tests, and documentation, which you should). Where do you get 7 lines
381.
▲
by
kentonv
1y ago
I do feel that the agentic thing is what made all the difference to me. The stuff I tried before that seemed pretty lame. Sorry, I know you were trying to avoid that exact comment, but it is true in my case. To be clear, I am not saying tha
382.
▲
by
kentonv
1y ago
Yes, the ethical debate is fair and worth having, and I don't think someone necessarily has to try it to be able to debate the ethics. I obviously don't quite agree with his opinions here but I respect them. (Though I would say, b
383.
▲
by
kentonv
1y ago
The author goes into great detail about how he looked at my commit log[0] where I used AI, and he found it "nauseating" and concluded he'd never want to work that way. I'm certainly not going to tell anyone that they
384.
▲
by
kentonv
1y ago
I think you're rationalizing your resistance to change. I've been there! I have no reason to care whether you use AI or not. I'm giving you this advice just for your sake: Consider whether you are taking a big career risk by
385.
▲
by
kentonv
1y ago
Luckily, shareholders do not decide who to hire and fire. The actual officers of the company, hopefully, understand why senior engineers are non-fungible. Tech companies, at least, seem to understand this well. (I do think a lot of non-tech
386.
▲
by
kentonv
1y ago
Fine, sorry, apparently both of meander_water's dates were incorrect, and I actually started the work two days before March. It was still less than a month from there to release, though.
387.
▲
by
kentonv
1y ago
> 1. Its output is unreliable at best > 2. That output often looks correct to an untrained eye and requires expert intervention to catch serious mistakes The thing is this is true of humans too. I review a lot of human code. I could
388.
▲
by
kentonv
1y ago
It's not a 100% bad idea. If you lose the encryption key, you lose the data. Data loss is bad! So better keep a backup of the key somewhere. I can see how it got there. Defeats the purpose in this case though.
389.
▲
by
kentonv
1y ago
Claude Code actually has a flat-rate subscription option now, if you prefer that. Personally I've found the API cost to be pretty negligible, but maybe I'm out of touch. (I mean, it's one AI-generated commit, Michael. What co
390.
▲
by
kentonv
1y ago
Dude. Claude Code has zero learning curve. You just open the terminal app in your code directory and you tell it what you want, in English. In the time you have spent writing these comments about how you don't care to try it now becaus
More ›