Skip to main content
deleted 4 characters in body
Source Link
Heslacher
  • 51k
  • 20
  • 35

The short answer is, if you know that your code has deficiencies that need to be fixed, then it is not ready to be reviewed here.

In general, we expect questions to have no known bugs. It might be OK to declare known issues, but only if you consider them to be insignificant or irrelevant for your intended deployment. Otherwise, you should fix those issues before asking for a review.

Asking for advice about features that have not yet been implemented is strictly off-topic for Code Review, because incomplete code would not be "working correctly as intended".

In summary, you should finish the your project, make the code as good as you can possibly make it, and ensure that it works to your satisfaction, before posting it here for a review.

The short answer is, if you know that your code has deficiencies that need to be fixed, then it is not ready to be reviewed here.

In general, we expect questions to have no known bugs. It might be OK to declare known issues, but only if you consider them to be insignificant or irrelevant for your intended deployment. Otherwise, you should fix those issues before asking for a review.

Asking for advice about features that have not yet been implemented is strictly off-topic for Code Review, because incomplete code would not be "working correctly as intended".

In summary, you should finish the your project, make the code as good as you can possibly make it, and ensure that it works to your satisfaction, before posting it here for a review.

The short answer is, if you know that your code has deficiencies that need to be fixed, then it is not ready to be reviewed here.

In general, we expect questions to have no known bugs. It might be OK to declare known issues, but only if you consider them to be insignificant or irrelevant for your intended deployment. Otherwise, you should fix those issues before asking for a review.

Asking for advice about features that have not yet been implemented is strictly off-topic for Code Review, because incomplete code would not be "working correctly as intended".

In summary, you should finish your project, make the code as good as you can possibly make it, and ensure that it works to your satisfaction, before posting it here for a review.

Source Link
200_success
  • 145.6k
  • 4
  • 114
  • 284

The short answer is, if you know that your code has deficiencies that need to be fixed, then it is not ready to be reviewed here.

In general, we expect questions to have no known bugs. It might be OK to declare known issues, but only if you consider them to be insignificant or irrelevant for your intended deployment. Otherwise, you should fix those issues before asking for a review.

Asking for advice about features that have not yet been implemented is strictly off-topic for Code Review, because incomplete code would not be "working correctly as intended".

In summary, you should finish the your project, make the code as good as you can possibly make it, and ensure that it works to your satisfaction, before posting it here for a review.