3 ms·
I'm hopeful AI will end up being probability/statistic's "CS", in the same way that CS relates to its mathematics. IOW, an intellectually-linked discipline tha
by ethbr1 3y ago
I'm hopeful AI will end up being probability/statistic's "CS", in the same way that CS relates to its mathematics.
IOW, an intellectually-linked discipline that drives so much revenue (and thus has so much work to be done in it) that it comprises its own field (about 75% of which is unique "applications-of-thing" problems).
- uoaei 3y agoSoftware engineering is already CS's "CS". CS is a field of study, not a role. There may be something like "AI engineering" but I can't see a way it would be much different from existing ML engineer roles. And if you do ML engineer minus specialized statistics knowledge you're just back to plain old software engineering. I don't know that this particular aspect of the "AI revolution" needs some disruptive paradigm shift.
- ethbr1 3y agoPo-tato potat-o, re: CS vs SE and role vs field. I'm hesitant to appropriate "engineer" into what we do. There are certainly people who work with code who earn that title. There are also many who don't. I do think it would be healthy for people who work with ML to separate more decisively from people who work with general purpose code. There are enough unique problems and solutions in ML that a clear community would better serve the field's maturation. As opposed to getting an endless summer of "Why don't you just" software developers fouling things up, because it's "similar".
- fragmede 3y agoAs a nascent field, "why don't you just" ends up with new, useful, applicable techniques, along with many that aren't. We don't know which is which until after the fact.