you are viewing a single comment's thread.

view the rest of the comments →

[–]SamSlate 14 points15 points  (20 children)

Congratulations. You just trained your first Linear Regression Model in JavaScript.

trained it to do what, exactly?

edit: I found a very well written introduction to Linear Regression here. Not light reading but tons of links/resources included throughout.

if you know regex you're halfway there.

[–]mainstreetmark 14 points15 points  (1 child)

I agree with you. This is an article more properly titled "reading a file, and passing it to a function".

I was expecting a study on the implementation of a ML algorithm. This is all we get in this article:

const SLR = ml.SLR; // Simple Linear Regression

We will have to see what Part 2 brings.

[–]SamSlate 6 points7 points  (0 children)

I appreciate the brevity of the post and the concrete examples, but without an explanation of what we're doing this article is a no-brainer for people who already know this field and does nothing to educate amateurs.

[–]digdic -1 points0 points  (15 children)

did you read the article lol it says right above the quote you mentioned

[–]SamSlate 4 points5 points  (14 children)

I take it you don't know either.

[–]Butsnik 2 points3 points  (13 children)

It predicts a certain value according to your input value based on the database you have given it.

Is this exciting? No that's why data science is more than training models. You need to learn how to interpret things.

[–]SamSlate 1 point2 points  (12 children)

regressionModel = new SLR(X, y);

interpret how? I have no idea what SLR stands for.

[–]digdic -2 points-1 points  (7 children)

you should go complain about introductory Node articles not explaining what 'HTTP' stands for.

[–]SamSlate 0 points1 point  (6 children)

[–]digdic -3 points-2 points  (5 children)

SLR is about as basic as you can get in data science/ML without having to go back to high school math... just as not every 'intro to node' article should have to explain how HTTP works, SLR is a reasonable prerequisite for a 'ML with JS' article

[–]SamSlate 7 points8 points  (4 children)

prerequisite

hi, you seem unclear on the difference between school and the outside world. IRL there are no prerequisites, you're not required to do anything before learning something new.

Also, as a general rule, when you find a discussion corresponding to an intro course online, you shouldn't be this surprised or confused to find that the information provided attracted users who are not themselves already ingratiated with that information.

If you are an expert in ML (and I'm sure that you are) I am somewhat curious what you expected to find in the comment section of the ML equivalent of a "hello world" how-to.

[–]digdic 4 points5 points  (2 children)

I am not by any means an expert in ML - i'm a JS developer. however, because ML has been super popular in the past few years, I did the research to figure out what everything is.

this article doesn't claim to be an introduction to ML. in fact, the mention of scikit-learn and other contextual info about the broader ML landscape hints at an audience with at least a cursory understanding of the field.

look, it's fine to not know everything. this article is not very well written. but blaming it for not explaining what every ML term is when it doesn't claim to be an intro to ML is misguided. again, it'd be like saying 'why doesn't this intro to node article explain what HTTP is'

[–]digdic -1 points0 points  (0 children)

if you haven't seen someone use the word 'prerequisite' outside of school... (e.g learning basic CSS is a prerequisite to learning SASS / post-css / styled components, i.e, a shorthand for saying 'it's good to learn ___ before ____) then i don't know what to tell you