Machine learning isn't Kaggle competitions
1–10 of 24 posts
Re: Machine learning isn't Kaggle competitions
#2Re: Machine learning isn't Kaggle competitions
#3What does HN think of doing this?
Re: Machine learning isn't Kaggle competitions
#4I'm selecting my final year (undergrad) project in the next couple of weeks. One of my professors posted a project that will simply be entering a competition on Kaggle. I don't know much about machine learning yet and I thought that this would be a great way to pick up something I've always been interested in. What does HN think of doing this?
Even the data-cleaning that the author claims is missing from Kaggle competitions, is not really missing, it's just Kaggle have made your data cleaning much simpler.
The main advice I would give is to find a problem where you can get an understanding of the data, i.e. not just treat it like a black box.
Re: Machine learning isn't Kaggle competitions
#5Re: Machine learning isn't Kaggle competitions
#6The exception is those fields that have physical data, like computer vision or speech recognition. In those fields, the actual model matters a lot more.
I think every job has this tendency, where the public focus on the most exciting and interesting part, and ignore the mundane but also extremely important parts.
And on the matter of skill/ability, in spite of not being a Kaggle winner, the author couldn't do their job without a good understanding of machine learning models. To do machine learning in practice, you must know both the software development/systems side and the maths/stats/ML side.
Re: Machine learning isn't Kaggle competitions
#7Re: Machine learning isn't Kaggle competitions
#8Re: Machine learning isn't Kaggle competitions
#9Model making is, imo, the fun part of the process, but by far from what actually needs to be done.
That being said, kaggle is a great platform to learn on.
There is a lot of value in understanding how to train a model, but it's only as valuable as understanding how to take data from disparate sources, cleaning and normalizing it, doing some EDA, and then understanding AFTER all that if you need a model to achieve your goals.