Skip to content

armgit / dspy

Public Imported from GitHub
0

DSPy: The framework for programming—not prompting—language models

Python

Update README.md

Omar Khattabe394464e0120
diff --git a/README.md b/README.md
index c4b073065..9a57906f1 100644
--- a/README.md
+++ b/README.md
@@ -15,9 +15,9 @@
----
-**DSPy** is a framework for developing **LM pipelines** and automatically optimizing their quality and cost. LMs are sensitive to prompts. This becomes a serious challenge in multi-stage pipelines, where different prompts (or finetunes) have to compose effectively. To use LMs to build a complex system without DSPy, you generally have to: (1) break the problem down into steps, (2) prompt your LM well until each step works well in isolation, (3) tweak the steps to work well together now, (4) generate synthetic data to tune each step, and (5) use that data to finetune smaller LMs to cut costs.
+**DSPy is a framework for developing LM pipelines and automatically optimizing their quality and cost.** LMs are sensitive to prompts. This becomes a serious challenge in multi-stage pipelines, where different prompts (or finetunes) have to compose effectively. To use LMs to build a complex system without DSPy, you generally have to: (1) break the problem down into steps, (2) prompt your LM well until each step works well in isolation, (3) tweak the steps to work well together now, (4) generate synthetic data to tune each step, and (5) use that data to finetune smaller LMs to cut costs.
-Composing these into the right pipelines is a hard and messy process: every time you change your pipeline, your LM, or your data, all prompts may need to change! To make this all more systematic, **DSPy** does two things. First, it separates the flow of your program (`modules`) from the parameters (LM prompts and weights) of each step. Second, **DSPy** introduces new `optimizers`, which are LM-driven algorithms that can craft and tune the parameters of your pipeline, given a `metric` you want to maximize.
+Composing these into the right pipelines is a hard and messy process: every time you change your pipeline, your LM, or your data, all prompts may need to change. To make this more systematic, **DSPy** does two things. First, it separates the flow of your program (`modules`) from the parameters (LM prompts and weights) of each step. Second, **DSPy** introduces new `optimizers`, which are LM-driven algorithms that can craft and tune the parameters of your pipeline, given a `metric` you want to maximize.
**DSPy** can routinely teach powerful models like `GPT-3.5` or `GPT-4` and local models like `T5-base` or `Llama2-13b` to be much more reliable (higher quality and/or avoiding specific failure patterns) at tasks. **DSPy** will compile the _same program_ into different few-shot prompts and/or finetunes for each LM.