←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.401s | 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 #
pjmlp ◴[14 Nov 24 15:32 UTC] No.42137171[source]▶
Yes, just like "Data Engineer" for knowing how to use Tableau or doing OLAP queries.
replies(5): >>42137828 #>>42137904 #>>42137975 #>>42139088 #>>42139089 #
Ldragon27 ◴[14 Nov 24 16:35 UTC] No.42137904[source]▶
Are you saying that true Data Engineers typically do more than just use Tableau or run OLAP queries, or do you see the title 'Data Engineer' itself as a bit of a red flag these days? I’m pretty early in my career and was leaning toward Data Engineering, but hearing stuff like this makes me wonder if going for SWE might be smarter.
replies(2): >>42137954 #>>42138306 #
hobs ◴[14 Nov 24 16:40 UTC] No.42137954[source]▶
The better paying role is a Backend SWE (usually). A really a good data engineer is just a Backend SWE who has specific experience.

A bad one is a SQL analyst whose been promoted too much.

replies(1): >>42139112 #
1. bubbleRefuge ◴[14 Nov 24 18:03 UTC] No.42139112[source]▶
as as data engieer/data architect , agreed. there are allot of 'tools' experts who are data engineers but can't code a lick.
replies(1): >>42139859 #
2. hobs ◴[14 Nov 24 19:01 UTC] No.42139859[source]▶
Yep, that's where I am at - the amount of times people have talked to me about the most recent podcast where they've heard how a new tool will solve all their problems and really its some samey mix of CDC and bad python+sql is... a lot.

I think there's not a ton of political palatability for realizing most of their projects are like one API and a sane use of some SQL away.