Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

TypeScript creator Anders Hejlsberg puts TypeScript 7 through its paces, compiling the 2.3M-line Visual Studio Code codebase in under five seconds, and breaking down how the new 10x faster Go-powered compiler and language service scales with shared-memory concurrency.

msdev's profile picture

Microsoft Developer

525,137 subscribers

41,539 görüntüleme • 2 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

The best thing about building in the open? Nothing gets lost. Anders Hejlsberg, creator of TypeScript and C#, on 12 years of issues and decisions, all searchable. "It didn't just disappear into some email I can't find anymore." Take a trip down memory lane and tell us: what was your first open source contribution?
0:53

The best thing about building in the open? Nothing gets lost. Anders Hejlsberg, creator of TypeScript and C#, on 12 years of issues and decisions, all searchable. "It didn't just disappear into some email I can't find anymore." Take a trip down memory lane and tell us: what was your first open source contribution?

GitHub

35,035 görüntüleme • 1 ay önce

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”
1:33

TypeScript was inspired by a strange ask from the outlook team. Anders Hejlsberg(Anders Hejlsberg) - creator of C#, TypeScript, Turbo Pascal & Delphi - tells us how TypeScript was born: “The world started building larger and larger applications in JavaScript. We saw that externally, but also internally. One of the trigger events was when the outlook team came to see the C# team and asked us whether we would pretty please productize this thing called Script#. And we go, well, what is Script#? It's this cross compiler that allows you to cross compile C# into JavaScript such that you can basically treat JavaScript as an instruction language and run your C# apps in a browser. Why would anyone want to do that? Well, because then you can get a grownup programming language with grownup tooling. You can use Visual Studio, you can have projects. You can do all of these wonderful things that you can't do with JavaScript because JavaScript is just the scripting language with shitty tooling. And we thought, well, perhaps a better approach would be to fix JavaScript. I mean, surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language”

The Pragmatic Engineer

116,193 görüntüleme • 2 ay önce

Code more intelligently in the terminal with the Language Server Protocol integration. Kiro CLI now has the same code understanding that powers the IDE. Pre-configured with 7 languages (TypeScript, Rust, Python, Go, Java, Ruby, C/C++), you can find references, navigate definitions, and get diagnostics all through natural language prompts. Just run /code init and ask. Learn more 👉
0:30

Code more intelligently in the terminal with the Language Server Protocol integration. Kiro CLI now has the same code understanding that powers the IDE. Pre-configured with 7 languages (TypeScript, Rust, Python, Go, Java, Ruby, C/C++), you can find references, navigate definitions, and get diagnostics all through natural language prompts. Just run /code init and ask. Learn more 👉

Kiro

12,703 görüntüleme • 7 ay önce

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”
1:16:01

Anders Hejlsberg (Anders Hejlsberg) is a living legend: he created Turbo Pascal, Delphi, C# and TypeScript (and today TypeScript is the most-used programming language, globally, as per GitHub.) Timestamps: 00:00 Intro 02:48 How Anders got into programming 05:40 Building his first compiler 07:44 Turbo Pascal 12:25 Delphi 14:53 Joining Microsoft 19:41 Building C# 29:11 Async/await 34:01 The rise of JavaScript 37:52 Building TypeScript 42:58 How the TypeScript compiler works 48:30 JavaScript’s strengths and weaknesses 52:18 How Anders uses AI 56:03 What language features work well with AI 1:02:49 How software craftsmanship is changing 1:07:49 Performance and efficiency 1:09:29 Anders’ tool stack 1:11:30 A 30-year career at Microsoft 1:13:40 Book recommendation Brought to you by: Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. WorkOS – Everything you need to make your app enterprise ready. turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. Four things that stood out to me: 1. “10x better for 1/10th of the price” is a proven winner. This is what Turbo Pascal did: it sold for $49.95 when competing compilers cost $500, and it was faster and more interactive than competitors’ products. Conveniently, the low price tag also killed off piracy 2. C# might have not existed without a famous court case. Microsoft originally hired Anders to architect its Java tools (Visual J++), but the Sun versus Microsoft lawsuit (1997-2001) meant Microsoft could not build on top of Java, as the company that owned Java’s IP (Sun) sued MS for alleged unauthorized changes to the Java language. Microsoft realized it had to build a new language that combined VB’s productivity with C++’s power. This led to C# and .NET. 3. TypeScript exists because Anders refused to build Script# for the Outlook .com team. Microsoft’s Outlook .com team asked Anders’ C# team to productize “ScriptSharp,” a language to cross-compile C# to JavaScript. Anders and the C# team pushed back, suggesting that a better approach was to fix JavaScript. Anders felt strongly that to be attractive to the best-of-breed developers in the JavaScript ecosystem, you want people to write JavaScript, and not another language like C#. 4. Designing a programming language is a 10-year play. As Anders puts it: “Version one is great, but has all sorts of issues. You’ve got to do version two, but it’s not until version three that it really starts to be great. Then you’ve got to convince people to adopt it.”

Gergely Orosz

129,192 görüntüleme • 2 ay önce

OpenAI Codex is now integrated directly in Visual Studio Code through the new Agent Sessions view - and can be powered by your GitHub Copilot subscription. Try it out now with VS Code Insiders and a Copilot Pro+ subscription. Happy coding!
0:32

OpenAI Codex is now integrated directly in Visual Studio Code through the new Agent Sessions view - and can be powered by your GitHub Copilot subscription. Try it out now with VS Code Insiders and a Copilot Pro+ subscription. Happy coding!

Visual Studio Code

335,037 görüntüleme • 9 ay önce

SEASON ON THE LINE. DOWN 1 WITH UNDER 10 SECONDS TO GO. GO-AHEAD 3 IN OT TO WIN GAME 6. RJ BARRETT AND THE RAPTORS FORCE GAME 7 IN EPIC FASHION!
0:25

SEASON ON THE LINE. DOWN 1 WITH UNDER 10 SECONDS TO GO. GO-AHEAD 3 IN OT TO WIN GAME 6. RJ BARRETT AND THE RAPTORS FORCE GAME 7 IN EPIC FASHION!

NBA

113,968 görüntüleme • 3 ay önce

Creator of C#, Anders Hejlsberg(Anders Hejlsberg), on the design goals that shaped the language and why standardisation was a goal from the beginning: “The overarching thing was this power and productivity of C++ with the ease of use of Visual Basic. We knew we wanted to build an object oriented language. We wanted managed code or byte code so we could target different runtime environments. We wanted garbage collection and exception handling, but also things like a unified object system where, and that's true in C#, anything can be assigned to an object. If it's a value type, we box it. And it's a self-describing object. So, reflection: you can ask an object, ‘what are you’? And you can get all of the facts about it at runtime, and you can dynamically manipulate it in ways that just don't exist in a lot of other environments. We wanted a language that made this new model of properties, methods and events first class because that was how components were built as opposed to just sort of functions and procedures and even objects. And we wanted to create a language that was standardised. We wanted to give this language to a standardisation committee and try to level the playing field there. And all of those things were sort of like what was rolled up in C#”
1:43

Creator of C#, Anders Hejlsberg(Anders Hejlsberg), on the design goals that shaped the language and why standardisation was a goal from the beginning: “The overarching thing was this power and productivity of C++ with the ease of use of Visual Basic. We knew we wanted to build an object oriented language. We wanted managed code or byte code so we could target different runtime environments. We wanted garbage collection and exception handling, but also things like a unified object system where, and that's true in C#, anything can be assigned to an object. If it's a value type, we box it. And it's a self-describing object. So, reflection: you can ask an object, ‘what are you’? And you can get all of the facts about it at runtime, and you can dynamically manipulate it in ways that just don't exist in a lot of other environments. We wanted a language that made this new model of properties, methods and events first class because that was how components were built as opposed to just sort of functions and procedures and even objects. And we wanted to create a language that was standardised. We wanted to give this language to a standardisation committee and try to level the playing field there. And all of those things were sort of like what was rolled up in C#”

The Pragmatic Engineer

18,332 görüntüleme • 2 ay önce

Before GenAI, prototyping an app, especially one powered by data or AI, meant hours of setup and boilerplate code before you could even test your idea. In this clip from the course Fast Prototyping of GenAI Apps with Streamlit, you’ll see how that changes. Watch how GenAI flips the development process, so instead of planning every step in advance, you start with intent and get working code in seconds. Learn to prototype faster, test more ideas, and go from concept to app. 👉 Take the course here: Snowflake Chanin Nantasenamat
2:33

Before GenAI, prototyping an app, especially one powered by data or AI, meant hours of setup and boilerplate code before you could even test your idea. In this clip from the course Fast Prototyping of GenAI Apps with Streamlit, you’ll see how that changes. Watch how GenAI flips the development process, so instead of planning every step in advance, you start with intent and get working code in seconds. Learn to prototype faster, test more ideas, and go from concept to app. 👉 Take the course here: Snowflake Chanin Nantasenamat

DeepLearning.AI

12,373 görüntüleme • 10 ay önce

🔥 New LangChain Academy Course: LangChain Essentials (Python & TypeScript) 🔥 Learn the basics of LangChain – our open source framework that makes it easy to start building agents with any model provider. Last week, we released LangChain 1.0. We’ve completely rewritten LangChain to be opinionated, focused, and powered by LangGraph’s runtime. It includes a new `create_agent` abstraction to build agents quickly, middleware for flexibility, and standard content blocks that work across any model provider. In this quickstart course, you'll learn how to: - Build an agent with the `create_agent` abstraction - Use LangChain’s core building blocks: Models, Messages, Memory, and Tools - Customize your agent with middleware - Debug and test your agent with LangSmith Observability & Evaluation Enroll for free ➡️
1:37

🔥 New LangChain Academy Course: LangChain Essentials (Python & TypeScript) 🔥 Learn the basics of LangChain – our open source framework that makes it easy to start building agents with any model provider. Last week, we released LangChain 1.0. We’ve completely rewritten LangChain to be opinionated, focused, and powered by LangGraph’s runtime. It includes a new `create_agent` abstraction to build agents quickly, middleware for flexibility, and standard content blocks that work across any model provider. In this quickstart course, you'll learn how to: - Build an agent with the `create_agent` abstraction - Use LangChain’s core building blocks: Models, Messages, Memory, and Tools - Customize your agent with middleware - Debug and test your agent with LangSmith Observability & Evaluation Enroll for free ➡️

LangChain

50,475 görüntüleme • 9 ay önce

Andrej Karpathy posted about the new programmable layer developers need to master: agents, subagents, prompts, contexts, memory, hooks, MCP. He said it came with no manual and everyone has to figure out how to hold it. This video is part of that manual. Hooks are one of the most underused features in Cursor and Droid, and they're what separate intentional AI-assisted development from hoping it works in production. After file edit: If the agent touches Rust code, hooks automatically regenerate TypeScript types for the frontend. If it touches TypeScript, ESLint runs with autofix. If it touches backend code, cargo clippy runs. On stop: When the agent finishes, it runs cargo check to validate the build before I even look at the output. 00:00 The problem: manually verifying AI-written code 00:31 Introducing hooks to automate tasks when files change 01:53 How hooks regenerate types for the frontend 02:24 How to set up the cursor.hooks.json file 04:44 Reviewing a more comprehensive hooks plan 05:48 Comparing FactoryDroid hooks vs Cursor hooks 06:45 Implementing the equivalent hooks in FactoryDroid 07:50 AI agent fixes a bug in the build command 08:27 How scaffolding makes the AI agent appear smarter 09:08 Demonstrating the successful hook implementation 09:53 Final insight: It's about providing guardrails, not a smarter AI
10:20

Andrej Karpathy posted about the new programmable layer developers need to master: agents, subagents, prompts, contexts, memory, hooks, MCP. He said it came with no manual and everyone has to figure out how to hold it. This video is part of that manual. Hooks are one of the most underused features in Cursor and Droid, and they're what separate intentional AI-assisted development from hoping it works in production. After file edit: If the agent touches Rust code, hooks automatically regenerate TypeScript types for the frontend. If it touches TypeScript, ESLint runs with autofix. If it touches backend code, cargo clippy runs. On stop: When the agent finishes, it runs cargo check to validate the build before I even look at the output. 00:00 The problem: manually verifying AI-written code 00:31 Introducing hooks to automate tasks when files change 01:53 How hooks regenerate types for the frontend 02:24 How to set up the cursor.hooks.json file 04:44 Reviewing a more comprehensive hooks plan 05:48 Comparing FactoryDroid hooks vs Cursor hooks 06:45 Implementing the equivalent hooks in FactoryDroid 07:50 AI agent fixes a bug in the build command 08:27 How scaffolding makes the AI agent appear smarter 09:08 Demonstrating the successful hook implementation 09:53 Final insight: It's about providing guardrails, not a smarter AI

Ray Fernando

60,884 görüntüleme • 7 ay önce

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."
3:13

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

The Pragmatic Engineer

13,258 görüntüleme • 1 ay önce

"I've spent $30K on a launch video, now you can make one with code." Here's my new episode with Bin Liu and Jake Moran, where they shared their 5-step playbook for using HyperFrames to make professional launch videos in Codex and Claude Code: 1. Gather video assets and create a frame.md 2. Create a storyboard.md with the scenes 3. Pull animations from the HyperFrames repo 4. Generate and review static frames 5. Build the video with HyperFrames Studio You can also start simple by using the built-in /website-to-video skill to one shot a launch video from any URL. HyperFrames is 100% free and I love how it democratizes video creation for everyone. 📌 Watch now: Thanks to our sponsors: Wispr Flow: 4x faster than typing with your voice Riverside: All-in-one AI studio for podcasts and video
0:43

"I've spent $30K on a launch video, now you can make one with code." Here's my new episode with Bin Liu and Jake Moran, where they shared their 5-step playbook for using HyperFrames to make professional launch videos in Codex and Claude Code: 1. Gather video assets and create a frame.md 2. Create a storyboard.md with the scenes 3. Pull animations from the HyperFrames repo 4. Generate and review static frames 5. Build the video with HyperFrames Studio You can also start simple by using the built-in /website-to-video skill to one shot a launch video from any URL. HyperFrames is 100% free and I love how it democratizes video creation for everyone. 📌 Watch now: Thanks to our sponsors: Wispr Flow: 4x faster than typing with your voice Riverside: All-in-one AI studio for podcasts and video

Peter Yang

68,646 görüntüleme • 1 ay önce

FireDucks makes Pandas 125x Faster... ...by changing JUST ONE LINE of code. Pandas has some major limitations: - Pandas only uses a single CPU core. - It often creates memory-heavy DataFrames. - Its eager (immediate) execution prevents global optimization of operation sequences. FireDucks is a highly optimized, drop-in replacement for Pandas with the same API. To use FireDucks: Remove this: ↳ import pandas as pd Add this: ↳ import fireducks.pandas as pd And you're done! ✔️ A performance comparison of FireDucks vs. DuckDB, Polars, and Pandas is shown in the video below. Official benchmarks indicate: - Modin: ~1.0x faster than Pandas - Polars: ~57x faster than Pandas - FireDucks: ~125x faster than Pandas I have shared a detailed article on this in next tweet! _____ Find me → Akshay 🚀 ✔️ For more insights and tutorials on ML and AI Engineering!
0:37

FireDucks makes Pandas 125x Faster... ...by changing JUST ONE LINE of code. Pandas has some major limitations: - Pandas only uses a single CPU core. - It often creates memory-heavy DataFrames. - Its eager (immediate) execution prevents global optimization of operation sequences. FireDucks is a highly optimized, drop-in replacement for Pandas with the same API. To use FireDucks: Remove this: ↳ import pandas as pd Add this: ↳ import fireducks.pandas as pd And you're done! ✔️ A performance comparison of FireDucks vs. DuckDB, Polars, and Pandas is shown in the video below. Official benchmarks indicate: - Modin: ~1.0x faster than Pandas - Polars: ~57x faster than Pandas - FireDucks: ~125x faster than Pandas I have shared a detailed article on this in next tweet! _____ Find me → Akshay 🚀 ✔️ For more insights and tutorials on ML and AI Engineering!

Akshay 🚀

218,990 görüntüleme • 1 yıl önce

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code
1:00:16

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 görüntüleme • 11 ay önce

New short course: Collaborative Writing and Coding with OpenAI Canvas! Explore new ways to write and code with OpenAI Canvas, a user-friendly interface that allows you to brainstorm, draft, and refine text and code in collaboration with ChatGPT. In the short course, created with OpenAI, and taught by , a research lead at OpenAI, you’ll learn to use Canvas to enhance your workflows. Canvas lets you go beyond simple chat interactions. It provides a side-by-side workspace where you and ChatGPT can edit and refine text or code collaboratively. This makes brainstorming, drafting, and iterating as you write feel more natural and effective. As the first major update to ChatGPT’s visual interface since its launch in 2022, Canvas gives a new, innovative approach to collaboration with AI. For instance, after writing the first version of your code, Canvas can review it and give suggestions for improvement. It can also help with debugging by adding logging, identifying problems to fix, and writing comments. In addition, you'll also learn what it takes to train the model for an interface like Canvas. In this video-only short course, you’ll: - Learn how to ask for in-line feedback and control the iteration of your work by directly editing selected areas of your text or code from the model’s output. - Learn how to access quick automation tools in a shortcut menu that allows you to modify your writing tone and length, enhance your code, and restore previous versions of your work. - Learn how to use Canvas as a research assistant tool with an example of asking the model to reason through the screenshot of a plot to write a research report, in which you can ask questions within the created report. - Ask the model to write Python code to replicate the graph seen on a screenshot image. - Go behind the scenes of how you can create a video game, such as Space Battleship, from scratch, edit it, and display it in one self-contained HTML file. - Get a real-world application example of creating a SQL database from the image of its architecture. - Understand the model training and design processes that power Canvas! Please sign up here:
1:49

New short course: Collaborative Writing and Coding with OpenAI Canvas! Explore new ways to write and code with OpenAI Canvas, a user-friendly interface that allows you to brainstorm, draft, and refine text and code in collaboration with ChatGPT. In the short course, created with OpenAI, and taught by , a research lead at OpenAI, you’ll learn to use Canvas to enhance your workflows. Canvas lets you go beyond simple chat interactions. It provides a side-by-side workspace where you and ChatGPT can edit and refine text or code collaboratively. This makes brainstorming, drafting, and iterating as you write feel more natural and effective. As the first major update to ChatGPT’s visual interface since its launch in 2022, Canvas gives a new, innovative approach to collaboration with AI. For instance, after writing the first version of your code, Canvas can review it and give suggestions for improvement. It can also help with debugging by adding logging, identifying problems to fix, and writing comments. In addition, you'll also learn what it takes to train the model for an interface like Canvas. In this video-only short course, you’ll: - Learn how to ask for in-line feedback and control the iteration of your work by directly editing selected areas of your text or code from the model’s output. - Learn how to access quick automation tools in a shortcut menu that allows you to modify your writing tone and length, enhance your code, and restore previous versions of your work. - Learn how to use Canvas as a research assistant tool with an example of asking the model to reason through the screenshot of a plot to write a research report, in which you can ask questions within the created report. - Ask the model to write Python code to replicate the graph seen on a screenshot image. - Go behind the scenes of how you can create a video game, such as Space Battleship, from scratch, edit it, and display it in one self-contained HTML file. - Get a real-world application example of creating a SQL database from the image of its architecture. - Understand the model training and design processes that power Canvas! Please sign up here:

Andrew Ng

128,180 görüntüleme • 1 yıl önce

Motion graphics were always the hardest part of making videos for me. Hours in After Effects for 10 seconds of movement. Now I can do them 10x faster without touching a timeline or writing a single line of code. Remotion released a skill that lets Claude Code create videos programmatically. I spent 5 hours building with it so I could show you exactly how it works. What's in the guide: - Installing the Remotion skill (takes 2 minutes) - Creating your first video scene by scene - Auto-editing long videos into clips - Adding animated captions and subtitles - Reframing for TikTok/Reels/Shorts - Stacking multiple skills into a mini production studio This is for content creators, marketers and GTM engineers who want to create more videos, better and faster, without learning video editing software or code. I recorded the full walkthrough. Every step. 👇 Comment "GUIDE" and I'll DM you the repo with all of the skills installed + getting started guide. (Make sure we're connected so I can DM you)
22:35

Motion graphics were always the hardest part of making videos for me. Hours in After Effects for 10 seconds of movement. Now I can do them 10x faster without touching a timeline or writing a single line of code. Remotion released a skill that lets Claude Code create videos programmatically. I spent 5 hours building with it so I could show you exactly how it works. What's in the guide: - Installing the Remotion skill (takes 2 minutes) - Creating your first video scene by scene - Auto-editing long videos into clips - Adding animated captions and subtitles - Reframing for TikTok/Reels/Shorts - Stacking multiple skills into a mini production studio This is for content creators, marketers and GTM engineers who want to create more videos, better and faster, without learning video editing software or code. I recorded the full walkthrough. Every step. 👇 Comment "GUIDE" and I'll DM you the repo with all of the skills installed + getting started guide. (Make sure we're connected so I can DM you)

JJ Englert

143,129 görüntüleme • 5 ay önce

Choose a model (any model) and build your application with it. Do not spend time swapping models early on. Do not try to optimize before you have a working system. This is one of the first recommendations I make to every new team I consult with. Eventually, it will be time to optimize the model. • You may need a cheaper model • You may need a faster model • You might need a smarter model Good luck if you stitched together 12 different APIs and SDKs from 7 different vendors. Over half of the companies I consult for run on Microsoft software and have access to Microsoft Foundry. Microsoft Foundry is a complete agentic ecosystem. If you're in that world and building AI applications, Microsoft Foundry is where everything lives: • Models (largest selection in the market) • Agentic SDK (Python, C#, JavaScript/TypeScript) • Tools • Evaluations • Monitoring They are fully integrated with GitHub and Visual Studio Code. The best part: Their agentic platform is fully agnostic of the models you use. You can integrate with any model using the same OpenAI-style API. Swapping one model for another takes 1 second.
3:49

Choose a model (any model) and build your application with it. Do not spend time swapping models early on. Do not try to optimize before you have a working system. This is one of the first recommendations I make to every new team I consult with. Eventually, it will be time to optimize the model. • You may need a cheaper model • You may need a faster model • You might need a smarter model Good luck if you stitched together 12 different APIs and SDKs from 7 different vendors. Over half of the companies I consult for run on Microsoft software and have access to Microsoft Foundry. Microsoft Foundry is a complete agentic ecosystem. If you're in that world and building AI applications, Microsoft Foundry is where everything lives: • Models (largest selection in the market) • Agentic SDK (Python, C#, JavaScript/TypeScript) • Tools • Evaluations • Monitoring They are fully integrated with GitHub and Visual Studio Code. The best part: Their agentic platform is fully agnostic of the models you use. You can integrate with any model using the same OpenAI-style API. Swapping one model for another takes 1 second.

Santiago

12,014 görüntüleme • 5 ay önce