News for hackers. Stuff that matters.
Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by jessaustin on Thursday April 19, 2018 @09:08PM (#16881436)
I didn't think I knew anything about ML, yet I seem to have passed all three tests... b^)
Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by edraferi on Thursday April 19, 2018 @09:38PM (#16881538)
If you know linear algebra, machine learning is not much further to go. You can understand pretty much all the models by looking under the hood at the math.

At that point it’s just experience to learn the rules of thumb that guide practical implementations.

Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by vvanders on Friday April 20, 2018 @12:08AM (#16882093)
That was my experience building a simple morse code decoder. Actually spent more time fighting the spectograph resolution than the ML part.

I also learned real quick that I don't want to do ML. It's all about data generation/sanitation/management which just doesn't click for me.

Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by killjoywashere on Thursday April 19, 2018 @09:44PM (#16881560)
But, grasshopper, you have not passed the third test. Where is your question?
Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by jessaustin on Friday April 20, 2018 @12:41AM (#16882190)
Haha. I guess if I had to ask any question about python, it would be, "why on earth did they do that ridiculous unicode thing in version 3?" Most builtins should use bytes, and the few that can't should just use bytes annotated with an encoding.
Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by PeterisP on Friday April 20, 2018 @02:17AM (#16882534)
Most builtins can't use bytes instead of string safely for all data, and the problem is that it propagates - in Python 2 you often have the case that library A uses library B that uses a builtin that treats a piece of text like a string of bytes, and so you can't use library A because it will give you broken results in certain conditions. We've spent time updating some third party open source libraries to support python 3, and that was well worth the time to avoid the waste of programmer time that'd come from working in python 2 due to lack of sane handling of unicode strings; and if you're working with user-facing software (as opposed to, say, scripts for system administration or physics calculations), pretty much every string you encounter nowadays is unicode string. Names of people, names of files, contents of files, results of http requests, results of database requests - all of those can be treated as streams of bytes only if you treat them as a single atomic token and don't look inside that stream in any way whatsoever. As soon as you make the first index operation, substring or split, you can't treat them as bytes anymore safely.

However, you can simply think of it as syntactic sugar that manages the encoding annotations in the default case. Where is it creating problems for you? Is it some performance hit or something else?

Re:A.I. Researchers Are Making More Than $1M, Even at a Nonp... by madhadron on Friday April 20, 2018 @02:05AM (#16882484)
There speaks someone who hasn't spent significant time working with multilingual texts.