Too many emojis in 'Concurrency and async / await' explanation
1–10 of 19 posts
Re: Too many emojis in 'Concurrency and async / await' explanation
#2Maybe I'm just an old man yelling at clouds, but I always found the use of emoticons and emoji in official documents extremely off putting. If you want to look hip and cool, at least do so only where appropriate - public-facing technical documentation needs to be articulate and maximally accessible.
Not to mention how inconvenient it is to actually add emoji. Chances are that the person who wrote that page didn't draft it from a phone with an easily accessible emoji keyboard, nor from a physical keyboard with emoji bindings. So they'd have to go out of their way to open up an on-screen emoji keyboard, or an emoji webpage, and paste those emojis one by one.
Re: Too many emojis in 'Concurrency and async / await' explanation
#3Maybe I'm just an old man yelling at clouds, but I always found the use of emoticons and emoji in official documents extremely off putting. If you want to look hip and cool, at least do so only where appropriate - public-facing technical documentation needs to be articulate and maximally accessible. Not to mention how inconvenient it is to actually add emoji. Chances are that the person who wrote that page didn't dra…
No you're not old, you are just not ridiculously young. :)
I agree though, use of emoji outside talking to your friend, to me, is an instant warning of immaturity, and a flag of more to come.
The OP post was horrendous to look at, I'm not sure why anyone thought that it would help with understanding the content.
Re: Too many emojis in 'Concurrency and async / await' explanation
#4here's the relevant documentation part in context https://fastapi.tiangolo.com/async/#concurrent-burgers who writes this stuff? who writes "your crush [Heart Eyes Emoji]" not just once but over and over, in documentation for a project? could easily just say "your friend [no emoji]"
Re: Too many emojis in 'Concurrency and async / await' explanation
#5here's the relevant documentation part in context https://fastapi.tiangolo.com/async/#concurrent-burgers who writes this stuff? who writes "your crush [Heart Eyes Emoji]" not just once but over and over, in documentation for a project? could easily just say "your friend [no emoji]"
To quote Michael Scott, “it looks like it was made by a 2-year old monkey!”
Re: Too many emojis in 'Concurrency and async / await' explanation
#6Aren't emojis supposed to replace words, kind of like abbreviations? What's the point of having a word and an emoji that mean the same thing right next to each other? I would never write, "want a hamburger :hamburger:?" Instead, I would just write, "want a :hamburger:?" This just seems like the worst of both worlds.
EDIT: HN doesn't seem to support emojis. Changed to a markdown like format instead.
Re: Too many emojis in 'Concurrency and async / await' explanation
#7here's the relevant documentation part in context https://fastapi.tiangolo.com/async/#concurrent-burgers who writes this stuff? who writes "your crush [Heart Eyes Emoji]" not just once but over and over, in documentation for a project? could easily just say "your friend [no emoji]"
You mean "Smiling face with heart eyes", and I never want to hear this phrase spoken out in my life again. It kinda started to make me aggressive after the 5th time or so.
Re: Too many emojis in 'Concurrency and async / await' explanation
#8An author of an open source project may do what they want, including using emoji in documentation like this.
On the flip side, I would never allow that code to be used in any of my projects, nor would I want to work with any contributors that think it is a "good" practice (nevermind "best"). To my mind, this documentation screams "unprofessional". I would be embarrassed to show it to any of my customers.
The code is not be the only thing by which a project should be judged. Bad documentation is worse than no documentation, because the author had a choice about the format and style that will be used. This project chose... poorly.
Re: Too many emojis in 'Concurrency and async / await' explanation
#9Maybe I'm just an old man yelling at clouds, but I always found the use of emoticons and emoji in official documents extremely off putting. If you want to look hip and cool, at least do so only where appropriate - public-facing technical documentation needs to be articulate and maximally accessible. Not to mention how inconvenient it is to actually add emoji. Chances are that the person who wrote that page didn't dra…
Ctrl+Cmd+Space brings up an emoji picker on macOS, you don’t have to paste anything
Re: Too many emojis in 'Concurrency and async / await' explanation
#10Aren't emojis supposed to replace words, kind of like abbreviations? What's the point of having a word and an emoji that mean the same thing right next to each other? I would never write, "want a hamburger :hamburger:?" Instead, I would just write, "want a :hamburger:?" This just seems like the worst of both worlds. EDIT: HN doesn't seem to support emojis. Changed to a markdown like format instead.
And yet, the first one is okay, and the second makes you look a mite out of touch (at least where I live). On could also simply send :hamburger:?