This may just be a cognitive bias on my side of things, but, I've found that a lot of the time when you ask people you don't work with to review your code, they tend to review it savagely, and with the intent of completely, and absolutely destroying you for "likes", "upvotes", etc.<p>A lot of the time I just want to figure out if I'm going down the right path before I have anything perfect, or breathlessly beautiful to ask for feedback on.<p>A lot of the time, I'm learning a new technology or a new paradigm and don't know what I'm doing, and, asking for help on Reddit or StackOverflow usually just means being roasted.<p>Is there any way to avoid the roasts?<p>Is there a different community everyone goes to?
I believe this community would be different: <a href="https://www.recurse.com/" rel="nofollow">https://www.recurse.com/</a><p>Based on their social rules: <a href="https://www.recurse.com/social-rules" rel="nofollow">https://www.recurse.com/social-rules</a><p>However, it might be difficult to get in...
TIL: all code posted for review on <a href="https://codereview.stackexchange.com/" rel="nofollow">https://codereview.stackexchange.com/</a> has to be compilable.<p>I noted that a function wasn't available in the snippet in my post, but 2 users still voted to remove the question without any feedback, person-to-person communication, etc., because it broke the rules.<p>While I'm a rule-breaker, and the problem, maybe GPT4 is where to go for code reviews.
Painful suggestion: I reframe the savagery as a free consultation by folks with poor people skills. Often one or two of the reviews gives you actionable results. I view this exercise as something you akin to learning how to be a sales person: a very unpleasant experience at first but eventually you develop a new muscle/superpower. Being coachable can take you pretty far.
<a href="https://codereview.stackexchange.com/" rel="nofollow">https://codereview.stackexchange.com/</a> may be worth a shot; I know it's a common meme that the stackexchange sites are a cesspool but my experience has been "garbage in, garbage out"<p>Also, I would guess the "review it savagely" and "absolutely destroying you" part is likely projection, or perhaps not setting expectations of what outcome you want from any such review. If it's "what's wrong with this code?" one will get a monster range of responses. If you have specific concerns, then stating them as specific success criteria will likely improve your experience<p>Without any question you will want to consider the audience of peers when asking for reviews. Stopping by r/Programmer and soliciting input is a good way to get the lolz; posting in a more targeted forum for your language or framework or both, or even asking your followers on any social media presence may get less firehose from the Internet
It's fun to write code you don't need reviewed. Build wondrous things, accept contributions (or not), and enjoy each project as its own gem.<p>If you want code reviewed, contribute to existing projects.<p>Part of getting better is realizing the previous work needs to be rewritten. Your past self wouldn't have known that at the beginning. But you got better.
I had a good experience while learning Ruby by asking on the Ruby discord channel. Everyone was supportive and there's a core group of highly knowledgeable users. A lot of people ask for help there, and it's a very positive environment.<p>Additionally on most sub-reddits I've seen people get good constructive feedback on their code.<p>If you can find such discord channels where the environment is non-toxic (I doubt any coding oriented ones are) and the users are active, that could be the ideal option.