←back to thread

The barriers to AI engineering are crumbling fast

(blog.helix.ml)
250 points lewq | 4 comments | 14 Nov 24 14:56 UTC | HN request time: 0s | 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 #
JohnFen ◴[14 Nov 24 17:13 UTC] No.42138404[source]▶
I work on such a team, and we don't refer to ourselves as "AI engineers". We're devs working on developing deep learning systems (but not genAI).
replies(2): >>42139765 #>>42140655 #
1. swyx ◴[14 Nov 24 18:54 UTC] No.42139765[source]▶
correct - but "developing a product that uses some form of AI at runtime" is a job that people do and the community has consolidated around "AI engineer" as shorthand https://www.latent.space/p/ai-engineer

i argue that its useful to have these shorthands to quickly understand what people do. its not so nice to just be default suspicious at a perhaps lower-technical-difficulty job that nevertheless a lot of comapnies want and a lot of people do

replies(3): >>42140311 #>>42140953 #>>42143882 #
2. dr_dshiv ◴[14 Nov 24 19:42 UTC] No.42140311[source]▶
Difficulty ≠ Value

But we think it is, due to our learned industrious—which is the opposite of learned helplessness. We associate difficulty with reward. And we feel discomfort when really valuable things become very easy. Strange times.

3. ◴[14 Nov 24 20:38 UTC] No.42140953[source]▶
4. throwaway290 ◴[15 Nov 24 04:06 UTC] No.42143882[source]▶
Why is it lower difficulty? If didn't get that impression from the article