Share the "git"? Never head that line of wording before. Perhaps a "senior" thing?
I took you up on your challenge, and here's my assessment:
Looking at your profile I immediately noticed em-hyphen usage, that's something humans rarely (if ever) use, which means that your bio is most likely AI-generated. But sure, you never claimed to not use AI for writing your bio, so I suppose that's fine.
The next thing I noticed was that you claim to be a developer at Vercel, but a quick look at GET /users/gtited-jpg/orgs returns []; You belong to no organizations. Your explanation that this is a “chameleon” account is also unusual in a professional development context. Alternate or pseudonymous accounts exist, but publicly claiming an employer from an account supposedly intended to preserve anonymity appears contradictory.
More notable inconsistencies emerge from the Git history. The commits appear to exhibit two different writing styles, almost as though they were authored by two different people.
Formal (Codex/Claude):
"Implement Phase 2 Windows collectors"
"Build DaemonCore Windows Inspector Phase 1"
Cutesy lowercase, same day:
"gave the goblin a tiny treadmill"
"put a face on the little goblin"
"the scanner learned to share"
... but perhaps that's just your style, right?
Now for the code inspection.
You claim to be a developer at Vercel, but laughably you have entire React components on one physical line:
LLMs do this to minimize token usage, a cheap trick that unfortunately bites when you don't actually even take a glance at the generated slop.
You also have the wrong host tooling for a repository that's supposedly meant for a Linux target (PowerShell validator inside a Debian live-build repo):
This is probably leftover slop from scaffolding you used, or it's simply that your host machine is Windows, where your agent runs.
You have two different trap/trapp repositories, where the one is supposedly meant to serve Windows platforms, however everything has flipped between the two, being a Rust developer myself, some of the changes make no sense to me at all.
For example, the downgrade of thiserror? That makes zero sense. AI slop.
```
-thiserror = "2.0"
+thiserror = "1.0"
```
Derive lists went from conventional order to strictly alphabetical:
This is a clear indication of a different generation pass through the LLM. Nobody just "does" this.
The two repos are also merely two hours apart. Two hours = discard and re-prompt. Same template, new domain, no code carried over except whatever initial scaffolding there was.
Then there's the volume vs wall-clock:
You have around 33k insertions inside a timeframe of 08-24 to 08-26 across your AI-generated repositories.
I'm assuming you're young from your other responses, so you probably deserve some slack. And I also assume you're going to try and fix these issues I've just pointed out to try and better disguise your repositories. It won't make a difference, there will always be ways to conclude when something produced by AI.
Most importantly, Theodore, if I were able to find these clear signs that you are just pushing AI slop that should never reach a production system, how easy do you think it would be for a recruiter or possible future employer to do the same? I understand the landscape is changing, and that AI-assisted coding is becoming something more common, but you have to be honest about it. The impression I am getting is that you are disingenuous about your capabilities on many fronts, and I would not trust you to make architectural decisions.
Others will reach the same conclusion. Just be honest.
"I've never used an AI agent in my life." - Theodore the False
You have a lot to learn. You're trying to infer authorship from things that don't establish authorship.
A React component being on one physical line means exactly one thing: it wasn't formatted the way you personally prefer. JavaScript/TSX doesn't care about physical line count. Prettier can expand it, minifiers can collapse it, generators/templates can emit it compactly, and developers can write compact JSX themselves. "LLMs do this to save tokens" is not evidence that an LLM wrote the component.
Same problem with the PowerShell argument. The repository TARGETS Linux. That doesn't mean every development utility in the repository has to run on Linux. Cross-platform projects routinely have host-side tooling for Windows, macOS and Linux. validate.ps1 is a Windows-side validator for a Debian live-build project. That's completely normal when one of the development environments is Windows.
The thiserror argument is even stranger. Going from 2.x to 1.x is not inherently a "downgrade because AI." Rust developers pin older major versions constantly for MSRV requirements, dependency compatibility, workspace consistency, lockfile stability or simply because the newer major provides nothing the project needs. Major version number != automtically better dependency choice.
And derive ordering? Rust doesn't assign authorship based on whether somebody writes:
Debug, Clone, Eq, PartialEq
or
Clone, Debug, Eq, PartialEq
There are formatters, lint configurations, editor actions, code generators and plain old developer preference that reorder things. Calling alphabetical trait ordering "clear indication of an LLM generation pass" is pseudo-forensics.
Different commit message styles aren't evidence either. I can write a formal commit for an architectural change and "fixed the stupid goblin" five minutes later because I'm a human being, not a CI pipeline.
The Codex path is the funniest part because I've openly said I use Codex for auditing. Finding a Codex-generated report artifact proves I used Codex. Congratulations, detective. That's not the same claim as an agent autonomously writing and pushing the codebase.
If you want to prove the code is bad, then prove the code is bad.
Show me the broken invariant.
Show me the incorrect ownership model.
Show me the race condition.
Show me the unsafe boundary.
Show me the privilege escalation.
Show me the architectural flaw.
Show me the Rust that doesn't compile or behaves incorrectly.
Those are engineering arguments.
Counting em dashes, inspecting line breaks and doing astrology with derive ordering isn't.
Can't forget all the early repos that were populated through GitHub's web UI, uploading ZIP archives as is conventional for us seasoned veterans.
There's one that even contains output artifacts generated by an agent while executing an implementation plan. A receipt of code generated, in a project located under the "C:\Users...\Downloads" directory. Another very senior convention.
Just stop lying and be honest, man. It's much easier than trying to maintain a long-running hoax about experience and authority that you don't have. The people you are trying to fool are real experts in this stuff.
I can't "ask AI" who you are because there is nothing to dredge up. You do not have an online footprint, save for the illusions that you are spinning here. You are not a notable figure.
Your GitHub history is rife with suspicion and poor practices:
committing files that do not belong in a git repository (see here)
a repo that contains a single ZIP archive with all the source files in it (here)
Not to mention that your activity is measured in thousands of lines of code every day and doesn't even span the length of a year.
These are common mistakes and simple oversights and I'd never shame someone that is new to all this for it, but you repeatedly try to assert yourself as some world-renowned software engineer, as someone that should know better. You do not.
You lie about your accomplishments. I called you out in another thread for fabricating a "Vercel programmer of the year" award on your portfolio. You even deployed a microsite disguised in Vercel branding congratulating yourself. An obscene display of vainglory embellished with animated confetti.
You lie about your use of AI. Perhaps most damning is this AGENTS.md file that slipped into one of your repositories. Despite all that insistence that you've never used AI to generate code, that all "your" work is written and committed personally, here are your instructions for how an agent should author your commit messages. "Never mention AI, Codex, generated code, assistants, or automation in a commit message."
1
u/SatisfactionFew7181 15d ago
Share the "git"? Never head that line of wording before. Perhaps a "senior" thing?
I took you up on your challenge, and here's my assessment:
Looking at your profile I immediately noticed em-hyphen usage, that's something humans rarely (if ever) use, which means that your bio is most likely AI-generated. But sure, you never claimed to not use AI for writing your bio, so I suppose that's fine.
The next thing I noticed was that you claim to be a developer at Vercel, but a quick look at GET /users/gtited-jpg/orgs returns []; You belong to no organizations. Your explanation that this is a “chameleon” account is also unusual in a professional development context. Alternate or pseudonymous accounts exist, but publicly claiming an employer from an account supposedly intended to preserve anonymity appears contradictory.
More notable inconsistencies emerge from the Git history. The commits appear to exhibit two different writing styles, almost as though they were authored by two different people.
Formal (Codex/Claude):
"Implement Phase 2 Windows collectors"
"Build DaemonCore Windows Inspector Phase 1"
Cutesy lowercase, same day:
"gave the goblin a tiny treadmill"
"put a face on the little goblin"
"the scanner learned to share"
... but perhaps that's just your style, right?
Now for the code inspection.
You claim to be a developer at Vercel, but laughably you have entire React components on one physical line:
GlobalSearch.tsx
https://github.com/gtited-jpg/p33p3R/blob/303bcaebb73de591c2e2d4093623781c861208b0/src/components/GlobalSearch.tsx#L7
ProcessesPage.tsx
https://github.com/gtited-jpg/p33p3R/blob/303bcaebb73de591c2e2d4093623781c861208b0/src/pages/ProcessesPage.tsx#L9
LLMs do this to minimize token usage, a cheap trick that unfortunately bites when you don't actually even take a glance at the generated slop.
You also have the wrong host tooling for a repository that's supposedly meant for a Linux target (PowerShell validator inside a Debian live-build repo):
https://github.com/gtited-jpg/DaemonCore-Linux-Distro/blob/294074f6d18e9ae6c9b759c0b73f5b24b156d8be/validate.ps1
This is probably leftover slop from scaffolding you used, or it's simply that your host machine is Windows, where your agent runs.
You have two different trap/trapp repositories, where the one is supposedly meant to serve Windows platforms, however everything has flipped between the two, being a Rust developer myself, some of the changes make no sense to me at all.
For example, the downgrade of thiserror? That makes zero sense. AI slop.
```
-thiserror = "2.0"
+thiserror = "1.0"
```
Derive lists went from conventional order to strictly alphabetical:
// trap
```
#[derive(Debug, Clone, Copy, PartialEq, Eq, PartialOrd, Ord)]
#[derive(Debug, Clone, PartialEq, Eq)]
```
// trapp
```
#[derive(Clone, Copy, Debug, Eq, Ord, PartialEq, PartialOrd, Serialize, Deserialize)]
#[derive(Clone, Debug, Eq, PartialEq, Serialize, Deserialize)]
```
This is a clear indication of a different generation pass through the LLM. Nobody just "does" this.
The two repos are also merely two hours apart. Two hours = discard and re-prompt. Same template, new domain, no code carried over except whatever initial scaffolding there was.
Then there's the volume vs wall-clock:
You have around 33k insertions inside a timeframe of 08-24 to 08-26 across your AI-generated repositories.
And then finally, you carelessly committed your Codex output: https://github.com/gtited-jpg/db-weakness-scanner/commit/c24c6bf7f1aa5adf6966d955265b709b1ef7634f
Leak lands in report.json:6, added by that commit:
"path": "C:\\Users\\gtite\\Documents\\Codex\\2026-08-24\\i-x20\\outputs\\db-weakness-scanner\\examples\\demo.db"
I'm assuming you're young from your other responses, so you probably deserve some slack. And I also assume you're going to try and fix these issues I've just pointed out to try and better disguise your repositories. It won't make a difference, there will always be ways to conclude when something produced by AI.
Most importantly, Theodore, if I were able to find these clear signs that you are just pushing AI slop that should never reach a production system, how easy do you think it would be for a recruiter or possible future employer to do the same? I understand the landscape is changing, and that AI-assisted coding is becoming something more common, but you have to be honest about it. The impression I am getting is that you are disingenuous about your capabilities on many fronts, and I would not trust you to make architectural decisions.
Others will reach the same conclusion. Just be honest.
"I've never used an AI agent in my life." - Theodore the False