Depends on typography traditions. In Russian, em-dash in the middle of a sentence is always typeset with short spaces. We also rarely use en-dashes (I think there are maybe two cases when it is allowed: in date ranges like 1940–1945 and as a bullet point in lists).
Man, just post a link to CV like you're advised and let good things happen to you. If they don't, you lose nothing, but if they do, you got something out of your effort.
Russian laws effectively prohibit all kinds of internet pornography. More precisely, they restrict "unlawful distribution of pornography", but never define any "lawful" way to do so.
---
That said, if it weren't pornography, small rant about our judicial system:
Any judge in any city pop 50000 can issue a country-wide block for any site. Often these resolutions are too far reaching, sometimes they order to block root page (/) instead of specific page (/foo/bar), rendering whole sites unavailable. Sometimes they ban ip addresses of aws services, disrupting half the internet.
Another important thing about these hearings is that there is often no defendant. They might call in the site hoster, but hosters are never interested in defending their customers so they simply ignore the subpoena. Site owner would often discover their site was blocked after the fact.
Finally, in many cases judges don't even bother writing their own verdict. Instead they copy-paste whatever public attorney cooked up, including all the factual and orthographic errors, and sign it.
https://medium.com/@aalien/law-limits-8d733178e158 this is a very insightful post (alas, only available in Russian) from @aalien, founder of lurkmore.ru, which is arguably the most often banned site in Russia, about how this horrible system functions (or rather, malfunctions). I found this excerpt especially hilarious:
«Full list of Roskomnadzor-banned pages is available on our site. Unfortunately, that page is also banned by Roskomnadzor, because it contains "textual information about committing suicide". It's in the quoted Roskomnadzor letter, of course»
> Now, the JS community seems to be thinking more about stability and backwards compatibility. That's very welcome, at least from the perspective of this grumpy server-side developer.
That's exactly why the blog post suggests using yarn instead of npm, isn't it?
Yeah, civ 5 ai sucks, and don't even get me started about combat (builds all the wrong units and can't properly control the armies it has). I blame 1-unit-per-tile change.
It's a shame, especially since in multiplayer this game is amazing (except for, cough, networking code, cough).
In rails/graphql combo it's resolved the same way you usually resolve n+1 queries: you make 1 request per type of edge (i.e. one request for posts, one request for authors, on request for comments)
> This isn't failure; it's the process!
> The biggest challenge? AI can't retain learning between sessions
ai slop