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 Is this a good fit for Code Reviews, and if so, how to best post it?

400 lines is not that big, it should be fine to post the complete program below the Code Reviews post category. I'd post it as separate code formatted blocks with one block per file indeed. A revi...

posted 3y ago by Lundin‭  ·  edited 3y ago by Lundin‭

Answer
#2: Post edited by user avatar Lundin‭ · 2021-09-14T13:56:49Z (about 3 years ago)
  • 400 lines is not that big, it should be fine to post the complete program below the Code Reviews post category.
  • I'd post it as separate code formatted blocks with one block per file indeed. A reviewer can then fairly easily reproduce the project. Plus then you'll get a review on the overall design and file structure as well.
  • Include everything else that's relevant too, like compiler options, pictures, requirements, use-cases.
  • 400 lines is not that big, it should be fine to post the complete program below the Code Reviews post category.
  • I'd post it as separate code formatted blocks with one block per file indeed. A reviewer can then fairly easily reproduce the project. Plus then you'll get a review on the overall design and file structure as well. Alternatively you could give a Github link or similar.
  • Include everything else that's relevant too, like compiler options, pictures, requirements, use-cases.
#1: Initial revision by user avatar Lundin‭ · 2021-09-14T13:41:26Z (about 3 years ago)
400 lines is not that big, it should be fine to post the complete program below the Code Reviews post category.

I'd post it as separate code formatted blocks with one block per file indeed. A reviewer can then fairly easily reproduce the project. Plus then you'll get a review on the overall design and file structure as well.

Include everything else that's relevant too, like compiler options, pictures, requirements, use-cases.