The assumption underneath most of these rooms is that competence has a paper trail. A degree from the right place, a title that took years to earn, a certification issued by someone with the standing to issue it. Show the paper, and the room grants you the competence. No paper, and the competence is on you to prove twice.
I don't have the paper. Associate's degree, community college. No engineering pedigree, no computer-science credential, nothing that would let me walk into a room and have the competence assumed on my behalf. I say that up front, on purpose, because hiding it would be the weaker move.
The paper is supposed to be a proxy for one question: can you actually do the work. The degree is evidence, not the thing itself, a reasonable bet that someone who completed it can probably do the associated work. But it's a bet on a proxy. The work is the real target, and the work can be demonstrated directly, without the proxy in the way.
So I demonstrate it directly. Not "I'm qualified to build this", here is the thing, built. Not "trust the credential", check the work. When you can't point to the paper, you have to point to the output, and pointing to the output turns out to be a stronger position than pointing to the paper, because the output is the thing the paper was only ever promising.
Leading with what I'm not, no degree, no pedigree, no title that did the vouching for me, does something counterintuitive. It moves the entire conversation onto the ground where I'm actually strong. If the question is "what school," I lose. If the question is "does the thing work," I have an answer, and it answers the question the credential was standing in for.
There's a habit that comes with learning this way, and it's the part I'd keep even if someone handed me the pedigree retroactively. Nothing was ever assumed. Every piece of it got learned because a specific thing needed doing and the knowledge wasn't there yet, so it had to be built, which means I never inherited the confidence that comes with a credential, the quiet assumption that because you were taught the thing, you know it.
I approach every tool the way you approach a system you inherited and don't trust yet: assume it has blind spots I haven't found. That instinct is worth more than the confidence a degree installs. The credential tells you you're qualified. The absence of one keeps you checking.
Nobody handed me a credential for this. I built the thing the credential was supposed to prove I could build, and the thing is the part that was ever going to matter.
[SOURCED] Self-taught; associate's degree, community college; no engineering pedigree or degree-based credential.
• Degree duration deliberately not stated (unresolved verification debt).
• No claim or implication of any certification, the word "certified" appears nowhere.