Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

77%
+5 −0
Meta Should I post a link to the Github repo for code reviews?

Welcome! It's best if the code being reviewed is here on the site, for ease of reference and defense against link rot. That sounds like a sizable program; are there key parts you'd like review on...

posted 2y ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2022-02-21T20:20:28Z (over 2 years ago)
Welcome!

It's best if the code being reviewed is here on the site, for ease of reference and defense against link rot.  That sounds like a sizable program; are there key parts you'd like review on, as opposed to the whole thing?  You could include the GitHub link for anybody who wants to run it as part of the review, but most of our code reviews have focused on smaller pieces.  The various utility methods, accessors, etc probably aren't the interesting part, right?  Also, if you focus on the most important parts, you're more likely to get good feedback from reviewers, as you'll make it easy for them to skip the routine stuff and focus on the meat.