While I'm technical, I don't refer to myself as a software engineer, nor am I ostentatious enough to call myself a social engineer. Many titles are meaningless, but I don't consider the title of engineer as trivial.
There's a Reddit thread (2) from a few years ago where writer Gwern claims to be the origin of the term prompt programing/prompt engineering and has a verbose defense. I think his argument is reasonable and well written, but I'm not sure I'm sold.
I've read several HN threads (3, 4) and I've generally come to the conclusion that you can do engineering without being an engineer, or at least calling yourself one.
What do you think? Would you suggest an alternative?
1. https://qz.com/work/1435689/the-origins-of-the-job-title-data-scientist
2. https://www.reddit.com/r/GPT3/comments/m177n2/the_problem_with_prompt_engineering/
3. https://news.ycombinator.com/item?id=25823907
4. https://news.ycombinator.com/item?id=33206677
I feel that any engineering endeavor needs to have at least some understanding of the underlying mechanics of what’s going on, but since a lot of obvious prompts “just work” the task isn’t mature enough to deserve any special designation.
We could probably just call it ‘prompting’ or ‘prompt testing/hacking’ and not lose any of the meaning.