A lawyer.
Scanning dense legalese and/or contract language becomes quite a bit easier if you have an easy visual cue where the current (tortured) sentence will end. It provides a decent estimate for the upper bound for how much context and/or state you need to keep in your head to process a given statement.
I get to review technical and security parts of contracts at work and can see the value for such a font in that particular case.
The "@" looks thinner than the other chars.
The "%" has its fraction slash cut in 2 non aligned non rectilinear parts (and not coherent with their "‰" and "‱").
(Also, the "€" looks weird to me, maybe because the horizontal lines are of the same length ? But that's probably less important in a coding context)
Not just that, why is the backtick unconditionally combining with the previous letter? If you type "a`" it will always print "à" for me, even combining with letters like "t", seems like a ligature table bug or something. Just randomly saw that when looking at a markdown file
1) The braces are completely horrible
2) What kind of person thinks that making the fullstop massive and putting it in the middle of the line like a dot product sign is good?
3) Where even is the backtick?
4) For all their talk of legibility, lowercase l and 1 are very similar looking to my eyes.