Author here: Sorry for the confusing formatting on the task descriptions at the end of the paper. That "4" is the human-generated target completion, not a model generated completion. I'm not sure whether the model got that particular question correct, but from Table 3.7 that GPT-3 has 36.5% accuracy on DROP in the few-shot setting.

Many other readers were confused by this so we'll update the formatting to say "target completion" to make this more clear.

Thanks for clarifying. I'm a bit more confused though, are you saying that all of these Q&A examples are human answered, and that you were just demonstrating the format / question types for Q&A? If so, is there any way to see some of the model's responses?

Thank you.

It adds important things like: "Review OKRs", "Planning sync", etc.

https://www.dropbox.com/s/7xizuaap0lbjt0k/Screenshot%202016-...

nice! :D

I agree that the phrase "non-specialized" is a bit tricky. Ants are mostly non-specialized in structure (there are only a handful of forms within the colony), but individuals take on specialized behavior based on the conditions that their put in. I think stem cells could be a better metaphor.

Nobody has mentioned hooktheory.com yet. If you're interested in why some music sounds good, check it out.

I'll second this even though I only checked out the site once a bit back. I'm still quite the newb at this stuff but it got a great response on the EDM production subreddit.

This is great. I could see it replacing much of my Illustrator work.

Thanks for bringing this to the playa, Samuel. Hope to see it again next year!

Here's an implementation of the latter try operator in swift.

    extension Optional {
        func try<U>(f: (T) -> U) -> Optional<U> {
            if let unwrapped = self {
                return f(unwrapped)
            } else {
                return nil
            }
        }
    }

You can see how to use it in this gist:

https://gist.github.com/nottombrown/c6585cad9588a9dc5383

In Swift, you have to signal and guard against the nil.

In ruby, you choose whether to signal and you choose whether to guard. Here are some ruby examples that may be more clear:

Does not signal

    user = User.find_by_favorite_dinosaur("Dromiceiomimus")

Does not guard

    def print_favorite_dinosaur(user)
        p "User's favorite dinosaur is #{user.dino})"
    end

Signals and guards

    def print_favorite_dinosaur(user)
        if user
            p "User's favorite dinosaur is #{user.dino})"
        else
            p "No user. (Let's assume she likes T-rexs)"
        end
    end

    possible_user = User.find_by_favorite_dinosaur("Dromiceiomimus")

    print_favorite_dinosaur(possible_user)

Thanks, I didn't know that swift requires the optional to be guarded against.

Here's the source of try from active_support

    def try(*a, &b)
      if a.empty? && block_given?
        yield self
      else
        public_send(*a, &b) if respond_to?(a.first)
      end
    end

https://github.com/rails/rails/blob/d68419a88e424e588c2d8dec...

Should be easy to do the same in swift. Let me take a stab at it.

Author here. Let me know your thoughts, concerns, and favorite dinosaur.

Nothing to do with the article, but I think it's interesting to see someone else with the "not#{first_name}#{last_name}" pattern. I didn't know that was a common thing.

Totally trending. All of us Smiths, Browns, and Johnsons have to do something to claim our handles.

http://names.mongabay.com/most_common_surnames.htm