Skip to main content
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Source Link

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcomeThis has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Source Link

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.seProgrammers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

If your answer contains code that you want reviewed, then post the core part of your answer as another question. This has a precedent, and is welcome...

If you want to go through more than just the code, then as I see it, you have three options:

  • head on over to the 2nd Monitor and discuss your answer in an informal setting

  • ask your question here on meta if you want to get a formal 'is that a decent Code Review answer' discussion.

  • Programmers.se includes discussion about:

    • development methodologies and processes
    • quality assurance and testing

    as part of their on-topic scope. You could consider asking about code-review best practices there.

Going to The 2nd monitor is always a good idea, whether you want to discuss your answer, or the weather.

replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
Loading
replaced http://meta.codereview.stackexchange.com/ with https://codereview.meta.stackexchange.com/
Source Link
Loading
Better example of a question that arose from writing an answer
Source Link
200_success Mod
  • 145.7k
  • 4
  • 114
  • 284
Loading
added 240 characters in body
Source Link
rolfl Mod
  • 98.1k
  • 4
  • 117
  • 238
Loading
Source Link
rolfl Mod
  • 98.1k
  • 4
  • 117
  • 238
Loading