Pinned Tweet
Last year, I made a meme that very few understood.
But I feel my fellow #RWRI participants will appreciate it 😅
Building LLM systems felt more like praying to the AI gods than engineering.
But all that changed when I learned about eval-driven development.
This Thursday (9/25) at 11AM CST, I’ll be sitting down with @HamelHusain for a live podcast to discuss evaluation frameworks and failure analysis in LLM systems.
We’ll cover:
- What's an AI eval—and why it matters?
- How to run error analysis for open-ended tasks
- Should you rely on LLM judges or code-based evals?
- How to debug and improve your system once you have evals in place
... and more
Join us live and ask Hamel your AI eval questions!
👉 Register here: luma.com/7izvlf3r
Shaw Talebi retweeted
Just watched @ShawhinT YT video on "ML Foundations for AI Engineers".
All the concepts are so beautifully explained with various examples. A must watch.
Building software on top of (unpredictable) LLMs can feel more like praying to the ML gods than engineering 🙏
But it doesn’t have to be that way…
In a recent blog post, I showed how error analysis resolves the guesswork by giving us a systematic way to identify and improve the most significant failures from an LLM system.
👉 Check it out here: medium.com/@shawhin/how-to-i…
--
Shout out to @HamelHusain and @sh_reya, who showed me the light when it comes to LLM error analysis in their fantastic AI evals course :)
I just received 3 baguettes from Sathish on @buymeacoffee! buymeacoffee.com/shawhint/c/…
Shaw Talebi retweeted
Over the last 2 yrs, I've helped 35+ companies improve their AI products.
I distilled my approach into this guide, which covers error analysis, synthetic data, eval-human alignment, involving domain experts, optimizing # of experiments & more (1/5)
hamel.dev/blog/posts/field-g…
4) You’re done when you deploy
As a data scientist, once the project was built and deployed, I could relax.
As an entrepreneur, this is only the start. After deploying, I need to let people know about it and (hopefully) pay for it.
3) Building (rather than buying) just because I can
Before, I had a tendency to avoid paid software tools/services when I felt I could implement them myself.
Now, I bias toward paying for solutions that can help me move faster.
2) Building for “prod” with 0 users
When working at an established company, ML projects might immediately impact thousands of customers and millions of dollars, so you have to build for scale from the start.
However, as an entrepreneur, you’re more often seeking validation, which means speed and iteration are much more important than scalability.
1) Progress = learning more tech skills
Going from a good to a great coder won’t move the needle as much as going from bad to mediocre in key non-tech skills (i.e., sales, marketing, writing, customer calls, etc.)
Shaw Talebi retweeted
Follow along @ShawhinT's five-step roadmap to gain a solid foundation in AI's current landscape. towardsdatascience.com/how-i…
Technical founders love to code, but that alone won't make you successful.
Here are 15 things I had to learn to become a (data) entrepreneur...
1. Talk to customers
2. Identify pain points
3. Sell
4. Sell to many people (i.e. marketing)
5. Make a website
6. Build a landing page
7. Write hooks
8. Write blogs
9. Post content
10. Cold outbound
11. Respond to emails faster
12. Use AI tools effectively
13. Look Foolish
14. Constantly learn
15. Keep going
What would you add?
Last month, I booked my most expensive mentorship call yet at $700/hr 😬
While this might sound like a big number, the person on the other side of the call makes $100k/mo as a solo AI entrepreneur.
Here are my key takeaways from this conversation...
1) Focus on customer pain points and problems, not your past experience and skills.
2) Price for the customer's value, not your time.
3) The bigger the price tag, the longer the copy (i.e. delay the ask)
4) Get hyper-clear on the customer and their problem, then attract them with free content (on socials) and a lead magnet.
5) The difference between 10k/mo and 100k/mo is more often business strategy rather than technical expertise.
Although these points might be Business 101 for some, many technical founders (like me) never learned these basics.
This is great news because it means I can probably get significant gains from a few simple adjustments.
Super grateful to @jxnlco for taking the time to share his wisdom with me 🙏
Shaw Talebi retweeted
Multimodal RAG systems can synthesize knowledge stored in a variety of formats, expanding what’s possible with AI. @ShawhinT reviews 3 simple strategies for developing such a system and then saw an example implementation of a multimodal blog QA assistant.
#RAG #Python
towardsdatascience.com/multi…
Shaw Talebi retweeted
Multimodal embeddings unlock countless AI use cases that involve multiple data modalities. Explore more mapping text and images into a common space in @ShawhinT's newest article.
towardsdatascience.com/multi…
Shaw Talebi retweeted
What are multimodal models and how can you start using them? @ShawhinT presents an accessible, hands-on introduction to one of the most rapidly evolving areas in machine learning. towardsdatascience.com/multi…
Physics majors when they heard @DarioAmodei say @AnthropicAI hired a bunch of theoretical physicists...








