Skip to main content
Code Review

Return to Question

added 4 characters in body
Source Link
selbie
selbie
  • 195
  • 3

I find myself answering a lot of questions on StackOverflow about sockets and network programming. I typically answer a lot questions from developers who are new to sockets and network coding - and they typically repeat the same mistakes.

These common mistakes range from mishandling of function return codes, not understanding TCP stream sockets, assumptions about message sizes, buffer overruns, and bad design patterns.

It's very easy to get socket code to "mostly work" - especially when testing is limited to the same subnet or same machine. Then the developer is left wondering why it doesn't seem to work as well when deployed to the Internet.

I am considering writing a blog article on "top 10 mistakes developers make with socket code". The text would include sample code with commentary. And then I might reference the text when answering future questions on StackOverflow.

After I'm done writing it up, would it be permissible to solicit for editorial and technical feedback on it through the CodeReview site? I don't profess to be the world's greatest socket expert, but someone who hangs out on the CRCodeReview might be.

I find myself answering a lot of questions on StackOverflow about sockets and network programming. I typically answer a lot questions from developers who are new to sockets and network coding - and they typically repeat the same mistakes.

These common mistakes range from mishandling of function return codes, not understanding TCP stream sockets, assumptions about message sizes, buffer overruns, and bad design patterns.

It's very easy to get socket code to "mostly work" - especially when testing is limited to the same subnet or same machine. Then the developer is left wondering why it doesn't seem to work as well when deployed to the Internet.

I am considering writing a blog article on "top 10 mistakes developers make with socket code". The text would include sample code with commentary. And then I might reference the text when answering future questions on StackOverflow.

After I'm done writing it up, would it be permissible to solicit for editorial and technical feedback on it through the CodeReview site? I don't profess to be the world's greatest socket expert, but someone who hangs out on the CR might be.

I find myself answering a lot of questions on StackOverflow about sockets and network programming. I typically answer a lot questions from developers who are new to sockets and network coding - and they typically repeat the same mistakes.

These common mistakes range from mishandling of function return codes, not understanding TCP stream sockets, assumptions about message sizes, buffer overruns, and bad design patterns.

It's very easy to get socket code to "mostly work" - especially when testing is limited to the same subnet or same machine. Then the developer is left wondering why it doesn't seem to work as well when deployed to the Internet.

I am considering writing a blog article on "top 10 mistakes developers make with socket code". The text would include sample code with commentary. And then I might reference the text when answering future questions on StackOverflow.

After I'm done writing it up, would it be permissible to solicit for editorial and technical feedback on it through the CodeReview site? I don't profess to be the world's greatest socket expert, but someone who hangs out on CodeReview might be.

Source Link
selbie
selbie
  • 195
  • 3

Is it permissible to solicit techincal feedback for a blog entry on coding

I find myself answering a lot of questions on StackOverflow about sockets and network programming. I typically answer a lot questions from developers who are new to sockets and network coding - and they typically repeat the same mistakes.

These common mistakes range from mishandling of function return codes, not understanding TCP stream sockets, assumptions about message sizes, buffer overruns, and bad design patterns.

It's very easy to get socket code to "mostly work" - especially when testing is limited to the same subnet or same machine. Then the developer is left wondering why it doesn't seem to work as well when deployed to the Internet.

I am considering writing a blog article on "top 10 mistakes developers make with socket code". The text would include sample code with commentary. And then I might reference the text when answering future questions on StackOverflow.

After I'm done writing it up, would it be permissible to solicit for editorial and technical feedback on it through the CodeReview site? I don't profess to be the world's greatest socket expert, but someone who hangs out on the CR might be.