Thanks for taking the time to contribute an answer. It’s because of helpful peers like yourself that we’re able to learn together as a community. Here are a few tips on how to make your answer great:

Pay it forward

Saying “thanks” is appreciated, but it doesn’t answer the question. Instead, vote up the answers that helped you the most! If these answers were helpful to you, please consider saying thank you in a more constructive way – by contributing your own answers to questions your peers have asked here.

Have the same problem?

Still no answer to the question, and you have the same problem? Help us find a solution by researching the problem, then contribute the results of your research and anything additional you’ve tried as a partial answer. That way, even if we can’t figure it out, the next person has more to go on. You can also vote up the question or set a bounty on it so the question gets more attention.

Answer the question

Read the question carefully. What, specifically, is the question asking for? Make sure your answer provides that – or a viable alternative. The answer can be “don’t do that”, but it should also include “try this instead”. Any answer that gets the asker going in the right direction is helpful, but do try to mention any limitations, assumptions or simplifications in your answer. Brevity is acceptable, but fuller explanations are better.

Provide context for links

Links to external resources are encouraged, but please add context around the link so your fellow users will have some idea what it is and why it’s there. Always quote the most relevant part of an important link, in case the external resource is unreachable or goes permanently offline.

Write to the best of your ability

We don't expect every answer to be perfect, but answers with correct spelling, punctuation, and grammar are easier to read. They also tend to get upvoted more frequently. Remember, you can always go back at any time and edit your answer to improve it.

Answer well-asked questions

Not all questions can or should be answered here. Save yourself some frustration and avoid trying to answer questions which...

  • ...are unclear or lacking specific details that can uniquely identify the problem.
  • ...solicit opinions rather than facts.
  • ...have already been asked and answered many times before.
  • ...require too much guidance for you to answer in full, or request answers to multiple questions.
  • ...are not about quantitative finance as defined in the help center.

Don't forget that you can edit the question you're answering to improve the clarity and focus - this can reduce the chances of the question being closed or deleted.

Always be polite and have fun

It’s fine to disagree and express concern, but please be civil. There’s a real human being on the other end of that network connection, however misguided they may appear to be. We’re here to learn from our peers, not yell at each other.
https://quant.stackexchange.com/help/how-to-answer
quant.stackexchange.com
crawl=CC-MAIN-2020-50
79399
application/http; msgtype=response
sha1:TBBPU4DIZ4GWGGDMLMW4IJV5PNKOLTML
<urn:uuid:509b2615-14ec-465b-8c4a-87a236127171>
2020-12-02T19:26:32Z
151.101.129.69
text/html
sha1:T7L6JJE43PQVZYIQZZTVF3NZJVKH3FIT
<urn:uuid:d4d992df-0839-40a1-86f3-1baeb011ee79>
https://quant.stackexchange.com/help/how-to-answer
response
<urn:uuid:deaf8d64-1f83-42a4-baf5-fe117c35d7c2>
isPartOf: CC-MAIN-2020-50
publisher: Common Crawl
description: Wide crawl of the web for November/December 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-121.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/