First: Who the hell am I

@lizTheDeveloper

You may remember me from such startups as:

Also I designed and implemented the system that protects your debit card

How did I get here & what does that have to do with comment classification?

Back to 2008...

Bet you never thought you'd be nostalgic for 2008

Figuring out the problem type from free-form entry

"The unit exhibits cracks along it's hinges, and the screen don't work"

"Customer laptop does not start"

"Water damage, but the computer turns on, customer is complaining about viruses"

"network card not working, reinstalled OS didn't help at all"

Naive Feature Extraction

Text	Classifications
"The unit exhibits cracks along it's hinges, and the screen don't work"	bezel damage, screen or video trouble
"Customer laptop does not start"	won't start
" Water damage, but the computer turns on, customer is complaining about viruses"	water damage, won't start, viruses
" network card not working, reinstalled OS didn't help at all"	network, reinstall OS

This script allowed us to allocate resources more efficiently, saving thousands of dollars

(not enough thousands to save Circuit City tho 😒)

Simple Scripts Save 🤑🤑🤑

It doesn't always need to be perfectly accurate

Comment Classification @ Enki

"Small typo: input giveN"

"The question answer is wrong"

"Syntax is won't please correct"

"The answer should be 2+3, shouldn't it?"

Insight probably needs maintenance:

"This is a dense lesson"

"As someone who didn't know what a generator is, I felt this insight failed to bring a definition. It already started telling me that is substitute something else. I felt lost."

Insight may be hard to understand:

I think the explanation is confuse and misleading. Read the link with long but correct explanation.

Insight may need to be reviewed

"wow, I SO did not get that and didn't even after seeing the correct answer! This was a blow to the ego and I am not sure why. Maybe I am trying to learn too many different things all at once and I am having trouble (a lot of trouble, apparently) keeping them all straight."

"okay, that I completely understood after the fact and I do understand this. I was distracted and was not paying attention and so I made a stupid mistake. I am annoyed, but I don't feel bad about this one."

#notallcomments

"Whilst this is a perfectly reasonable python question, it has absolutely nothing to do with the pdb module. A more relevant question would be good. This question belongs somewhere else, to do with basic language syntax."

(are simply classified)

I keep getting syntax errors, I am typing the "indent" , is this not needed? or am I not doing this correctly?

does the "indent" in the example code just to show where it should* be indented or is there a reason it is there (otherwise it seems like I am doing it correctly)

Small teams need to prioritize work really efficiently