←back to thread

The barriers to AI engineering are crumbling fast

(blog.helix.ml)
250 points lewq | 2 comments | 14 Nov 24 14:56 UTC | HN request time: 0.399s | source
Show context
JSDevOps ◴[14 Nov 24 15:05 UTC] No.42136819[source]▶
Is anyone instantly suspicious when they introduce themselves these days an "AI Developer"
replies(8): >>42136909 #>>42136984 #>>42137147 #>>42137171 #>>42137380 #>>42137938 #>>42137950 #>>42140294 #
master-lincoln ◴[14 Nov 24 16:38 UTC] No.42137938[source]▶
I would interpret that as somebody working on ML algorithms and architectures, not somebody developing a product that uses some form of AI at runtime...
replies(2): >>42138131 #>>42138404 #
spmurrayzzz ◴[14 Nov 24 16:54 UTC] No.42138131[source]▶
I haven't seen this sort of work called AI Developer yet, but I may have missed the trend shift. Isn't the convention for this still to use the title of Machine Learning Engineer (MLE)?
replies(1): >>42138269 #
1. master-lincoln ◴[14 Nov 24 17:04 UTC] No.42138269[source]▶
There is another thread here that seems to confirm it's me who has missed a trend shift. I didn't know this term had a special meaning. I just followed the thought that an x-developer is somebody developing x.
replies(1): >>42143862 #
2. throwaway290 ◴[15 Nov 24 04:03 UTC] No.42143862[source]▶
They use "AI" like they use "Python" in "Python developer" or "Web" in "Web developer".