3 ms·
Yup. As someone who is in a junior position in the field - I'm torn between, on one hand, riding the wave so to speak and taking advantage of all the buzzwords
by altairiumblue 8y ago
Yup. As someone who is in a junior position in the field - I'm torn between, on one hand, riding the wave so to speak and taking advantage of all the buzzwords that I can put on my resume (which is fine with me because I can back them up), and on the other hand avoiding association with a certain type of person/career path that might turn out be just hot air in a couple of years.
So if I can actually write decent code, have solid understanding of software development principles, have studied math and statistics from the ground up to an advanced level, am familiar with relevant research - then do I really want to call myself a data scientist (or ML-something) just because it might improve my job/salary prospects, or do I want to stay away from it because everyone who takes a one-week course on Udemy calls themselves a data scientist without being able to back it up with actual skills?
- fock 8y agoHaving been subject to a lot of buzzword-blarers over the last term I'd say that you just tell everybody that you are working the foundations of what all the other people are doing if they ask, what makes you special. If you can back it up, why not ride the wave. I would refrain from putting the sticker on everything though. I als made a turnaround and now spin everything I do which takes time (basically automating my research and data-vis) as building blocks for (gradschool) ML-based research.