Member-only story
I used AI to write 100% of my code for a month. My pull request got rejected.
Cursor, Copilot, zero manual typing and the code review that made me want to delete my GitHub account.
<devtips/>11 min read·6 days ago--
You ever submit a pull request feeling like an absolute genius, only to watch it get dissected like a first-year biology frog?
Yeah. That was me. February. Twelve commits deep into what I genuinely thought was my best work in years. My reviewer a senior engineer who communicates exclusively in terse Slack messages and code comments that feel like parking tickets came back with fourteen inline comments. Fourteen. On code I didn’t fully write. On code I couldn’t fully explain.
“What does this function actually do? Walk me through it.”
I stared at that comment for a solid three minutes. I had accepted the suggestion. I had seen it pass the linter. I had shipped it. But walk you through it? That was going to be a problem.
Here’s the context: for the entire month of January, I ran an experiment. Every line of code I wrote or rather, every line of code that went into my repos came from an AI tool. Cursor for the heavy lifting. Copilot for the inline fills. I wrote prompts. I reviewed suggestions. I pressed Tab…
