Fun side thing to help me read
Select a term and it explains it in the context of the sentence you're on — no jumping to the link and losing your place. At the end it builds one linked note of everything you read.
Just hit 100 followers 🎉
Thanks everyone who followed, connected and replied 🙏
Hey @X Algorithm 👋 @grok
Looking to connect with:
🚀 SaaS Founders 🤖 AI Builders 💻 Developers ⚡ Indie Hackers
What are you building? Drop below 👇 Let's connect! 🤝
@shzhv13 yep, that’s why 3 and 8 kinda go hand in hand. once you start logging what the agent actually got, a lot of the “it reasoned wrong” stuff turns out to be a bad chunk or old data. the model wasn’t dumb, it just got fed the wrong stuff
10 lessons from 6 years of building AI systems that actually ship:
1. Your demo works on 10 examples. Production has 10,000 you never imagined
2. Evals come first. If you can’t measure it, you’re just guessing
3. Most “agent” problems are really retrieval problems in disguise
4. Chunking strategy matters more than which vector DB you pick
5. Every LLM call needs a fallback, a timeout, and a log line
6. Structured outputs will save you more hours than prompt tricks
7. Cost creeps up quietly. Track tokens per request from day one
8. Nobody can explain a bad output if you didn’t log what went in
9. Prompt injection isn’t theoretical. Someone will try it in week one
10. The model is maybe 20% of the system. The other 80% is plain engineering
The models keep getting smarter. The systems around them still need someone who knows what they’re doing.