• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: August 11th, 2023

help-circle


  • I rushed to just grab that codeblock from Wikipedia. But the selection of which characters are considered emoji is not arbitrary. The Unicode Consortium (their Unicode Emoji Standard and Research Working Group to be exact) publishes those list and guidelines on how they should be rendered. I believe the most recent version of the standard is Emoji 15.1.

    Edit: I realized I’m going off track here by just reacting to comments and forgetting my initial point. The difference I was initially alluding to is in selection criteria. The emoji. for assigning a character a Unicode codepoint is very different from the criteria for creating a new emoji. Bitcoin has a unique symbol and there is a real need to use that symbol in written material. Having a unicode character for it solves that problem, and indeed one was added. The Emoji working group has other selection criteria (which is why you have emoji for eggplant and flying money, and other things that are not otherwise characters. So the fact that a certain character exists, despite its very limited use, has no bearing on whether something else should have an emoji to represent it.


  • There’s no ambiguity. Emoji are characters in the emoticons code block (U+1F600…U+1F64F). Emoji are indeed a subset of characters, but anything outside that block is not an emoji.

    Edit: jumped the gun on that definition, just took the code block from Wikipedia. But there is no ambiguity on which character is an emoji and which is not. The Unicode Consortium publishes lists of emoji and guidelines on how they should be rendered.







  • That is totally a non-trivial problem, which requires a lot more conception before it can be solved.

    Most candidates don’t realize that. And when I say they split by single space I mean split(' '). Not even split(/\s+/).

    Does “don’t” consist of one or two words? Should “www.google.com” be split into three parts? Etc.

    Yes, asking those questions is definitely what you should be doing when tackling a problem like this.

    If I got that feature request in a ticket, I’d send it back to conception.

    If I got it, I’d work together with the product team to figure out what we want and what’s best for the users.

    If you asked me this question in an interview, I’d ask if you wanted a programmer, a requirements analysis, or a linguist and why you invite people for a job interview if you don’t even know what role you are hiring for.

    That would be useful too. Personality, attitude, and ability to work with others in a team are also factors we look at, so your answer would tell me to look elsewhere.

    But to answer that question, I’m definitely not looking for someone who just executes on very clear requirements, that’s a junior dev. It’s what you do when faced with ambiguity that matters. I don’t need the human chatGPT.

    Also, I’m not looking for someone perfectly solving that problem, because it doesn’t even have a single clear solution. It’s the process of arriving to a solution that matters. What questions do you ask? Which edge cases did you consider and which ones did you miss? How do you iterate on your solution and debug issues you run into on the way? And so on


  • I always feel bad when I try out a new coding problem for interviews because I feel I’m going to offend candidates with such an easy problem (I interview mostly for senior positions). And I’m always shocked by how few are able to solve them. The current problem I use requires splitting a text into words as a first step. I show them the text, it’s the entire text of a book, not just some simple sentence. I don’t think I’ve had a single candidate do that correctly yet (most just split by a single space character even though they’ve seen it’s a whole book with newlines, punctuation, quotes, parentheses, etc).