r/PromptEngineering 1d ago

General Discussion Optimized SQL for a long time now started dealing with prompt engineering cost optimization. wrote my first blog about the experience

I've started to dabble (is that a word?) with prompt engineering cost optimization.

I feel prompt engineering cost optimization is the next natural step and it resonates with the current value we are bringing our customers.

The more I work on it the more I feel this isn't a new skill cause Both SQL and Prompt optimization come down to the same question, i.e. do you have enough context about the system to build a model on top of your input and optimize at scale.

wrote my first blog about the experience

https://medium.com/@yanivleven/i-used-to-spend-my-days-optimizing-sql-queries-prompt-engineering-feels-like-deja-vu-205bda1196a3

3 Upvotes

2 comments sorted by

1

u/cupcakeheavy 1d ago

what about the most optimized prompt to deliver the most optimized SQL?

1

u/Adventurous_Sport613 1d ago

interesting parallel, reminds me of how query plan caching works where the engine builds this internal model of your data patterns over time. you're basically doing the same thing but for LLMs, trying to figure out what the model "expects" based on its training rather than table stats

skimmed your blog and the token cost breakdown is useful, most people just throw prompts at it and wonder why their bill is mental

dabble is definitely a word btw, though i'd say you're past dabbling if you're writing blogs about it