Live data from Hacker News

Building a no-code toxicity classifier by talking to GitHub Copilot

surgehq.ai

1–10 of 152 posts

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#2
This is really pretty impressive. I think Copilot for these kinds of one-off analysis tasks where specific data manipulation rather than structuring abstractions makes a lot more sense. Structuring libraries or building UI requires a lot more understanding of potential users - in that case, writing the requirements is honestly the harder part.

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#3
post #2

This is really pretty impressive. I think Copilot for these kinds of one-off analysis tasks where specific data manipulation rather than structuring abstractions makes a lot more sense. Structuring libraries or building UI requires a lot more understanding of potential users - in that case, writing the requirements is honestly the harder part.

[deleted]

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#6
post #5

Notice that the comments used to generate the code via GitHub Copilot are just another very inefficient programming language.

There is nonetheless something extremely valuable about being able to write at different levels of abstraction when developing code.

Copilot lets you do that in a way that is way beyond what a normal programming language would let you do, which of course has its own, very rigid, abstractions.

For some parts of the code you'll want to dive in and write every single line in painstaking detail. For others `# give me the industry standard analysis of this dataset` is maybe enough for your purposes. And being able to have that ability, even if you think of it as just another programming language in itself, is huge.

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#7
post #5

Notice that the comments used to generate the code via GitHub Copilot are just another very inefficient programming language.

Programming languages have syntax and semantics, while text-generators are statistical. So I wouldn't call them a programming language, since "having well-defined semantics" is more fundamental than "is often used in an edit->run loop".

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#8

Impressive BUT. Who is defining toxic speech? Where is that data being taken from? This is the definition of using AI to set what the edges of “speech” should be based on potentially flawed data. This is a clown world.

> In this example, we’re using the Copilot extension for Visual Studio Code, and a free toxicity dataset that we built;

(Emphasis mine)

Following that link:

> Surge AI is a data labeling platform and workforce. Our labeling team pored over tens of thousands of social media comments to build this toxicity dataset. Each comment was then evaluated by multiple members of our team to determine its severity level.

Re: Building a no-code toxicity classifier by talking to GitHub Copilot

#9
This is a game-changer, even if it doesn't work 100% of the time. I only infrequently need to use notebooks and dataframes, I'd say once every few months. Frequently enough that I have a vague idea of what I need to do but not frequently enough that I can remember syntax.

With this, I don't need to memorize the syntax OR be bottlenecked on looking at documentation or stack overflowing the commands I need.

Post reply on HN