Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Introducing OpenReview An AI code review system I'm building to learn how real systems work. No noise. No generic comments. Just reviews that actually understand your code. Open source. Currently in build. Everything I'm exploring: • AI PR reviews with real context • Full repo indexing (embeddings + vector...

11,249 görüntüleme • 3 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Massive breakthrough here! Someone fixed every major flaw in Jupyter Notebooks. The .ipynb format is stuck in 2014. It was built for a different era - no cloud collaboration, no AI agents, no team workflows. Change one cell, and you get 50+ lines of JSON metadata in your git diff. Code reviews become a nightmare. Want to share a database connection across notebooks? Configure it separately in each one. Need comments or permissions? Too bad. Jupyter works for solo analysis but breaks for teams building production AI systems. Deepnote just open-sourced the solution (Apache 2.0 license) They've built a new notebook standard that actually fits modern workflows: ↳ Human-readable YAML - Git diffs show actual code changes, not JSON noise. Code reviews finally work. ↳ Project-based structure - Multiple notebooks share integrations, secrets, and environment settings. Configure once, use everywhere. ↳ 23 new block - SQL, interactive inputs, charts, and KPIs as first-class citizens. Build data apps, not just analytics notebooks. ↳ Multi-language support - Python and SQL in one notebook. Modern data work isn't single-language anymore. ↳ Full backward and forward compatibility: convert any Jupyter notebook to Deepnote and vice versa with one command. npx @ deepnote/convert notebook.ipynb Then open it in VS Code, Cursor, WindSurf, or Antigravity. Your existing notebooks migrate instantly. Their cloud version adds real-time collaboration with comments, permissions, and live editing. I've shared the GitHub repo link in the replies! It's 100% open-source.

Akshay 🚀

33,358 görüntüleme • 7 ay önce

What they don't tell you about vibe coding: • Moltbook exposed 1.5M auth tokens. The owner hadn't written a single line of code. • Tea App leaked 72,000 government IDs. The database was just open, no sophisticated hack needed. • A researcher took control of a journalist's computer through her own vibe-coded game, without a single click. The code ran fine in all three cases, tests passed, reviews looked clean, and nothing raised a flag. That's the problem nobody is talking about. Teams are shipping faster than ever. AI writes the code. CI catches build failures. Tests catch regressions. Observability catches outages. But nobody is asking the one question that actually matters: What can an attacker do with this, right now? Because the bottleneck is no longer writing code. It's understanding what that code actually exposes once it's live. PR reviews miss auth edge cases. Unit tests don't probe broken access control. Staging environments don't simulate adversarial behavior. And business logic flaws look completely fine until someone decides to break them on purpose. Strix is an open-source tool that fills this gap. It reviews your running app the way an attacker would: - Crawls the app and maps every exposed route and flow - Probes abuse paths dynamically, not just at build time - Returns findings with proof-of-concepts and suggested fixes Strix was benchmarked against 200 real companies and open-source repos, where it found 600+ verified vulnerabilities including assigned CVEs. It's designed to fit into how modern teams already work. Run it before a release, after major changes, or continuously as the app evolves. If your team is shipping AI-generated code and you don't currently have a way to answer "what does this actually expose", it's worth looking at. GitHub link in the next tweet.

Akshay 🚀

52,377 görüntüleme • 3 ay önce

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,010 görüntüleme • 1 yıl önce