Sahin Boydas
Random theme
Select theme
Back to all articles

10 Lessons I Learned About Prompt Engineering After Spending the last 2 years

I went deep on Prompt Engineering, investing the last 2 years to master it. These are the 10 most critical, non-obvious lessons that will accelerate your learning curve and save you from costly mistakes.

2024-09-036 min read687 words

I wanted to share my perspective on this. I went deep on Prompt Engineering, investing the last 2 years to master it. These are the 10 most critical, non-obvious lessons that will accelerate your learning curve and save you from costly mistakes.

The Framework That Actually Works

Here is a simple framework for evaluating prompt engineering. It's not complicated, but it requires discipline.

Step 1: the market doesn't care about your roadmap

This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.

Step 2: the best solutions are often the simplest ones

Once you have the foundation right, this becomes much easier. I've watched founders struggle with this for months when the answer was staring them in the face.

Step 3: Iterate relentlessly

Nothing works perfectly the first time. The companies that get prompt engineering right treat it as an ongoing process, not a one-time project.

Why Most Approaches Fail

Many common approaches to prompt engineering are flawed at the root.

The root cause is usually one of three things:

Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.

Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.

Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.

What I've Learned From 20 Companies

Across 234 angel investments, including Anthropic, a few patterns in prompt engineering come up again and again.

The founders who handle prompt engineering well understand that the market doesn't care about your roadmap.

Lessons From the Trenches

I want to share a few specific lessons I've picked up over the years. These aren't theoretical. They come from real companies, real failures, and real successes.

Lesson 1: The best time to start thinking about prompt engineering was yesterday. The second best time is now. Don't wait until you have the perfect plan.

Lesson 2: Hire for attitude, train for skill. The best people at prompt engineering are rarely the most technically gifted. They are the most curious and persistent.

Lesson 3: Your competitors are probably getting this wrong too. That's your opportunity. While everyone else is following the same playbook, you can zig when they zag.

This connects to broader themes around AI design tools, AI video, Stable Diffusion, image generation, AI art that I've been thinking about a lot lately.

Final Thoughts

There are no shortcuts in prompt engineering, but there are smarter paths.

The strongest teams treat prompt engineering as a competitive advantage, not a checkbox. They invest in it early, measure it obsessively, and never stop improving.

If you're just getting started with prompt engineering, don't be intimidated. Everyone starts somewhere. The key is to start with the right mindset and the right framework, and then execute like your company depends on it. Because it probably does.

FAQ

Frequently Asked Questions

Q:How were these items selected?

Each item on this list comes from direct experience, either from building my own companies or from patterns I've observed across the 234 startups I've invested in. I prioritize practical, actionable items over theoretical concepts.

Q:Can I implement all of these at once?

I'd strongly recommend against it. Pick the 2-3 items that resonate most with your current situation and focus there. Trying to do everything simultaneously is a recipe for doing nothing well.

Q:Which item on this list has the highest impact?

It depends on your stage and context, but in my experience, the items near the top of the list tend to have the broadest applicability. That said, sometimes the less obvious items create the biggest breakthroughs for specific situations.

Q:How do I know which items apply to my situation?

Start by honestly assessing where your biggest bottleneck is right now. The items that address that specific constraint will give you the highest return on your time and energy.

Written by

Sahin Boydas

Serial entrepreneur, #1 angel investor, author of Becoming Top 1%

Get Sahin's Weekly Insights

Join 10,000+ founders and investors. One email per week with actionable advice on startups, investing, and building in the AI era.

No spam. Unsubscribe anytime.