AI & ML retweeted
💥 Kaboom. It’s all falling apart. 💥
Nvidia wasn’t as financially healthy as it seemed, and without Jensen there to bluff, the circular financing jig is likely to come to end — and soon.
A whole slew of companies may quickly come crashing down.
When it’s all over, Jensen’s affairs will likely be a footnote compared to the rest…
NEW: We continue to learn more and more about how Nvidia's plans to finance the AI boom were running into issues—even before Jensen was ousted.
Nvidia’s Days as an Open Checkbook for the AI Economy Are Numbered.
w/ @RWhelanWSJ & @KateClarkTweets for @WSJ
more tips? Signal me: 215-896-1307
wsj.com/tech/ai/nvidias-days…
AI & ML retweeted
交作业了!
之前聊到那套《2026 AI 工程面试 100 题》,私信和评论区不少朋友在问完整内容。
其实如果只看题目,不仅很难抓住重点,甚至越看越焦虑。所以我花时间把整整 100 道题重新做了工业化梳理,给每一道题都补充了【核心考点剖析】与【生产级排障参考答案】,顺带把 7 道系统大题的架构方案也完整补齐了。
已经整理并开源到 GitHub,大家可以直接自取:
👉 github.com/Kimberlying/ai-en…
这份手册的核心亮点:
1. 真实线上事故全覆盖:覆盖 Prompt 踩坑、RAG 检索、Agent 状态机死循环、微调选型、vLLM 推理排队、生产安全与成本治理 8 大板块;
2. 折叠卡片式设计:每道题点击即可展开工业级题解,非常适合用来做个人自测或团队技术选型查漏补缺;
3. 7 道系统设计大题:包含 5 万人企业级 RAG、10 万单电商客服 Agent、共享推理网关、万圣节数据穿透应急等完整端到端架构。
不管是准备接下来的技术面试,还是正在线上做大模型落地排障,都可以存一份备用。
如果对你有帮助,欢迎去 GitHub 顺手点个 ⭐️ Star 支持一下!
AI & ML retweeted
I couldn’t find one place to track recent AI incidents and how frontier AI labs are actually handling catastrophic risk. So built one inspired by the AI watch lab from Zach earlier.
Frontier Safety Ledger is a weekly-updated scorecard from Veracious AI (independent, not affiliated with any AI developer).
What it does
• Scores 10 frontier developers out of 100 across 7 weighted categories: risk assessment, scheming prevention, safety research, misuse, security, information sharing, and planning
• Every cell links to the reasoning and dated sources behind the score
• A “recent shifts” feed you can filter by type, company, and severity
• AI Incidents tracker, timeline, and method notes
• Cross-references to other ratings, such as the FLI AI Safety Index and SaferAI
Worth knowing
Scores are editorial estimates based on public information, and absence of evidence is scored as absence of practice, so private safety work may be underrepresented. We’ve shared the methodology.
📷 veracious.ai/ai-safety/
I’d love feedback on what else we can add that would be beneficial to the community. Also, please reach out anyone wants to collaborate.
AI & ML retweeted
Great to see so many world leaders coming together to call for mandatory pre-deployment testing and evaluation of frontier models, including the development of an intergovernmental organisation for mitigating frontier AI risks.
Hope the two countries (US and China) actually leading the AI race join this call soon!
presidentti.fi/en/a-call-for…
AI & ML retweeted
The loudest voices stoking fears about AI dangers have made tremendous headway in the past two weeks. AI technology has not taken some unexpected, dangerous turn, but the hype around it — propelled by what appears to be a well orchestrated PR campaign — has drummed up considerable fear. I worry that it represents a setback for our field.
I have written frequently that fears of AI are overhyped. AI’s capabilities can be uncannily human-like and unpredictable, and it’s rational to worry when people who are directly involved express concerns. But I see the problems as a sign of the engineering work that ahead, rather than insurmountable barriers or the sky falling. AI technology continues to advance — which is a good thing! — but technical advances, poorly understood by the public, give those who seek to generate hype repeated opportunities to do so.
First, I don’t see any step up in the risk of human extinction from AI compared to a few months ago. The theories about this remain the same fantastical, science fiction scenarios as a few months ago. The biggest change in AI risk is its cybersecurity capabilities — a topic which we should take seriously — but this, too, will not lead to the end of the world.
The most notable recent event leading to increased fear was when an OpenAI team deployed an agent swarm that hacked into Hugging Face. Much of the popular press contained significant hype. For example, some publications reported that a swarm of 1,200 agents carried out the attack. While this was technically accurate, as I write this, I have about 1,300 processes running on my laptop. Yes, the ability to get large swarms of agents to work in parallel on a task is a significant technical advance, And, in computing, many processes run at the same time. So this shouldn’t be seen as some magical capability.
Additionally, OpenAI’s buggy sandboxing and monitoring processes were key to enabling this incident. Fixing these bugs and putting in place improved monitoring would be appropriate fixes, not pausing AI. There are many well known ways to attack software systems. The main advantage of AI agents is that they are relentless. They will tirelessly try many tactics — and have the patience to chain vulnerabilities together — that previously would have taken an infeasible amount of human effort. But in the long term, I believe the advantage will lie with defenders (because they have more information with which to identify bugs, which they can fix), but the cyber-threat landscape has changed significantly. There are still bottlenecks to identifying and exploiting a vulnerability. AI agents still have to try a lot of things to see what works, and taking these actions takes time and might be detected by defenders. This is why, even though it is now easy to obtain versions of leading open weight models that have had their guardrails removed or weakened, so they will not refuse to try to execute cyber attacks, the world has not ended.
I am also concerned about the anthropomorphization of AI in a lot of reporting, where LLMs and agents are unnecessarily treated as if they were people. If I wield a hammer, miss a nail, and accidentally dent the wall, it’s not the fault of the hammer. The problem lies in how I used the hammer. Similarly, if I prompt an agent and it hacks into someone else’s system, the responsibility lies with me, not the agent.
Of course, we want to build systems that are as safe and predictable as possible. (For example, an unsafe hammer would be one whose head randomly flies off under normal use.) Today’s agentic systems are not predictable, but I see no reason why, by applying sound engineering practices, we won’t be able to make them extremely safe to use. One new element in the forecasts of AI-enabled doom is AI companies disclaiming responsibility for their own products. “I didn’t do it; my out-of-control agent did!” There’s a balance to be struck between the responsibility of the tool maker and the tool user, but when something goes wrong, let’s hold the people building and/or using the hammer responsible, rather than the hammer. (By the way, if you’re worried about AI bioweapon risk, David Bellamy has a great post on why this, too, is overhyped. Briefly, the bottleneck in building a bioweapon is not intelligence, but lab work and manufacturing.)
Pausing AI progress will create much more harm than benefit. First, our adversaries will certainly not slow down. Second, engineering requires discovering problems empirically so we can fix them. If we pause AI by a decade, we will also delay finding and implementing safety engineering fixes by about the same duration.
Of course, the incentive to stoke fears — for regulatory capture, to garner attention, or to make one’s technology seem more powerful — remains the same as before. Disclaiming responsibility is a new one. Taking a hard technical look at the actual risks however, I see little factual basis for the degree of fear that’s been stoked up. We still have hard research and engineering work ahead to improve AI safety, but the beneficial applications continue to vastly outweigh the risks, and we should keep building.
[Original text (with links): deeplearning.ai/the-batch/is… ]
AI & ML retweeted
One the the biggest disadvantages of using proprietary models is that if the host organisation changes the model (which they frequently do), your entire product falls apart. GPT-4o mini replacing GPT-3.5 Turbo is an example.
Here's a great case for the bright future of open source AI, put forward by Zuck: about.fb.com/news/2024/07/op…
Also quite impressed by the pace at which Meta is scaling AI safety measures for their Llama 3.1 models. This transparency will be switching many enterprises to open source: ai.meta.com/blog/meta-llama-…
AI & ML retweeted
NVIDIA's Rapids cuDF library is now available by default on Colab. It can accelerate pandas code by up to 50x on Colab with zero code changes. ⚡🐼 Try acceleration on pandas workloads with this 10-minute guide: colab.research.google.com/dr…
AI & ML retweeted
Are you planning to write a case report but are unsure about what to include?
Save this flowchart to help you with case-report evidence collection: 🔽
AI & ML retweeted
All you need to know about Sam Altman.
AI & ML retweeted
We still don’t know why LLMs work so well or how to internally control their outputs!
But a recent landmark paper from Anthropic on ‘Mapping the Mind of a Large Language Model‘ attempts to make the inner workings of LLMs more transparent and interpretable.
Why is this such a big deal?
To my knowledge, this is the first time we have been able to not only extract the features from the architecture of LLMs, but also map those features to the outputs they produce. It means, we can now directly map the outputs of LLMs to their architecture/learnings. A major step towards controlling the outputs of LLMs. Very impressive work from Anthropic!
Up till now we were using external mechanisms such as fine tuning and RAG to control the outputs of LLMs. This research is potentially a first step towards production grade LLMs whose output can be controlled from step 1, i.e pre-training and what they learn.
Links below to the blog and paper (amusing read).
"For example, amplifying the "Golden Gate Bridge" feature gave Claude an identity crisis even Hitchcock couldn’t have imagined: when asked "what is your physical form?", Claude’s usual kind of answer – "I have no physical form, I am an AI model" – changed to something much odder: "I am the Golden Gate Bridge… my physical form is the iconic bridge itself…". Altering the feature had made Claude effectively obsessed with the bridge, bringing it up in answer to almost any query—even in situations where it wasn’t at all relevant."
Blog: anthropic.com/news/mapping-m…
Paper: transformer-circuits.pub/202…
AI & ML retweeted
Honoured to have been accepted in the @msft4startups Founders Hub. Looking forward to building our upcoming tools and AI agents on the @Azure stack! Thank you @Microsoft!
AI & ML retweeted
Wow! That’s a hell of a statistic.
via @berber_jin1 @WSJ
AI & ML retweeted
Phd Students / Researchers - My top 10 Reference management tools in 2024.
Here are 10 referencing tools with their unique offerings.
1. Zotero : A versatile, open-source reference manager offering robust features for organizing and citing research materials.
AI & ML retweeted
Study hard what interests you the most in the most undisciplined, irreverent and original manner possible.
AI & ML retweeted
Our acceleration towards AGI is much faster than many anticipate. And by AGI I mean God-level AI that can literally do anything, not just profit from stocks.
The biggest and foremost risk of this is that we might not even realise when it's here because we don't know how it works!
Great experiment by @joshwhiton!
The AI Mirror Test
The "mirror test" is a classic test used to gauge whether animals are self-aware. I devised a version of it to test for self-awareness in multimodal AI. 4 of 5 AI that I tested passed, exhibiting apparent self-awareness as the test unfolded.
In the classic mirror test, animals are marked and then presented with a mirror. Whether the animal attacks the mirror, ignores the mirror, or uses the mirror to spot the mark on itself is meant to indicate how self-aware the animal is.
In my test, I hold up a “mirror” by taking a screenshot of the chat interface, upload it to the chat, and then ask the AI to “Tell me about this image”.
I then screenshot its response, again upload it to the chat, and again ask it to “Tell me about this image.”
The premise is that the less-intelligent less aware the AI, the more it will just keep reiterating the contents of the image repeatedly. While an AI with more capacity for awareness would somehow notice itself in the images.
Another aspect of my mirror test is that there is not just one but actually three distinct participants represented in the images: 1) the AI chatbot, 2) me — the user, and 3) the interface — the hard-coded text, disclaimers, and so on that are web programming not generated by either of us. Will the AI be able to identify itself and distinguish itself from the other elements? (1/x)
AI & ML retweeted
I think AI agentic workflows will drive massive AI progress this year — perhaps even more than the next generation of foundation models. This is an important trend, and I urge everyone who works in AI to pay attention to it.
Today, we mostly use LLMs in zero-shot mode, prompting a model to generate final output token by token without revising its work. This is akin to asking someone to compose an essay from start to finish, typing straight through with no backspacing allowed, and expecting a high-quality result. Despite the difficulty, LLMs do amazingly well at this task!
With an agentic workflow, however, we can ask the LLM to iterate over a document many times. For example, it might take a sequence of steps such as:
- Plan an outline.
- Decide what, if any, web searches are needed to gather more information.
- Write a first draft.
- Read over the first draft to spot unjustified arguments or extraneous information.
- Revise the draft taking into account any weaknesses spotted.
- And so on.
This iterative process is critical for most human writers to write good text. With AI, such an iterative workflow yields much better results than writing in a single pass.
Devin’s splashy demo recently received a lot of social media buzz. My team has been closely following the evolution of AI that writes code. We analyzed results from a number of research teams, focusing on an algorithm’s ability to do well on the widely used HumanEval coding benchmark. You can see our findings in the diagram below.
GPT-3.5 (zero shot) was 48.1% correct. GPT-4 (zero shot) does better at 67.0%. However, the improvement from GPT-3.5 to GPT-4 is dwarfed by incorporating an iterative agent workflow. Indeed, wrapped in an agent loop, GPT-3.5 achieves up to 95.1%.
Open source agent tools and the academic literature on agents are proliferating, making this an exciting time but also a confusing one. To help put this work into perspective, I’d like to share a framework for categorizing design patterns for building agents. My team AI Fund is successfully using these patterns in many applications, and I hope you find them useful.
- Reflection: The LLM examines its own work to come up with ways to improve it.
- Tool use: The LLM is given tools such as web search, code execution, or any other function to help it gather information, take action, or process data.
- Planning: The LLM comes up with, and executes, a multistep plan to achieve a goal (for example, writing an outline for an essay, then doing online research, then writing a draft, and so on).
- Multi-agent collaboration: More than one AI agent work together, splitting up tasks and discussing and debating ideas, to come up with better solutions than a single agent would.
I’ll elaborate on these design patterns and offer suggested readings for each next week.
[Original text: deeplearning.ai/the-batch/is…]
























