As Anders said near the end of the video, if you want to know more, look at the source code[1]. Speaking as someone who&#x27;s worked on it (so I&#x27;m biased), I feel it&#x27;s pretty easy to jump in and edit (though I&#x27;d advise new people to avoid the typechecker unless you feel particularly adventurous, it&#x27;s a multi-thousand line long monster file). There are piles of easy issues[2] that are looking for community members to work on them.<p>By the way - one of the most meaningful comments he made in this talk (to me) was when he said that your parser had to &quot;parse more than the allowed grammar&quot; so you can provide better error messages. Compilers are, ultimately, tools for developers - so developer experience is tantamount. This, I&#x27;ve found, is so very very true in any smaller projects I&#x27;ve worked on, and is easily one of the first things neglected by some of my more algebraically inclined peers (who are very satisfied with a perfect ABNF and a parser which strictly adheres to it).<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;TypeScript" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;TypeScript</a>
[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;TypeScript&#x2F;labels&#x2F;Effort%3A%20Easy" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Microsoft&#x2F;TypeScript&#x2F;labels&#x2F;Effort%3A%20E...</a>