Perhaps, silence would be a good choice on this issue?
To my view, coding is as much art as science, and it is limitlessly fascinating to me how different people find different ways of expressing ideas and solutions.
Also, the code review process is fraught with opportunities for insult, misunderstanding and unfortunate power dynamics. It is inherently difficult regardless of the actual content being reviewed.
On the other hand, if there is a significant issue here "I am having trouble following your thinking here. Perhaps dividing this up into smaller functions would help?" Might be a good review comment?
The style wars are very tempting to engage in, but they virtually never drive greater productivity, real quality improvements, or positive team dynamics.
If there are real reasons that this wants to be broken out into a separate function (reusability for instance), then make that clear in your suggestion.
It is super fantastic that you have been able to learn, grow, and achieve so much. You do sound like a super star. It also sounds like you have reached a point where transition is required.
I respectfully disagree with those who say "get a new job". This may be a good idea, but it is certainly not a solution to your issues which are very likely to come with you wherever you go.
I suggest that you stop contributing so much under your own name, and start helping others contribute under their names. "Not much grows under a great oak". You may be casting a shadow that makes it hard for your colleagues to grow?
10x developers are awesome, but very hard to scale. Far more powerful are the "super colleagues" who make everyone around them 5x better. Add a 10x developer to a team of 10 and you 2x the team's output. Add a super colleague to the same team and output rises by 5x.
Perhaps instead of focusing your energy on loneliness it would be helpful to ignore it and focus instead on the things that you like and genuinely enjoy. Things that often leave you feeling better afterward than you did before you started. These things can be big or small. For me some examples are riding my bike, drinking a glass of cool water, planting seeds (more or less anything, but particularly tomatoes), walking around the neighborhood, cooking my brains in a sauna, going to the beach. If you can't think of any, then experiment. Check your status before and after each activity. Make sure to keep judgement relative and incremental. Things don't need to blow your mind. Even things that make you feel just marginally less shitty are a great place to start!
Try to focus on those things that "fill your bucket" whatever they are. Consciously spend more time engaging with those things, and spend less time on everything else. Cooking get you down? Stop. Playing chess perk you up? Play more chess... find new venues in which to play chess (or whatever, chess is not for me, just a theoretical example).
As you get better at filling your bucket, you will surely meet new people along the way. Do they fill your bucket? Engage more. Drain your bucket? Engage less.
The whole idea is a bit like Yoga... slowly and gently stretch your time-spent in happier directions.
Another thought... as you meet new people remember that a lot of them won't be a good fit for you for reasons that have 0% to do with you. Don't take it personally. If 1 in 20 new interactions is positive you are doing super fabulous! Stick to it. Those positive interactions will add up. Make sure you have time in your life to spend on them when the do happen. Having a good chat with the barista, be 5 minutes late to your morning meeting and let the people behind you enjoy the anticipation of their morning coffee for a bit longer.
Take your time, take it easy, and seek out fun... genuine fun for you, not what anyone else thinks is fun (a-doy!). People who are your kind of fun will be there when you arrive.
Not included in this analysis is leakage rate... by which I mean ooze leakage.
I have found that some batteries have a much greater likelihood of leaking ooze than others (yeah Rayovak, I'm looking at you!)
Except in the case of crappy toys, the damage that this causes radically outstrips the cost of the battery.
As a result, I buy batteries not based on electrical performance, but track record in not ruining the things I put them into. I am very happy to accept 50% less energy if I can avoid destroying my $200 gadget.
Yeah... I don't want to make this stuff, I want to use this stuff.
It would be great to get an understanding of its performance specs. I may be able to specify hardened wood in place of steel, aluminum, magnesium machined parts in high-end ecologically conscious consumer products... but not without some understanding of the engineering specifications and a source of material.
I was in a similar state at times in my early 20s. My advice is...
#1 Don't harm yourself. You are in a rough patch. It will be over at some point. Life is really very hard some times, but not all the time. Some times it is really fun and lovely. Those times will come again.
#2 Whenever you do something (work on a project/spend time with people/walk in nature/check in with social media) ask yourself do you feel better, healthier, happier, stronger after this activity or do you feel worse. Focus on those people and activities that "fill your bucket". To the greatest degree possible avoid people and actives that empty your bucket.
#3 Don't worry about it too much. Take it easy on yourself and be patient with yourself. Do worry too much about social media profiles. They aren't real. To the degree they are real, they are not the full story. Just try to have a good time where ever you can. Be nice to yourself.
To my view, coding is as much art as science, and it is limitlessly fascinating to me how different people find different ways of expressing ideas and solutions.
Also, the code review process is fraught with opportunities for insult, misunderstanding and unfortunate power dynamics. It is inherently difficult regardless of the actual content being reviewed.
On the other hand, if there is a significant issue here "I am having trouble following your thinking here. Perhaps dividing this up into smaller functions would help?" Might be a good review comment?
The style wars are very tempting to engage in, but they virtually never drive greater productivity, real quality improvements, or positive team dynamics.
If there are real reasons that this wants to be broken out into a separate function (reusability for instance), then make that clear in your suggestion.