Date: August 7th, 2026 10:38 AM Author: Harsh Lodge Double Fault
I have a part-time job that pays $75+/hour to write LLM prompts for software problems that are too difficult for AI to solve. Most of the job is just waiting for Claude Code to run. The hardest part is coming up with realistic prompts for open-source projects.
LLMs can't manage that complexity perfectly. I'm paid to find those gaps in LLMs' knowledge, specifically stuff that experienced engineers can identify as potential failure points.
You can make AI build complex stuff with plain English, that's very true. But I'm getting paid to make sure AI doesn't overlook something that's typically obscure or not initially obvious so that the next generation of models are even better.
Here's a recent, concrete example: An app built with TypeScript/Next.js has a REST API, and my prompt asked the LLM to implement pagination in some of the API results. One subtlety/complexity of handling pagination in code is that you can get virtually any input for pagination (like page "32s" with "yellow" results per page). LLMs can filter out the invalid inputs, but they struggle with numbers in TypeScript/JavaScript, primarily because JavaScript is a stupid language. What I caught, and what the LLM missed, was that the pagination functionality accepted the JavaScript number "Infinity" as a valid input, which then broke the app. It should have replaced "Infinity" with a limit that doesn't blow up the app, like "Number.MAX_SAFE_INTEGER."
The pay is good because it's specific for coding (not general AI), and I have over 15 years of experience as a codecuck.
It doesn't matter that this happened with an internal app. The whole point is to identify weak spots in LLMs, like this Infinity oversight, so that they don't make these same mistakes in newer models for real-world applications.
99.9% of the time you won't have to deal with pagination issues like this, but it's still very important to identify these shortcomings in LLMs so that this obscure mistake doesn't make it into production code and blow up an app.
No it isn't holy shit this looks more tedious and useless than law. No wonder you're severely mentally ill and gaythreading on here, I'd have actually killed myself if this was my life. Incredible.
I'm doing this temporarily and only part-time (3-5 hours a day) to make some money while I wait to start my new real job. If it sounds tedious, that's because codecucking is tedious. Holy fuck I hate coding. I'm going to be a manager at my next job. I'm not going to pretend I enjoy doing this shit; it's just my way of paying my bills without having to sell any stock in between jobs. Fuck anything coding-related Jfc.
Yes, managing 4-5 coder autists and basically attending lots of meetings. They want a "manager who still codes," but that never works out because managers inevitably get sucked into 15,000 meetings and bullshit administrative work. It's going to suck, but it pays better than being a regular codecuck (holy fuck I hate coding), and I will likely write very little code.
I'm not autistic enough to be a true codecuck. That's my guess about why I got promoted to management several years ago: I'm less autistic than average and can talk like a normal person.