the_sisko

@the_sisko@startrek.website

• ⁨Comment⁩ on ⁨this AI thing⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  The closest analogy is specific tech skills, like say DBs, for a small firm its just something one backend dude knows decently, at a large firm there are several DBAs and they help teams tackle complex DB questions. Same with say Search, first Solr and nowadays Elastic.

  Yeah I mean I guess we’re saying the same thing then :)

  I don’t think prompt engineering could be somebody’s only job, just a skill they bring to the job, like the examples you give. In those cases, they’d still need to be a good DBA, or whatever the specific role is. They’re a DBA who knows prompt engineering, etc.

• ⁨Comment⁩ on ⁨What happens of you use the gas from the exhaust pipe to inflate a tire?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I have an air compressor which is powered by the 12V DC outlet in a car. They are quite cost effective and easy to buy. I use it all the time to refill my tires. Much better than some odd exhaust pressure solution.

• ⁨Comment⁩ on ⁨this AI thing⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’m totally willing to accept “the world is changing and new skills are necessary” but at the same time, are a prompt engineer’s skills transferrable across subject domains?

  It feels to me like “prompt engineering” skills are just skills to compliment the expertise you already have. Like the skill of Google searching. Or learning to use a word processor. These are skills necessary in the world today, but almost nobody’s job is exclusively to Google, or use a word processor. In reality, you need to get something done with your tool, and you need to know shit about the domain you’re applying that tool to. You can be an excellent prompt engineer, and I guess an LLM will allow you to BS really well, but subject matter experts will see through the BS.

  I know I’m not really strongly disagreeing, but I’m just pushing back on the idea of prompt engineer as a job (without any other expertise).