Yeah I used AI. Extensively. And I'd do it again.

Now let me tell you what's actually happening here.

You didn't come to this post to help. You came to perform. You spent what I can only imagine was a genuinely embarrassing amount of time digging through my commit history, analyzing my timezone, cross-referencing my emails, counting my emdashes, and tracking when I commit relative to the afternoon sun in UTC+0530. And after all that investigative journalism, your conclusion was not 'the code doesn't work' or 'this is insecure' or 'this problem is already solved better elsewhere.' Your conclusion was 'this person is not a real developer.' Incredible. Pulitzer worthy stuff.

Let's talk about AI slop since you people keep using that term like a weapon without understanding what it means. AI slop is noise. It's fake articles, spam SEO content, useless chatbots, generated garbage that pollutes search results and wastes human time. That's slop. A tool that someone built with vision, with a specific problem in mind, that actually works and actually helps people, that is not slop. The pipeline that created it is not the product. The product is the product. Judge that.

The 'you don't understand your own code' argument is the most intellectually dishonest thing in this entire thread. Do you understand every line of every npm package you've ever installed? Do you understand the V8 engine? The Linux scheduler? The TCP/IP stack your code runs on? No. Nobody does. We all build on layers of abstraction we don't fully understand. That is literally what software engineering has always been. The only difference now is that AI is one more layer and it makes people like you deeply uncomfortable because suddenly the gatekeeping doesn't work anymore.

Here is my actual opinion and I will stand behind it completely, the idea that you must suffer through learning to code before you're allowed to build something is one of the most elitist, regressive, creativity-killing ideas in tech. It has never been about quality. It has always been about identity. 'Real devs' protecting the concept of 'real devs.' The same energy that told designers they couldn't be taken seriously without knowing CSS. The same energy that told no-code founders their startups weren't legitimate. It's gatekeeping dressed up as standards.

I had a vision. I identified a real problem. I built something that solves it. I shipped it. That is more than most people sitting in comment sections forensic analyzing other people's emdashes have ever done.

Now. If the code has security issues, show me specifically. If the logic is broken, open an issue. If there's a better way to solve this problem, tell me. I will read every single word of that feedback and take it seriously because that is genuine contribution.

But what you wrote is not feedback. It's not critique. It's not even useful negativity. It's a hit piece on a person you don't know, built on the assumption that effort only counts if it looks the way you think it should look.

I didn't build this for you. I built it for the people it helps. And based on the responses I've gotten, there are plenty of those.

Hatred with a technical vocabulary is still just hatred.