The problem with being the best developer I meet this year is twofold.
Firstly, it's unlikely that your definition of 'best" and my definition of "best" co-incide. Being a developer encompasses a wide range of skills, technical skills like writing code, writing helpful documentation, interacting with colleagues, architecting for the future, fixing other peoples bugs and more. Unless your priority order is the same as mine, knowing you're good at one thing can get a hindrance.
But leaving that aside, being very good at something (and more importantly knowing it) seldom makes for a good team mate. It comes with an attitude that is less likely to conform with what we do here, less likely to admit when you're wrong, less likely to adapt when we have priorities other than yours.
I'll also point out that your additude to non-developer topics should be one of privacy. I don't really want to know your political views, or your views on crypto, or your brushes with race, ethnicity and so on. If you vered into any of those topics in an interview I'd be alarmed. Even if asked your answers in those areas should be non-committal. And if I did ask about something like crypto (I dont) I'd be looking for a measured answer that showed you can understand both sides of an argument, that you can admit when a position is controversial, that while there are positives there are also negatives and so on.
I say this not to negate you, but perhaps to help you grow in your interviewing skills. It's just fine to be white, libertarian, into crypto, 35 years old, whatever. But interviewing is about getting to know someone, and TMI can be, well, too much.
I get where you're coming from, I really do, and you may be a great developer, but unfortunately you may not be a great employee just yet. And ultimately they're hiring an employee first, a developer second.
Firstly, it's unlikely that your definition of 'best" and my definition of "best" co-incide. Being a developer encompasses a wide range of skills, technical skills like writing code, writing helpful documentation, interacting with colleagues, architecting for the future, fixing other peoples bugs and more. Unless your priority order is the same as mine, knowing you're good at one thing can get a hindrance.
But leaving that aside, being very good at something (and more importantly knowing it) seldom makes for a good team mate. It comes with an attitude that is less likely to conform with what we do here, less likely to admit when you're wrong, less likely to adapt when we have priorities other than yours.
I'll also point out that your additude to non-developer topics should be one of privacy. I don't really want to know your political views, or your views on crypto, or your brushes with race, ethnicity and so on. If you vered into any of those topics in an interview I'd be alarmed. Even if asked your answers in those areas should be non-committal. And if I did ask about something like crypto (I dont) I'd be looking for a measured answer that showed you can understand both sides of an argument, that you can admit when a position is controversial, that while there are positives there are also negatives and so on.
I say this not to negate you, but perhaps to help you grow in your interviewing skills. It's just fine to be white, libertarian, into crypto, 35 years old, whatever. But interviewing is about getting to know someone, and TMI can be, well, too much.
I get where you're coming from, I really do, and you may be a great developer, but unfortunately you may not be a great employee just yet. And ultimately they're hiring an employee first, a developer second.