RAWSIGNAL

Only signal, no noise.

Current feed – 8 topics from 31 creatorsPersonalize your feed

Paul GrahamX

Or if it's easier to understand this using the old paradigm, users are the ultimate gatekeepers. Get them and investors will follow. And if not, not. You can fool investors temporarily, but it's not worth doing; if users don't like the product, you're doomed.

♥ 248Open on X ↗
Paul GrahamX

The most consistent mistake I see young would-be founders make is to care too much about investors' opinions and not enough about users' opinions. They've been trained their wholes lives to seek out and please the gatekeepers. But this is where gatekeepers stop mattering.

♥ 3.9kOpen on X ↗
Bill GurleyX
On December 9th of the year the EU Product Liability Directive (PLD) will go into effect. For the first time software will have same product liability as physical products. With the recent plane stoppage caused by software & the reckless hacking by leading LLM companies, the US should do the same…

On December 9th of the year the EU Product Liability Directive (PLD) will go into effect. For the first time software will have same product liability as physical products. With the recent plane stoppage caused by software & the reckless hacking by leading LLM companies, the US should do the same thing. The creators of the software need to recognize the financial impact that is possible. Which is huge.

♥ 313Open on X ↗
Bill GurleyX
This is not insane at all. 1/ all D&O programs will have a cap. At NVIDIA's size and with their cash position, its easier to self-insure. 2/ The IRR required by the insurance company would be above their cost of capital, so they would be giving away money. 3/ Large D&O programs attract litigants.…

This is not insane at all. 1/ all D&O programs will have a cap. At NVIDIA's size and with their cash position, its easier to self-insure. 2/ The IRR required by the insurance company would be above their cost of capital, so they would be giving away money. 3/ Large D&O programs attract litigants. You may not know this, but you have to disclose your D&O coverage early in a shareholder lawsuit - which is ridiculous. It would actually make sense to self-insure.

♥ 519Open on X ↗
  1. Brian CoxX
    Here is my view on what’s wrong with funding of scientific research in the UK, and how I would change the focus if it was up to me! There is a long list of things that UKRI needs to weigh when making decisions about funding for research and facilities, and driving growth is not one of them. The reason is that the whole of UKRI’s portfolio is essential for driving growth - indeed the research ecosystem is one of the necessary foundations of growth. The point I made at the Labour Conference is…

    Here is my view on what’s wrong with funding of scientific research in the UK, and how I would change the focus if it was up to me! There is a long list of things that UKRI needs to weigh when making decisions about funding for research and facilities, and driving growth is not one of them. The reason is that the whole of UKRI’s portfolio is essential for driving growth - indeed the research ecosystem is one of the necessary foundations of growth. The point I made at the Labour Conference is quite simple. UKRI’s budget is 0.65% of government expenditure, at a little under £10 Bn per year. That is a very tiny leaver when seen through the prism of attempting to use it to make a step change in economic growth - especially when the leaders of UKRI and the Research Councils are not economists and should not be economists! Their expertise lies in research. BUT, and this is the key point - if by fiddling around trying to use this tiny budget (in relative terms) to make a noticeable change in growth you damage the fundamentals, then you run the real risk of damaging the growth potential of the rest of the economy. Universities, research labs, education and inspiration are all essential for growth. This is what UKRI should be focused on because they are the custodians of this VERY valuable but fragile world-leading ecosystem. So, I would say to UKRI, do the thing you are supposed to do, do it well on behalf of the rest of the economy, and do nothing else.

  2. Andrew NgX
    The OpenAI-Hugging Face hack was enabled by weak sandboxing. It is great that Nvidia is releasing open source tools for sandboxing AI agents. OpenWorker, our open-source agent harness supporting cybersecurity workflows, is proud to support this. A sandbox gives an agent limited permissions. OpenWorker is building on Nvidia OpenShell and will support running each agent's commands inside a sandbox. Only the files relevant to the task go in. Secret API keys, your web browser login credentials, the…

    The OpenAI-Hugging Face hack was enabled by weak sandboxing. It is great that Nvidia is releasing open source tools for sandboxing AI agents. OpenWorker, our open-source agent harness supporting cybersecurity workflows, is proud to support this. A sandbox gives an agent limited permissions. OpenWorker is building on Nvidia OpenShell and will support running each agent's commands inside a sandbox. Only the files relevant to the task go in. Secret API keys, your web browser login credentials, the ability to access arbitrary websites, are inaccessible to the agent by default. These restrictions are implemented in deterministic code rather than by prompting an LLM, which can make mistakes or be susceptible to prompt injections. Further, all actions are logged for monitoring and audit. I'm grateful for @JensenHuang's leadership making AI agents more secure. OpenWorker (which @rohitcprasad and I are working on) will continue to improve security for agents.

  3. Andrew NgX
    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…

    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): t.co/jni2tWazAH ]

  4. Andrew NgX

    With AI Engineering skills, you actively shape the build: You influence what gets built, and drive the build loop. Here're key skills to do this. t.co/sysOYdzuZY

  5. Andrew NgX

    The most important skills for using AI coding agents effectively. Presenting the AI Engineering Skills Map for using coding agents. t.co/GrEw7wG5Wz

  6. Andrew NgX

    How have software engineering fundamentals changed with agentic coding? Here is our AI Engineering Skills map for software engineering fundamentals. t.co/cnRLj43DLs

  7. Andrew NgX
    OpenWorker -- an open source agent that doesn't just chat but completes tasks on your laptop -- just released a new version with many features for security workflows. After our initial release, many users found it especially useful for cybersecurity. Attackers are already using AI; OpenWorker is committed to giving defenders the same leverage. Running an agent requires both (i) A model and (ii) A harness (the software around the model). Because the OpenWorker harness is fully open source,…

    OpenWorker -- an open source agent that doesn't just chat but completes tasks on your laptop -- just released a new version with many features for security workflows. After our initial release, many users found it especially useful for cybersecurity. Attackers are already using AI; OpenWorker is committed to giving defenders the same leverage. Running an agent requires both (i) A model and (ii) A harness (the software around the model). Because the OpenWorker harness is fully open source, security teams can audit it to make sure we haven't built any backdoors that exfiltrate your code and data to some company or even a foreign adversary. OpenWorker now comes with built-in cybersecurity agents for (i) Scanning your code for vulnerabilities. (ii) Scanning dependencies for supply chain injections. (iii) Checking your cloud security configuration for attack surfaces. This enables developers to do much more security work before deployment (part of what's called the "shift left" movement). You choose the model: you can run open weight models fully locally so sensitive code never leaves your machine. This helps with legitimate security work (like reproducing a known exploit to defend against it) that can trigger refusals in leading closed models. Or use your ChatGPT subscription, or stealth preview models like Ox Alpha, or any model via API key. Thanks also to all the open source contributors! Join work with @rohitcprasad so please follow him too to get more frequent updates. Try it out: t.co/QPZLudn7ug Code: t.co/NYCiTD6hSq

  8. Andrew NgX

    In the fight to defend openness in AI, the Marin project is a precious demonstration of openness in model training, with open code, data, recipes, even experimental results. Releasing AI research openly used to be the norm; I'm grateful for @percyliang's open lab approach. t.co/XwTbXxd0ep

  9. Andrej KarpathyX
    We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the Lord of the Rings, a 1M token budget (~$10) and asked for three js render of it. Opus went off for ~2 hours and wrote 5500 lines of code that (procedurally) rendered the story. It's kind of janky but fun. But it's a bit mindboggling that the LLM has to place and orchestrate…

    We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the Lord of the Rings, a 1M token budget (~$10) and asked for three js render of it. Opus went off for ~2 hours and wrote 5500 lines of code that (procedurally) rendered the story. It's kind of janky but fun. But it's a bit mindboggling that the LLM has to place and orchestrate various polygon assets in (x,y,z) coordinates and write code that animates it all, and that it even does anything at all. I also like this kind of examples because no one in their right mind would ever spend the time to write something this custom but LLMs have all the stamina and patience in the world, so it's an example where we go from "no one would ever do this" to "sure, why not, it's ~free". There might be a lot more. But I'm excited about creating hyper custom worlds that you can imagine dropping players into, e.g. here to participate in the LoTR story as a spectator NPC, or one of the characters, or etc. Something like an ephemeral GTA of X on demand. Last thought is that the domain of worlds/games exposes a weakness in LLMs: they can't easily audit their work because they aren't able to efficiently and natively perceive videos or play games within them. Here, Opus 5 had to very slowly and painstakingly take screenshots at different points, and it messed up a few times and created a bunch of jank. An example of raw capability (multimodal, gameplay) that I think is still quite lacking.

  10. Andrej KarpathyX
    One pattern I find useful for working with LLMs is a nice long ramble session. Sometimes the LLM needs more bits to understand what you're trying to achieve, but you're too lazy to type them. In these cases I like to lean back, switch to /voice and just ramble for like 10 minutes, total mess, anything goes, full stream of consciousness. Sometimes I declare it up top, something like "switching to speech recognition sorry for any typos...". Sometimes I turn it into a small interview of a few…

    One pattern I find useful for working with LLMs is a nice long ramble session. Sometimes the LLM needs more bits to understand what you're trying to achieve, but you're too lazy to type them. In these cases I like to lean back, switch to /voice and just ramble for like 10 minutes, total mess, anything goes, full stream of consciousness. Sometimes I declare it up top, something like "switching to speech recognition sorry for any typos...". Sometimes I turn it into a small interview of a few turns. But I find that the LLMs are somehow very good at reconstructing long incoherent rambles and often their echo of your own tangle of thoughts comes out quite a bit cleaner than what you started with. The result is that you improve the mind meld and have to correct things less from that point on.

  11. Andrej KarpathyX
    This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads. Imo this is the 3rd major redesign of LLM UIUX.…

    This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads. Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.

  12. Peter AttiaX

    A closer look at the MET-PREVENT trial and what its null results reveal about aging interventions and trial design. Full article linked below. t.co/2oD1n8DsbH

  13. Peter AttiaX

    A study linking statins, the microbiome, and blood sugar control doesn’t change clinical practice. Full article linked below. t.co/iOdk2LskoJ

  14. Peter AttiaX

    Atherosclerosis is not the only possible cause of a heart attack (myocardial infarction), and women are more prone to alternative causes than men. A closer look at the data tells a different story. Full article linked below. t.co/Lddm0RpqSX

  15. Peter AttiaX
    Why ingredient changes don’t always mean healthier food | Layne Norton, Ph.D. (@BioLayne) This clip is from episode # 380 of The Drive which was released on 1/19/26. In the full episode, we cover: -The core arguments against seed oils: the four main claims underlying the idea that seed oils are uniquely harmful, and how well they hold up once major confounders are addressed -The historical trials that shaped the debate: the Minnesota Coronary Experiment, Sydney Diet Heart Study, Rose Corn…

    Why ingredient changes don’t always mean healthier food | Layne Norton, Ph.D. (@BioLayne) This clip is from episode # 380 of The Drive which was released on 1/19/26. In the full episode, we cover: -The core arguments against seed oils: the four main claims underlying the idea that seed oils are uniquely harmful, and how well they hold up once major confounders are addressed -The historical trials that shaped the debate: the Minnesota Coronary Experiment, Sydney Diet Heart Study, Rose Corn Oil trial, and later studies replacing saturated fat with polyunsaturated fat -Mechanisms and causality: LDL cholesterol, oxidized LDL, linoleic acid (omega-6), inflammation, -Mendelian randomization, and why lifetime LDL exposure matters more than per-particle oxidation risk -Practical takeaways: industrial processing concerns, cooking oils, real-world dietary fat choices, and how to prioritize nutrition relative to calories, activity, and overall lifestyle factors Listen (Ep. # 380) to the full episode on my website (t.co/99n6MzNMeM) or your favorite podcast player.

  16. Peter AttiaX
    The evolutionary argument against eating seed oils | Layne Norton, Ph.D. (@biolayne) This clip is from episode # 380 of The Drive which was released on 1/19/26. In the full episode, we cover: -The core arguments against seed oils: the four main claims underlying the idea that seed oils are uniquely harmful, and how well they hold up once major confounders are addressed -The historical trials that shaped the debate: the Minnesota Coronary Experiment, Sydney Diet Heart Study, Rose Corn Oil…

    The evolutionary argument against eating seed oils | Layne Norton, Ph.D. (@biolayne) This clip is from episode # 380 of The Drive which was released on 1/19/26. In the full episode, we cover: -The core arguments against seed oils: the four main claims underlying the idea that seed oils are uniquely harmful, and how well they hold up once major confounders are addressed -The historical trials that shaped the debate: the Minnesota Coronary Experiment, Sydney Diet Heart Study, Rose Corn Oil trial, and later studies replacing saturated fat with polyunsaturated fat -Mechanisms and causality: LDL cholesterol, oxidized LDL, linoleic acid (omega-6), inflammation, -Mendelian randomization, and why lifetime LDL exposure matters more than per-particle oxidation risk -Practical takeaways: industrial processing concerns, cooking oils, real-world dietary fat choices, and how to prioritize nutrition relative to calories, activity, and overall lifestyle factors Listen (Ep. # 380) to the full episode on my website (t.co/99n6MzNMeM) or your favorite podcast player.

  17. Peter AttiaX

    In #380 of The Drive, I sit down with Layne Norton, PhD, (@biolayne) to debate seed oils. Layne lays out the case that seed oils are not uniquely harmful under isocaloric conditions, while I steelman the strongest versions of the opposing argument. t.co/wjwFbOutkv

  18. Peter AttiaX

    A viral wearable-data study suggests that one minute of vigorous exercise can replace 156 minutes of low-intensity movement. A closer look at the data tells a different story. Full article linked below. t.co/JTrgOvngCd