Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

My 3rd online course is live! 🎉 I made this one because I kept getting the same question on my YT videos about Grafana MCP: how does this setup on my laptop become something I can actually run in production? There was almost no practical material, so I couldn't...

134,786 görüntüleme • 9 gün önce •via X (Twitter)

8 Yorum

Big Sheddy 🦅 profil fotoğrafı
Big Sheddy 🦅9 gün önce

congratulations bro

Nemanja Magic profil fotoğrafı
Nemanja Magic7 gün önce

My idolo!

Big Sheddy 🦅 profil fotoğrafı
Big Sheddy 🦅7 gün önce

ah I’m not worthy o, happy for you bro

catman profil fotoğrafı
catman9 gün önce

The best technical teaching connects the local demo to the production constraints, because that is where concepts like permissions, networking, and secrets become real.

rafiki profil fotoğrafı
rafiki9 gün önce

Congratulations and well done friend! So proud 🥰🥰

Nemanja Magic profil fotoğrafı
Nemanja Magic7 gün önce

❤️❤️

Obinna Ekwuno profil fotoğrafı
Obinna Ekwuno9 gün önce

Congratulations Man🙌🏾

Nemanja Magic profil fotoğrafı
Nemanja Magic7 gün önce

🙌🏾🙌🏾

Benzer Videolar

Almost 20 years later, AWS is still the most popular cloud in the world. The reason is simple: it just works! They have four services focused on Generative AI: 1. Amazon Q 2. Amazon Bedrock 3. SageMaker JumpStart 4. PartyRock I've been using AWS for around 15 years (honestly, I don't remember well), and their Developer Center is a gold mine. If you open their Developer Center, you'll find a new learning path, "Generative AI for Developers." I'm linking to it below. This is not just a course. This is a collection of courses, examples, videos, tutorials, and code walkthroughs. They will teach you how to use Generative AI on AWS using the four services above. ↑ That right there is a huge selling point: These classes aren't just theoretical. You'll have a chance to learn using the same professional tools everyone else uses. By the way, there are many more resources in the Developer Center: • Machine Learning • Data Operations • DevOps All of these are free. Click, click, and start learning right away. One more thing before I forget: If you are building anything with AWS, check out Amazon Q, their coding assistant. This is the *best* coding assistant for AWS-related work, and it's not even close. It's a Visual Studio Code extension. Install it, and it works like any other code assistant, except this one knows a lot about AWS. Thanks to AWS for sponsoring a post about their free courses and learning resources. There's a special place in Developer Heaven for you.

Santiago

22,104 görüntüleme • 1 yıl önce

I didn’t start my company NextLink Labs because I wanted to be a founder. I started it because production kept falling over and no one could explain why. At my last job, I was a solo developer on a critical system. Servers were going down. The service was unstable. Customers were feeling it. So I started digging. What I found wasn’t a bad engineer or a bad decision. It was something worse. The application was running on extremely old servers, filled with things that had nothing to do with the service. When I asked why we hadn’t migrated to the new servers we bought 18 months earlier, the answer stunned me: “We bought them… but no one knows how to set them up.” No documentation. No CI/CD. No infrastructure as code. No one actually knew what was running in production, so no one felt confident touching it. To make it harder, the servers were in Los Angeles. I was in Pittsburgh. I couldn’t even get hands-on to fix it myself. That was the moment it clicked. This wasn’t a one-off failure. This was how a lot of companies operated. I kept pushing for a better way. More structure. More clarity. Systems that didn’t rely on tribal knowledge. Eventually, I “wore out my welcome.” My manager didn’t fire me, but he did say, “Maybe you should do what you’re building on the side… full time.” Once I landed one more client, I resigned within four weeks. That was 11 years ago. Here's the lesson I took with me: Most outages aren’t caused by bad engineers. They’re caused by undocumented systems and neglected foundations. At NextLink Labs, everything we do comes back to that belief. Build systems people understand. Make infrastructure boring and predictable. And design for execution, not heroics. That’s how you scale without things constantly breaking.

Jordan Saunders

417,369 görüntüleme • 7 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,256 görüntüleme • 1 yıl önce

Ever since I wired Claude Code to WhatsApp 3 weeks ago, I built a stupidly large infra around it. I mean, opus built it. No clue how the code even looks. The entire thing was vibe coded using my phone. I wanted to see how far I could push it without touching the computer. Everything via WhatsApp. Build what I need on the fly. So the resulting infrastructure will already be battle tested for software development. The entire thing was streamlined with nearly no manual interventions, everything was communicated via WhatsApp using a single script establishing this connection. If the script is down, I need to get home to start it again to resume the development. Claude was upgrading it, debugging it, restarting it while maintaining constant uptime so it could keep communicating with me. I stressed Claude about it, telling it that it will be “in the dark” and other words that deliberately sound scary about losing communications if the script dies. I also refused git and refused cloning the code, I wanted to see Claude adapting to work on a *LIVING* system. The way this whole thing works: Claude has its own dedicated phone number that I am paying for. A real WhatsApp account for it is installed on a real iPhone that is sitting on my desk. All is registered under my name, this is legit setup with no hacks and tricks. I’ve set up a WhatsApp “Community” and multiple different groups under it. Both me and Claude are the admins, so Claude could edit it on my behalf. Each group is a project I am working on and has its own isolated context. The Group description is a system prompt that gets auto-appended to the larger system prompt explaining this setup in general. When I send a message it’s an instant interrupt to Claude Code’s process, just like in the terminal. Voice notes are seamlessly transcribed with a local Whisper model. Images are used with multimodal reading in an isolated parallel session. Multiple groups running in parallel so I can work on all projects at the same time. No cross-talking, everything has an isolated context and history. And because it’s local on my own machine: Everything is REAL. The browser is REAL. I am connected as myself on it to all services because I actually use it in real life. Claude has unlimited internet access, just like humans who use actual browsers. It utilizes custom-made browser tools that I made to control any browser session it wants. Depending on the situation, it can either connect to my existing session or create one for its own. (You can tell it ‘look at my browser for a sec’ then talk about the current page you are on and it just works, pretty cool) My custom browser tools are not perfect (not by a long shot) but I managed to make them work well to the point they are somewhat reliable. This gives Claude full access to my real creds and all the services I actually use. I’m productive AS HELL with this. It really feels like a personal assistant. I ask it to read my emails and msgs, check x .com for news, research arxiv papers, write code, run experiments for me, investigate and reverse engineer github repos, even use my credit card and order things. [I try not to do this one a lot lol so far no disasters]. All from my phone. Super convenient. This is not a product or an open source project (maybe soon of it will make sense). This is just an ugly script I hacked the entire thing is ~600 lines. (ok maybe i did look at the code, but i swear i didn’t edit!) You can also vibe code this from scratch pretty fast and it will probably even end up better. This is just a cool thing so I’m sharing. It is a real speed booster for many things I do on daily basis, mostly boring things. Forcing my routine into some new “agent platform” just didn’t feel right for me. WhatsApp is where I already communicate and look for messages, so I decided that my agents will live there too. AGI in my pocket 24/7.

Yam Peleg

420,390 görüntüleme • 9 ay önce

single most useful thing for my local ai setup that made life easy is my 2x DGX Spark becoming one serving box for every device i own here is how i do it: > 1. the two sparks run one vLLM server together with one endpoint, i use dgx sparks, you can use any nodes that can run an llm > 2. install tailscale to have all your nodes and machines on the same tailnet, the endpoint lives there so every device reaches it from anywhere and no port is open to the internet > 3. that one tailnet endpoint with the exposed port is your base url for everything, it speaks OpenAI chat, OpenAI Responses and Anthropic Messages, so any chat app, coding agent or phone bot you point at it talks to the same model > 4. the server also answers to the name "local", so clients can ask for "local" instead of a model name and when i swap the model on the servers nothing on the devices needs a config change. right now it's serving GLM 5.3-Flash, next week it can be something else this video below is the whole thing running end to end, orange dots are requests going in, white and green are tokens coming back it takes however many requests you throw at it, your config decides how many run at once and the rest wait their turn, when several run together each request's tok/s drops a bit while the box moves more tokens in total. mine is set to one at a time right now, so when every device fires together they queue up this setup really improved my quality of life with local ai, if you get stuck anywhere setting it up leave a comment and i'll help you

Sudo su

32,379 görüntüleme • 9 gün önce

If your MCP server has dozens of tools, it’s probably built wrong. You need tools that are specific and clear for each use case—but you also can’t have too many. This creates an almost impossible tradeoff that most companies don’t know how to solve. That’s why I interviewed my friend Alex Rattray (Alex Rattray), the founder and CEO of Stainless. Stainless builds APIs, SDKs, and MCP servers for companies like OpenAI and Anthropic. Alex has spent years mastering how to make software talk to software, and he came on the show to share what he knows. I had him on Every 📧’s AI & I to talk about MCP and the future of the AI-native internet. We get into: • Design MCP servers to be lean and precise. Alex’s best practices for building reliable MCP servers start with keeping the toolset small, giving each tool a precise name and description, and minimizing the inputs and outputs the model has to handle. At Stainless, they also often add a JSON filter on top to strip out unnecessary data. • Make complex APIs manageable with dynamic mode. To solve the problem of how an AI figures out which tool to use in larger APIs, Stainless switches to “dynamic mode,” where the model gets only three tools: List the endpoints, pick one and learn about it, and then execute it. • MCP servers as business copilots. At Stainless, Alex uses MCP servers to connect tools like Notion and HubSpot, so he can ask questions like, “Which customers signed up last week?” The system queries multiple databases and returns a summary that would’ve otherwise taken multiple logins and searches. • Create a “brain” for your company with Claude Code. Alex built a shared company brain at Stainless by keeping Claude Code running on his system and asking it to save useful inputs—like customer feedback and SQL queries—into GitHub. Over time, this creates a curated archive his team can query easily. • The future of MCP is code execution. Instead of giving models hundreds of tools, Alex believes the most powerful setup will be a simple code execution tool and a doc search tool. The AI writes code against an API’s SDK, runs it on a server, and checks the docs when it gets stuck. This is a must-watch for anyone who wants to understand MCP—and learn how to use them as a competitive edge. Watch below! Timestamps: Introduction: 00:01:14 Why Alex likes running barefoot: 00:02:54 APIs and MCP, the connectors of the new internet: 00:05:09 Why MCP servers are hard to get right: 00:10:53 Design principles for reliable MCP servers: 00:20:07 Scaling MCP servers for large APIs: 00:23:50 Using MCP for business ops at Stainless: 00:25:14 Building a company brain with Claude Code: 00:28:12 Where MCP goes from here: 00:33:59 Alex’s take on the security model for MCP: 00:41:10

Dan Shipper 📧

15,645 görüntüleme • 1 yıl önce