I'm surprised (without any particular positive/negative valence) that the article doesn't mention using AI to write the port - especially since both CEL and protovalidate have fairly extensive conformance testing harnesses. The project should be right in the sweet spot for today's tools. The omission is especially striking since most of the article sounds AI-authored to me. (Pangram agrees, for what that's worth.)
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
Building a native C# implementation of CEL engine
11–15 of 15 posts
Re: Building a native C# implementation of CEL engine
#12Earlier quoted context omitted.
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...
Re: Building a native C# implementation of CEL engine
#13Earlier quoted context omitted.
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...
I've always liked them and tried to convince others to use them
AI models seem to like them as well
Re: Building a native C# implementation of CEL engine
#14Earlier quoted context omitted.
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...
Re: Building a native C# implementation of CEL engine
#15Earlier quoted context omitted.
The code is also clearly all vibecoded. I think this is the usual we get these days: "Show HN: I built..." where in fact author did write neither the code nor the writeup.
Is the "chore" commit subject prefix an AI thing? I've started seeing that at work too...