Live data from Hacker News

Speech and Language Processing, 3rd ed. draft (2017)

web.stanford.edu

1–10 of 41 posts

Re: Speech and Language Processing, 3rd ed. draft (2017)

#2
Often this stuff is used for surveillance. If you choose to study this area, please be careful how you apply your knowledge. There are plenty of positive ways to use it: contributing content classification systems to sci-hub or libgen, building tools for the disabled, automating multilingual visual design aesthetics with computational linguistics and machine learning...

Re: Speech and Language Processing, 3rd ed. draft (2017)

#3
On the slim chance that someone here wants to re-implement the unmodified Kneser-Ney algorithm[0], the presentation of it by the book does not account for unknown tokens in the query not in the vocabulary. I extended the recurrence to its natural closure including unknown tokens here [https://github.com/jhanschoo/HMMTagger/blob/master/readme.pd...]. A straightforward task, but it might take you an hour or two (probably more) otherwise to obtain it and prove its correctness, seeing as I couldn't find an extension in a Google search nor is it described in the original paper as well. I believe that it would likewise be straightforward to extend this to modified Kneser-Ney as well.

[0]: The modification of using multiple discount values due to Chen & Goodman is regarded as a more well-behaved smoothing, and more popular today.

Re: Speech and Language Processing, 3rd ed. draft (2017)

#4

Often this stuff is used for surveillance. If you choose to study this area, please be careful how you apply your knowledge. There are plenty of positive ways to use it: contributing content classification systems to sci-hub or libgen, building tools for the disabled, automating multilingual visual design aesthetics with computational linguistics and machine learning...

Whilst I understand the concern but just Internet is now for control and tracking (chi-na is more obvious but post someone we all know better), we cannot stop the wheel.

Not knowing is even worst.

Re: Speech and Language Processing, 3rd ed. draft (2017)

#5
post #4

Often this stuff is used for surveillance. If you choose to study this area, please be careful how you apply your knowledge. There are plenty of positive ways to use it: contributing content classification systems to sci-hub or libgen, building tools for the disabled, automating multilingual visual design aesthetics with computational linguistics and machine learning...

Whilst I understand the concern but just Internet is now for control and tracking (chi-na is more obvious but post someone we all know better), we cannot stop the wheel. Not knowing is even worst.

We need an equivalent of the hippocratic oath for software engineers: I swear by Hephaestus, the ugly god of crafts, that I shall not use my skills for controlling and tracking ...

Re: Speech and Language Processing, 3rd ed. draft (2017)

#6
post #5
post #4

Earlier quoted context omitted.

Whilst I understand the concern but just Internet is now for control and tracking (chi-na is more obvious but post someone we all know better), we cannot stop the wheel. Not knowing is even worst.

We need an equivalent of the hippocratic oath for software engineers: I swear by Hephaestus, the ugly god of crafts, that I shall not use my skills for controlling and tracking ...

Great, these who want to build these things will simply hire people who don't subscribe to this oath ... And now the organization will be populated by a whole tribe of people who have no qualms about doing this -- does that sound like something that will make things better?

Aside: the book looked interesting. Skimmed it, beautiful typesetting, not gratuitously mathematical, looked readable -- I may be wrong, but it's just a exercise of adding awareness of it's existence to me.

Re: Speech and Language Processing, 3rd ed. draft (2017)

#7

Often this stuff is used for surveillance. If you choose to study this area, please be careful how you apply your knowledge. There are plenty of positive ways to use it: contributing content classification systems to sci-hub or libgen, building tools for the disabled, automating multilingual visual design aesthetics with computational linguistics and machine learning...

Fast programming equals surveilance. Programs must be asserted at some point in op cycle. The point of privacy is not about capturing software device neither parsing software device, it is when to use an external(internet) service.

Re: Speech and Language Processing, 3rd ed. draft (2017)

#8
post #6
post #5

Earlier quoted context omitted.

We need an equivalent of the hippocratic oath for software engineers: I swear by Hephaestus, the ugly god of crafts, that I shall not use my skills for controlling and tracking ...

Great, these who want to build these things will simply hire people who don't subscribe to this oath ... And now the organization will be populated by a whole tribe of people who have no qualms about doing this -- does that sound like something that will make things better? Aside: the book looked interesting. Skimmed it, beautiful typesetting, not gratuitously mathematical, looked readable -- I may be wrong, but it's…

> Great, these who want to build these things will simply hire people who don't subscribe to this oath ...

How many doctors are willing to give up their title to do unethical stuff?

An ethical code will change people's perception, and that's a big thing. It will morph the perception of Google and Facebook from cool tech companies into dark places where no decent people want to work; unless of course these companies are willing to change. And there will be a huge effect on politics, other businesses, and media.

Re: Speech and Language Processing, 3rd ed. draft (2017)

#9
post #5
post #4

Earlier quoted context omitted.

Whilst I understand the concern but just Internet is now for control and tracking (chi-na is more obvious but post someone we all know better), we cannot stop the wheel. Not knowing is even worst.

We need an equivalent of the hippocratic oath for software engineers: I swear by Hephaestus, the ugly god of crafts, that I shall not use my skills for controlling and tracking ...

Early in my career (it began after a discussion in a tutorial during my undergrad) I made a choice to never to use my engineering skills to build weapons. I don't believe its a morally justifiable choice in this century. It's not like I have been forced to starve as a result but it did reduce a few opportunities.
Post reply on HN