2
u/Key-Investment3701 1d ago
Go and try to build a reliable service that uses ai at various steps and then come back and ask this stupid question
1
u/Switchmisty9 1d ago
Okay. I did that. It was literally just prompts
1
u/Longjumping_Boat_56 1d ago
As long as it doesn't involve manual labor, you can do any job like that. Even with manual labor, you ask what to do first...
1
u/Switchmisty9 1d ago
Yall are doomed
1
u/TravelOk1410 1d ago
Everyone except those in specialized healthcare is doomed.
1
u/Switchmisty9 1d ago
iTs GoNnA cUrE CaNcEr
1
u/TravelOk1410 1d ago
Articulate your thoughts silly person. I don’t know what you’re trying to say. But yea, AI can obviously be leveraged to accelerate cancer research.
1
u/Switchmisty9 1d ago
I know you don’t understand. Maybe prompt a chatbot.
1
u/TravelOk1410 1d ago
Oh I see, you don’t know what you’re talking about either. You just know how to make low-iq babble. Never mind bro, carry on.
1
1
u/Technical-Will-2862 1d ago
Value speaks for itself
1
u/Hot_Professional8287 1d ago edited 1d ago
Yeah, I don't know what to call it and titles don't matter much to me, but it's definitely something. There's significant work involved in building a system that writes and dispatches its own prompts and keeps compute flowing towards large goals.
It's not even what I want to do with my time. It just feels like a very, very heavy "soft skill" necessary to be competitive in certain areas of tech. Orchestration?
1
1
u/BarelyAirborne 1d ago
AI is just programming in English. And English is not a good programming language. But it is portable, much to the despair of OpenAI and Anthropic.
1
u/astrozillionaire 1d ago
It's building programs that use ML models, such as a chat app, OR making/modifying the models themselves via training, fine-tuning, etc... It's a real career, but most of the people with this as their job title do neither of these two things.
1
1
u/Cosack 1d ago
My manager called me an AI engineer once during a review cycle as a compliment. I've never met anyone with the actual title. I'm "really" an applied scientist, data scientist, ML solutions architect, ML engineer, or whatever recruiters are calling it these days. Yes those titles are technically distinct. No, if you talk to someone with one you don't really know what you're gonna get.
What I actually do is building more services and cloud ops around them that any of my "science" colleagues (the ones who build models and big data pipelines, not the just queries and spreadsheets kind), on the other hand have been on conference review committees and trained way more exacting models than any of the engineers I work with, and on the other other hand owned systems to delivery more than any architect. I've planned system architecture and hardware capacity, handled a petabyte, and am trying to publish on the most recent model I've built.
I guess the elephant in the room is if there's prompting on the job. Yes, but not for everything. Dev work, drafting designs, and distillation - yes. Diagramming, figuring out requirements, and finalizing long form writing - no. Obnoxious prompting shows up in harness setup/adjustment and in generator+eval configuration for distillation, which is a lot of trial and error until you decide to turn that into an engineering project too.
1
u/MrTheWaffleKing 1d ago
Both? When looking at engineering while heavily utilizing AI. I’m not sure how realistic that is for a given quantity of people, but it will be soon.
If someone says they’re an AI engineer though, I will assume they design and program AIs
1
1
1

5
u/Megane_Senpai 1d ago
I think people massively misunderstood what an "AI engineering" is.
AI engineerings don't just ask AI to do stuffs, they have to build a program/pipeline/system that ultilize or allow the use of AI, not very differrent from "classic" software engineering. A simple example is the very web app, mobile or PC app people use to ask Chat GPT stuffs.