Should working as a machine learning engineer feel like a lot of trial and error?

A work project for me usually goes something like:

Percentage of TimeTask
10Researching problem
20Implementing solution
60Changing things via trial and error to get better results
10Final testing

The trial and error isn't random. I usually look at my results and see what I can do to improve accuracy, but the changes I make in my code don't always work out as expected, then I have to try other methods to bump up the accuracy of my results.

It might be helpful to mention most of the work I'm doing involves NLP, specifically information extraction from raw text data.

This is my first internship, so I wanna know if a job with high amounts of NLP is usually like this, or if I just really suck at predicting outcomes. It's hard when I'm going to multiple files, each with differences is formatting (some information is in a table, others are hidden in text, some important headers only have the first word capitalized making it difficult to distinguish from other text, etc)

It's frustrating when I usually have to try so many different solutions to a problem to see which ones are best, or more generalized.

Posted Jul 12, 2017, 11:36 PM UTC · edited

310
dls2016•

The trial and error isn't random. I usually look at my results and see what I can do to improve accuracy, but the changes I make in my code don't always work out as expected, then I have to try other methods to bump up the accuracy of my results.

Sounds like (a portion of) the scientific method to me.

if I just really suck at predicting outcomes

How does one build intuition without experimentation?

It's frustrating when I usually have to try so many different solutions to a problem to see which ones are best, or more generalized.

Keep plugging away, taking notes, recording results. You will improve.

9
QuoteMaker_OPMachine Learning Intern•

Thanks man, I needed to hear that

2
sonnytronSDE•

Should working as a machine learning engineer feel like a lot of trial and error?

FTFY.
And yes, it should. Anyone who expects perfection isn't realistic and doing work you've mastered is soul crushing.

5
QuoteMaker_OPMachine Learning Intern•

I don't get a sense of trial and error with other fields of programming, like web/Android development. Sure there are a lot of bugs that usually come with creating a new feature, but fixing them (while still a source of frustration) doesn't feel like trial and error.

1
sonnytronSDE•

Even if you built the same types of things, you'd have trial and error with structure and logic. I am building a CRUD application right now in Kotlin and even though almost everything about this application is stuff that I've done more than a few times before, I find myself going through trial and error to get the logic to work the way I want it to.
Please don't insult fields you think are "lesser" by saying that they're not trial and error.
You're an intern, you have a long way to go. This entire industry is essentially "trial and error".

3
QuoteMaker_OPMachine Learning Intern•

Sorry, I didn't mean to insult Android development at all! Thank you for your response

1
amdds•

You're not wrong though. Yes, every kind of programming involves trial and error. But that's because the term "trial and error" is overloaded: They aren't all the same kind of trial and error. It's qualitatively different, and the distinction you're sensing is real.

It's like saying biology and physics are both about "figuring out nature." Yes, the phrase applies to both. But the challenges, methods, and required skills in one are different than they are in the other. Neither is "lesser," and I didn't think you were trying to imply one was.

1
throwaway20170226•

This is quite normal. However, make sure you discuss your results with your manager / mentor / other senior engineers and really understand why your trials didn't give you desired outcome. As an example, make sure you don't go down the rabbit-hole of parameter tuning when your loss function is sub-optimal for the problem you are trying to solve.

2
[deleted]•

[deleted]

1
thoughandtho•

I work at an organization with post-docs, grad students, and post bachs doing research. Within our ML team, I'd say that this is fairly common. I get that it can be frustrating, but as others have stated: you'll get better.

ML can be tricky and there are a lot of things to learn. There is certainly the aspect of "am I using the right tool for the job?" Just keep at it and try to learn as much as possible. It's a very cool field imo.

1
SemaphoreBingo•

If 50% or more of your time isn't spent cleaning data, you're in good shape.

1