Earlier quoted context omitted.
A key "ah-ha" moment for me was realizing that your wallet is your login on every dApp that's ever existed or ever will exist. It's pseudonymous and developers sort of get various things for free out of it as a result(payments, authorization, authentication)
There's also the potentially interesting idea of wallet-as-resume. IE allowing different types of access depending on what sorts of things you've done with your wallet in the past. Certainly not for all applications, but a certain level of implied competency might be appropriate in some cases.
How does "wallet as resume" solve the implied competency better than a GitHub repo with signed commits?
How does the wallet-as-resume solve the "I copied a project" or "I followed the tutorial line for line?" One can create a NFT or whatever equivalent for code you wrote just as easily as code you copied (be it with cp or typing it all in yourself). Can only one person would be verify a particular implementation of FizzBuzz? If the code is copied, can the original author usurp the "I wrote this" from a pretender?
Does anyone reading resumes actually think that this is a problem that needs solving?