代码旅行 (@tourcoder) header
代码旅行 (@tourcoder) profile picture

信仰永恒,无所畏惧|Do Faith No Fear 推文主要是记录,自说自话,有点话痨,主要活跃在 https://xitter.cf/t.co/WX18eESyTC,这里大部分内容是同步过来的,有时会因为字数限制被截断。

Joined August 2020
Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)Photo by 代码旅行 (@tourcoder)
Dragon Ball Z | Tap Hold Load 4k
4
161
2,279
48,553
20秒被这个律师干趴下,“聪明是最重要的东西”。
295
760
45
4,450
663,775
代码旅行 retweeted
71
1,743
96
11,447
312,771
TIL adding your terminal here will greatly speed up compile times. nnethercote.github.io/2025/0…
38
167
22
3,106
452,543
代码旅行 retweeted
Gemini 3 Flash is now available in your terminal! ⚡️ Fast, efficient, and capable! ❯ npm install -g @google/gemini-cli@latest 👇Read the announcement blog below
22
67
6
812
67,378
代码旅行 retweeted
Today we’re taking a big step on the path toward AGI and releasing Gemini 3— our most intelligent model yet. With Gemini 3, you can bring any idea to life. It is state-of-the-art in reasoning, the best model in the world for multimodal understanding, and our best agentic and vibe coding model.
158
437
122
3,387
493,748
代码旅行 retweeted
Our most anticipated launch of the year is here. - Gemini 3, our most intelligent model - Generative interfaces, for perfectly designed responses - Gemini Agent, made to complete complex tasks on your behalf See how Gemini 3 can help you learn, build & plan anything 🧵

416
1,087
339
8,612
5,218,411
代码旅行 retweeted
Omg very cute. 😂😂
588
7,348
592
47,951
1,750,689
代码旅行 retweeted
Parenting hacks👩‍🍼👪
179
5,100
163
49,926
13,411,967
代码旅行 retweeted
How to season a new Wok
234
1,963
161
35,758
10,806,373
49
1,295
186
10,722
783,009
代码旅行 retweeted
Replying to @alenatitova_
this one was 0.215, 0.61, 0.355, 1 0.43s
2
1
65
5,069
Apple website from start to present a thread 🧵
60
360
36
4,971
1,047,658
The 5 Levels of AI Agents Lets explore the 5 levels of AI Agents, from simple to complex. Always start with level 1 and add complexity as needed. Level 1: Agent with tools and instructions. When people say agents are just LLM + tool calls in a loop, this is what they mean (this also tells you their level of understanding). Instructions "teach" the Agent how to achieve its task and tools let Agents interact with external environments to push or pull data. Here's an Agent that helps developers build Agents using Agno (so clean 🤩) Level 2: Agent with knowledge and storage. Rarely does a model have all the information it needs to achieve its task and we obviously can't jam everything in the context, so we give the Agent knowledge that it searches at runtime (i.e Agentic RAG or Dynamic few-shot). Knowledge search needs to be hybrid (full-text and semantic). Hybrid search + reranking is the best out-of-the-box Agentic Search strategy you can use. Storage saves the Agent's state in a database. LLM calls are "stateless" and storage makes Agents "stateful" by storing messages in a database and adding them to the current call as needed. If you're using chatgpt, storage is what lets us continue the chat after closing the tab and each chat thread that you see on the left navbar is a "session" in storage. Storage also saves the session state (very useful) but that's for another day. Here's how knowledge & storage look like in code: Level 3: Agent with memory and reasoning. Memory let's an Agent remember details about a user and personalize its responses across sessions. This is a fairly new concept that everyone is still exploring. The part of memory im the most excited about is "self-learning", more on this soon. Reasoning is a key feature that every agent builder should know when and how to use. The biggest problem with Agents is that the success rate of an agent decreases with the number steps the agent needs to take. Eg: if success rate of 1 step is 90%, average success rate of an agent that needs to take 5 steps (across 1000s of runs) is ~60%. This is no good. Reasoning architectures not only improve cognitive reasoning (understanding of data and instructions) but also improves the success rate of each step. By taking a hit on cost and latency, we can improve the overall performance. Here's how you can add memory and reasoning to an Agno agent: Level 4: Multi Agent Teams. Agents work best when they have a narrow scope (i.e. specialized to a domain) and a reasonably small set of tools (<10 ish). By putting agents together in a team, we can increase the overall capabilities and solve broader, more complex problems. Remember to add reasoning, otherwise the Team leader struggles to work on complex tasks. Note: my current (2025) belief is that autonomous multi-agent teams don't work. They work <1/2 the time and thats no good. As models get better and capabilities improve, this is the level im most excited about, but at the moment autonomous multi-agent systems remain an area of research and experimentation only. Agno comes with an industry leading multi-agent architecture that supports 3 modes of execution: coordinate, route and collaborate with the ability to automatically manage agentic memory and context. Here's an example: Level 5: Agentic Systems. APIs (i.e. servers) that take in a request, asynchronously and reliable complete the task and stream back the result. These are hard, very hard - when the request comes in we need to save the state in a database and trigger an async job (background task in FastAPI) and stream the results back as they're ready. Websockets can work here, but they are not an each tech to work with. Agentic systems is where the $ is and what everyone is trying to build. We've put out the Agent API, Agent UI and detailed documentation on how to build them. I hope to write more on this to help AI engineers build better systems. Thank you for reading, I should probably turn this into a blog post. If you liked reading this, please let me know and consider starring Agno: agno.link/gh If you're interested in building Agents, you can read more on our docs: agno.link/docs Final parting words: AI Engineering is Software Engineering. Keep it simple and things become a lot easier. Thanks, Ashpreet
20
137
11
646
78,176
代码旅行 retweeted
MCP vs function calling visually explained:
47
409
29
3,624
482,113
代码旅行 retweeted
固态硬盘知识
46
339
3
1,741
540,963
代码旅行 retweeted
Be water, my friend
77
248
14
2,073
116,777
代码旅行 retweeted
咖啡配方☕️
47
439
11
3,344
1,408,409
New 2h11m YouTube video: How I Use LLMs This video continues my general audience series. The last one focused on how LLMs are trained, so I wanted to follow up with a more practical guide of the entire LLM ecosystem, including lots of examples of use in my own life. Chapters give a sense of content: 00:00:00 Intro into the growing LLM ecosystem 00:02:54 ChatGPT interaction under the hood 00:13:12 Basic LLM interactions examples 00:18:03 Be aware of the model you're using, pricing tiers 00:22:54 Thinking models and when to use them 00:31:00 Tool use: internet search 00:42:04 Tool use: deep research 00:50:57 File uploads, adding documents to context 00:59:00 Tool use: python interpreter, messiness of the ecosystem 01:04:35 ChatGPT Advanced Data Analysis, figures, plots 01:09:00 Claude Artifacts, apps, diagrams 01:14:02 Cursor: Composer, writing code 01:22:28 Audio (Speech) Input/Output 01:27:37 Advanced Voice Mode aka true audio inside the model 01:37:09 NotebookLM, podcast generation 01:40:20 Image input, OCR 01:47:02 Image output, DALL-E, Ideogram, etc. 01:49:14 Video input, point and talk on app 01:52:23 Video output, Sora, Veo 2, etc etc. 01:53:29 ChatGPT memory, custom instructions 01:58:38 Custom GPTs 02:06:30 Summary Link in the reply post 👇
393
1,588
205
13,647
975,502
代码旅行 retweeted
1997 年的 模拟人生1 游戏设计文档下载 donhopkins.com/home/TheSimsD…
2
4
24
21,631