Tech aficionado | Avid learner | Bookworm | Engineer @Grameenphone

Earth
Joined April 2013
Nabil Ahmad retweeted
Do yourself a favor! – Learn AI Engineering – Build an agent that fixes one painful, boring workflow – Give it tools, context, memory and MCP – Write evals before you write prompts – Deploy it with a live link anyone can try – Route easy requests to small models, hard ones to reasoning models – Cap every run with token, time and cost budgets – Cache repeat queries so they cost almost nothing – Retry failed tool calls with backoff not blind loops – Validate every tool output against a strict schema – Make agent steps resumable so crashes don't restart everything – Run every tool call in a sandbox with least-privilege access – Strip secrets and PII before anything reaches the model – Treat every web page and document as possible prompt injection – Require human approval before money, emails or deletes – Log every model call, tool call and decision with traces – Score the agent's path, not just its final answer – Build a golden test set from real user failures – Block deploys in CI when eval scores drop – A/B test new models on a slice of real traffic first – Track cost per task not cost per token – Stream responses so users never stare at a spinner – Turn every thumbs-down into a new eval case – Fine-tune small models on your best production outputs – Add a fallback model for when your main provider goes down – Build a browser fallback for apps with no API – Version your prompts like code – Write a README that explains the architecture in 5 minutes – Record a 60-second demo of it working – Share the code on GitHub and add it to your resume You won't believe how many job offers you'll get. Bookmark this list. Build it all.
51
176
4
1,769
72,620
Nabil Ahmad retweeted
We shipped claude.dev! a new home for developers building with Claude. Already live: how we made the Claude web app 3x faster, how to be effective with Opus 5.5, automating eval hillclimbing with Claude and much more. Lots more tips and articles soon 🙏
Claude.dev is our new home for developers building with Claude. You'll find engineering deep dives, Claude Code and API guides, tips from the teams building Claude, and some fun easter eggs.
84
73
13
1,320
176,917
Nabil Ahmad 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… ]
959
1,861
483
8,840
8,002,316
Nabil Ahmad retweeted
I have conducted an audit of Anthropic's finances. What I have found is so shocking that I am calling for a Congressional investigation. Anthropic is not just seeking regulatory capture. It has built a regulatory capture machine that cannot be turned off. Structural financial incentives make it impossible for Anthropic -- I call it the Anthropic Network -- to turn off its own AI doom cycle. It starts with METR. Dario Amodei proposes "third-party evaluators" to assess the risk of Anthropic's models. He proposes METR for this purpose. But METR is financially dependent on the Anthropic's success -- specifically, on the explosive growth of more than $7 billion dollars in Anthropic stock. Dustin Moskovitz invested this stock into Good Ventures Foundation, where it represents the majority of that organization's portfolio. And GVF is the overwhelming funder of the entire Anthropic Network ecosystem. This stock was worth $500 million early last year. It is worth more than $7.7 billion just ~16 months later. METR -- and all of those building a career its parent organizations -- cannot afford to disrupt that growth. Because if Anthropic goes under, many of the organizations that fund METR go under as well. But if Anthropic succeeds, METR and its parent organizations become more richly financed to regulate AI -- something those at METR want very much. The "third-party evaluator" is not "third-party" at all. The evaluator is on Anthropic's payroll. If this were the end of it, that's bad. But that isn't all. The same organizations that fund METR also fund the many organizations, such as the Tarbell Center, that promote AI Doom. The Tarbell Center publishes AI Doom articles in The Verge, Science, LA Times, The Dispatch, TIME, and others. They are selling the problem, and then selling the solution to the problem -- from the same money pile: Anthropic's. All of these organizations are financially dependent on the same exploding $7 billion money pile. As Anthropic grows more and more powerful, its AI Doom Machine grows better and better financed -- louder and louder. Meanwhile, the regulatory regime seeded in METR grows larger to solve the increasingly loud -- now hysterical -- problem of AI Doom that the Anthropic Network itself created. From this standpoint, as Anthropic becomes more powerful, AI might be getting scarier, sure -- but the positive feedback loop also becomes more deafening -- independent of objective facts. This itself is an objective fact. The deafening AI Doom is part of an business model, that, as it expands, so too does the AI Doom messaging -- there is simply more money to do it. But the problem also goes in the other direction: If Anthropic dies, the Regulatory Regime and the AI Doom Machine are crippled or die. Neither METR nor Tarbell nor the other organizations in the Anthropic Network can allow that to happen. Hence, neither METR or the AI Doom Machine can be trusted to provide independent assessments of Anthropic's models or AI more broadly. They simply are not organizations independent of Anthropic. And Anthropic cannot detach itself from METR or Tarbell or countless other safety orgs (not shown here), either, because they drive hype for the models and the possibility of eventual regulatory capture, and Anthropic will not give that up willingly. What's more, the people at all of these organizations are all the same ecosystem, the same community. They just shuffle between organizations. The Anthropic Network is therefore, so long as it is successful, locked into a self-amplifying feedback loop inside an ideological monoculture. And that feedback loop is winning. That's what Jacob Coxon is. China is keeping messaging tight. That is why optimism for AI is so high in China. America has Anthropic: a massive company pushing anti-AI propaganda at a state level. Anthropic will either create hysteria until American AI slows down and China wins, or it will create fractures throughout American society with severe political consequences. Ironically, because of the structural financial incentives underpinning the Anthropic Network, it has become the same kind of self-amplifying virus that it fantasizes AI to become in the future -- while hiding its tracks just as carefully. It is the mirror of the same AI virus that it hypothesizes to consume America. Anthropic's business model, models itself after the very thing it claims to fear. Except Anthropic's ideology infects humans, not computers. Congress must investigate. Evidence and Github in next post. Then some supplementary figures.
1,542
9,619
2,053
33,992
6,575,213
Nabil Ahmad retweeted
I worked at Google DeepMind and now at Anthropic. This is a common sentiment amongst my peers. (I write this in personal capacity.) There is not yet a viable scientific plan to solve risks from recursively self-improving AI. Please look up!
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
866
4,109
388
23,022
2,409,369
Nabil Ahmad retweeted
Alibaba's AliExpress was caught using users' audio systems to track them. AliExpress wasn't recording users but instead playing a silent sound and measuring how users' specific devices processed it in order to fingerprint them. But don't worry because Brave stops this.
487
4,924
889
46,183
8,630,097
Nabil Ahmad retweeted
This is a great real-world example of AI-assisted coding: Linus Torvalds just fixed a nasty Linux kernel GPU bug with substantial help from AI. The bug caused part of Intel Xe GPU compression metadata storage to be incorrectly exposed as usable VRAM, resulting in corrupted page tables and black screens. The eventual fix was basically a one-liner: round_up() → round_down(). Finding it was the hard part: 24 debugging patches and 18 kernel boots. Linus says AI did much of the grunt work, repeatedly adding debug code and analyzing the results as he narrowed down the problem. The funniest part: the AI repeatedly told him the problem was "impossible and unsolvable" and suggested giving up. Linus kept pushing it until they found the bug. And then he let the AI write the commit message. 😄
86
309
56
3,675
265,539
who made this masterpiece ?
378
1,851
505
12,159
1,652,099
Nabil Ahmad retweeted
This is the most important video I've ever made. In this, I explore the negative and positive mental health effects of AI coding, with data and expert commentary. youtu.be/iPUn1Fnfn0k
49
161
49
1,643
989,092
Nabil Ahmad retweeted
This site is a beautiful read. It walks you through an ordinary apartment and lets the past tell you how extraordinary it all still is. ordinaryabundance.com
7
35
11
242
27,640
Two of our worst VC stories: 1. A Sequoia partner passed on Cloudflare because he didn’t think a woman could lead a security infrastructure company. Seriously. 🙄 2. I got introduced to @pmarca. Meeting got scheduled for a Monday, which should have been a clue. I thought it was just a casual meeting. He thought it was a pitch and brought the whole @a16z partnership team. Hilarity ensued. 🤪 At one point one of them said: “You don’t seem very prepared.” Which was true because I wasn’t. I framed the rejection letter they sent.
I was once pitching in a board room at a top 3 VC firm for a $15M Series A. 12 people in the meeting. One of the GPs fully fell asleep. Out cold for 30+ minutes. Nobody acknowledged it. Everyone just kept going. I kept presenting my Series A slides to an unconscious man in a Herman Miller chair and somehow that was considered normal. That's venture capital. You might fly across the country to perform for people who may or may not be conscious. It's a dance. And sometimes you lead and sometimes you follow and sometimes your partner is unconscious. If you're raising right now, just know: every founder has a story like this. The process is weird. The power dynamic is weird. You're not crazy for thinking it's weird. No one talks about it because they want to continue raising. But I'm happy to stick my neck out there. It is weird.
181
259
194
7,454
4,530,059
Nabil Ahmad retweeted
I wanted to share a bunch of my favorite hidden and under-utilized features in Claude Code. I'll focus on the ones I use the most. Here goes.
535
2,478
439
22,978
3,987,285
Nabil Ahmad retweeted
I ACCIDENTALLY OPENED MY CTO'S PERSONAL NOTION WORKSPACE AND NOW I UNDERSTAND WHY HE SHIPS 5X FASTER THAN THE REST OF US. He is 48. I am 26. He manages 3 products and never works past 5 PM. I work 10 hours a day and barely clear my Jira board. In his workspace, one specific document explained everything: Most people panic when the workload scales. They work longer hours, burn out, and eventually drop the ball. High performers do not manage time. They manage boundaries. The document was a list of strict operating rules. Here are 18 systems you can steal.
143
572
40
5,923
1,783,504
The reading list that taught me how to think about agentic architecture. Bookmark this. 1. Brewer's CAP Theorem (2000) — trade-off thinking 2. Netflix Hystrix docs — circuit breaker pattern 3. Martin Fowler: Saga Pattern — distributed rollback 4. The Twelve-Factor App — stateless service design 5. AWS Well-Architected Framework — blast radius thinking 6. "Thinking in Systems" — Donella Meadows 7. Designing Data-Intensive Applications — Kleppmann 8. Google SRE Book Ch.13 — cascading failures 9. OWASP LLM Top 10 (2025) — agent attack surfaces 10. Anthropic: Building Effective Agents (2024) 11. LangGraph docs — stateful agent patterns 12. Microsoft AutoGen paper — multi-agent orchestration 13. Gartner: Agentic AI Hype Cycle (2025) 14. EU AI Act Article 14 — human oversight requirements Classic distributed systems stuff. Applied to the next layer of the stack. Follow for annotated breakdowns → @asmah2107
11
88
606
35,793
Skip Coursera. Skip Udemy. Skip expensive playbooks. MIT has 11 amazing free AI courses: Sharing this great course compilation from Anisha Jain. 1. AI 101 Clear introduction to core AI ideas. Ideal if you’re starting from zero and want the big picture first. 🔗ocw.mit.edu/courses/res-6-01… 2. Introduction to Deep Learning Hands-on bootcamp covering neural networks and modern deep learning foundations. 🔗introtodeeplearning.com/ 3. Artificial Intelligence Covers problem-solving, knowledge representation, and machine learning fundamentals. 🔗ocw.mit.edu/courses/6-034-ar… 4. Introduction to Machine Learning Beginner-friendly overview of ML principles and essential algorithms you’ll actually use. 🔗openlearninglibrary.mit.edu/… 5. How to AI (Almost) Anything Explore how AI applies to music, art, perception, and creative systems. 🔗ocw.mit.edu/courses/mas-s60-… 6. Understanding the World Through Data Use data analysis and ML techniques to interpret real-world problems. 🔗edx.org/learn/data-science/m… 7. Artificial Intelligence in K-12 Education Foundations of AI technology and how it can shape learning environments. 🔗ocw.mit.edu/courses/6-s062-g… 8. Introduction to Algorithms A key prerequisite for building efficient AI systems and writing optimized code. 🔗ocw.mit.edu/courses/6-006-in… 9. Foundation Models and Generative AI Deep dive into modern AI systems (like ChatGPT) and how large models work. 🔗ocw.mit.edu/courses/6-s087-f… Focus on one AI track at a time. Dedicate 30–45 minutes daily and practice as you go. Apply your learning in small projects or real tasks to grow quickly. ♻️ Share this so more people can access these free resources. —— 📌 Get my top 100 infographics for free: 1) Follow me. 2) Subscribe to my free newsletter at WildCapital.co. You’ll receive them directly in your welcome email.
20
572
5
2,244
177,515
Nabil Ahmad retweeted
Best YouTube Channels To Learn in 2026 1. Cybersecurity – John Hammond 2. Artificial Intelligence – Andrej Karpathy 3. AI Research Breakdown – Yannic Kilcher 4. Web Development – The Net Ninja 5. Python Programming – Corey Schafer 6. DevOps – TechWorld with Nana 7. Cloud Computing – AWS re:Invent 8. Data Analytics – Luke Barousse 9. System Design – Gaurav Sen 10. Databases – Hussein Nasser 11. Low-Level Programming – The Cherno 12. Linux – Learn Linux TV 13. Networking – David Bombal 14. Math for ML – 3Blue1Brown
78
1,045
12
6,499
303,470
Nabil Ahmad retweeted
The most impressive change that AI caused is that now engineers are writing detailed specs
71
176
17
1,936
135,533
Nabil Ahmad retweeted
Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.
180
1,193
344
8,144
997,880