That’s an incorrect summary of my comments, which is NOT your fault, rather it’s my fault for not finding a way to express myself clearly. I know you’re just sharing your interpretation of my comments, which is helpful feedback for my writing. I want to correct the record on two things:
This case isn’t cause for update?
you’re saying this one individual case wouldn’t affect your beliefs.
To the contrary, I have updated my beliefs based on Constance’s story, and I believe that others will do similarly, particularly absent an answer to the question about EA job selectivity. From my original comment:
If EA(G) rejects a doctor who tries really really hard to attend (and pay for) a conference, I wonder whether the Rest-of-Us™ are wasting our time by applying for EA jobs/grants… For now, I have updated towards believing that most EA opportunities (e.g., 80K job board postings) aren’t accessible to me.
From my second comment:
The way I see it, Constance’s story is the tip of the iceberg, a symptom, if you will, of a bigger problem… I’m worried that if EAG doesn’t accept people like Constance, then the job pool might be similarly exclusive, and thousands of EA’s like me are wasting our time applying for jobs.
Just one case?
you had beliefs/concerns about exclusivity and competitiveness, driven by the case of one individual
I agree that as a general rule one shouldn’t update drastically on the basis of a single anecdote. However, the issue of EA exclusivity is not new, so my original point still stands whether or not I was aware of the other data points. Still, FWIW, I did mention more evidence in that original comment:
I now have some explanation for why I have been rejected for jobs that I’m plenty qualified for on paper. The competition must be substantially stiffer than I thought.
Markdown Syntax Reference
My User Story: As proficient markdown author and new EA Forum user, I want a reference guide for the forum’s markdown, so that I can more quickly determine the correct syntax for features that vary across markdown implementations. (E.g., footnotes took me a loooong time to figure out.)
(I suspect there’s an identical user story for new users who are NOT already used to writing markdown, but I don’t want to put words in anyone’s mouth.)
I suspect that a reference guide already exists, but my google-fu is failing me—I tried searching here, the general reference docs, github, and the code itself. As evidence that I’m not the only one, I see that the previous feature request thread has mentions a markdown cheatsheet as part of larger request for general markdown improvements. I’m hoping that adding just the syntax reference part is an easy win.