Where can I ask questions about code?

Where can I ask questions about code?

With this goal in mind, we decided to make a blog post about websites, where you can ask all of your programming questions.

  • Stack Overflow.
  • Quora.
  • Reddit.
  • CodeProject.
  • CodeRanch.
  • Programmers Heaven.
  • FindNerd.
  • Chegg.

How do I ask a question about information?

Ten Tips for Asking Good Questions

  1. Plan your questions.
  2. Know your purpose.
  3. Open conversation.
  4. Speak your listener’s language.
  5. Use neutral wording.
  6. Follow general questions with specific ones.
  7. Focus your questions so they ask one thing at a time.
  8. Ask only essential questions.

How do you ask for code review?

How to get your code reviewed faster

  1. Before you start. Every team has its own standards and best practices.
  2. Make sure your code is ready.
  3. Do a self review.
  4. Show what you’ve done.
  5. Ask questions.
  6. Don’t do changes for the sake of changes.
  7. Don’t ignore comments.
  8. Make it clear when you’re done with the changes.

What questions can you ask a question?

Break the ice and get to know people better by selecting several of these get-to-know-you questions.

  • Who is your hero?
  • If you could live anywhere, where would it be?
  • What is your biggest fear?
  • What is your favorite family vacation?
  • What would you change about yourself if you could?
  • What really makes you angry?

How do I ask for help on github?

For issues with the the code you should use https://github.com/callmeal/Flickr4Java/issues. However, to reach out to the author/maintainer with something not code related or bug, you should find out if he has his email or equivalent public.

How many HCPCS coding questions do you need?

Please submit no more than one (1) question per request. Pertinent medical record documentation that will provide information to assist the Central Office in determining the appropriate HCPCS code assignment must be included (if applicable).

How to explain code in the same language?

Explain the code in the same language the users use. Explain the code using standard programmer terms, e.g. Terms like “buffer”, “list”, “singleton” are familiar to most of us, as are common mathematical terms. Explain what you’re doing in terms of the inputs and outputs. Invent words for concepts you don’t have words for.

When do you need source code explaining skill?

The most difficulties happen when I explain how a particular small piece of code works. The funny thing is, that explaining and providing examples on how something works on a much higher level, e.g. interactions between separate modules and subsystems, is much easier for me. To make it clearer, what I call “source code explaining skill” is a

How can I become better on explaining the code to other programmers?

Explain the code in the same language the users use. Explain the code using standard programmer terms, e.g. Terms like “buffer”, “list”, “singleton” are familiar to most of us, as are common mathematical terms. Explain what you’re doing in terms of the inputs and outputs.