the definition(s) and use(s) of "prompt engineering" will continue to evolve, shapeshift, fragment and become even more _multiple_ and context-dependent. But still a useful handle?

[highlighting added]

##### [\@yoavgo](https://twitter.com/yoavgo/status/1674446687308218370)

- i didnt look in details yet but this is roughly what i'd imagine a chaining tool api to look like (ahm langchain, ahm).

- its interesting how the definition of "prompt engineering" evolves and shapeshifts all the time.

##### [\@jxnlco](https://twitter.com/jxnlco/status/1674373377702653955)

Why prompt engineer \@openai with strings?

Don't even make it string, or a dag, make it a pipeline.

Single level of abstraction:

Tool and Prompt and Context and Technique? its the same thing, it a description of what I want.

The code is the prompt. None of this shit
"\{\}\{\{\}\} \{\}\}".format\{"\{\}\{\}"

PR in the next tweet.

![Tweet from @jxnlco](https://hypandra.b-cdn.net/koureia/danielsgriffin/posts/weblinks/2023/06/29/prompt-engineering-evolving-and-shapeshifting/tweet1674373377702653955.image-2026-09-20T13-50-55-a844c007.jpeg)

Tweet [Jun 29, 2023](https://twitter.com/jxnlco/status/1674373377702653955)

Tweet [Jun 29, 2023](https://twitter.com/yoavgo/status/1674446687308218370)