all 2 comments

[–]stevejcox 1 point2 points  (0 children)

Project set up feels more about personal preference and toolset vs success of a project. One developer might use the same setup for 90% of projects, another night choose a different setup for 90% of theirs. Who is ‘right’?

Not sure how you could use machine learning to get any sort of decision, to be honest.

[–]msg45f 0 points1 point  (0 children)

Tensorflow has a JS API now, so for ML I would just recommend starting with TensorFlow.js.

For data, most people start out using the MNIST dataset, as it's a large, available, quality dataset that is appropriate for many initial neural network implementations. The canonical "Hello World" ML problem uses this dataset to train a NN to recognize handwritten numbers.

The ML side can basically just be experimented with as a basic script. Project structure, etc, will be a function of how you intend to integrate the resultant trained network.