Comments

You must log in or register to comment.

TheCloudTamer t1_iuloar3 wrote

EE to ML guy here. Copying some advice I sent someone else. It’s not exactly what you asked, but might be helpful.

Spend some time at a low level: use only Numpy to write a NN including backdrop. It’s feasible to do this for reasonably complex nets. For example the DRAW network by Alex Graves. You want to read the first 1/4 of David MacKay’s book. Watch the NYU DL video series and try the notebooks. Do the same the UvA I think that reading lots of new papers is a bad idea, especially as people create elaborate explanations for things. Instead, find some people to follow on GitHub who are coding with the latest ideas. Having said that, there are quite a few ppl who you want to read/listen their every word (Yann LeCun comes to mind). Listen to Andrej Karpathy to see what DL looks like in production. Don’t shy away from working on core basics like linear algebra.

2

qtqtc t1_iulvko6 wrote

As far I expierenced it, it gets really boring at some point, because some predictions feeling kinda useless. Or you need a f-load of parameters to produce an "okay" result. And at some point, you wish you could debug a trained model.

Most bosses or companies don't know, what ML is really doing. They believe we can put some random data inside the model and after that, the output gonna be a gamechanger.

​

I'm doing a lot of automation and optimizing processes. My first boss wanted, to implement "some AI" in our process. I told him, it makes no sense to train a model, if our process is already stright forward and deterministic.

He wanted it anways, so I added a portion sarcasm to it: "Maybe in a private Blockchain with Kubernetes?"
He was all in.

So I guitted this job after a few months.

​

But here's my opinion/suggestion:

If you love working as ML-engineer -> go for it. It's still hypetech and companies throwing money at it. (Till the next "AI" winter)

But learn some programming skills for being a developer at one day -> developers are higly needed! And this won't change over the next decades.

1

fhadley t1_iupdm7l wrote

Replying to 1percentof2 (#416,505)

Writing a deep net in numpy 10 years ago continues to prove to be one of the most valuable personal development tasks I've ever taken on. It's a lot, it's totally unnecessary, but dang does it get you learned up good. For a minute there in the beginning of my career, whenever I tried a new model/algorithm, I wouldn't use it for anything serious until after I'd implemented from "scratch" (with numpy, so not technically "scratch," but you get the idea). This was an insane amount of overhead and tons of extra work that would make zero sense for a person who's well into their career. But again gosh dang did it get things to stick.

ETA: I occasionally wish that instead of diving so deep on methods and their details, I'd spent more time building my math skills. I can keep up with most ML math, but theory papers go over my head, and I not infrequently find myself wishing I had deeper linear algebra knowledge.

1