Загрузка видео...

Не удалось загрузить видео

На главную

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...

Pragmatic_Eng's profile picture

The Pragmatic Engineer

51,937 subscribers

116,346 просмотров • 5 месяцев назад •via X (Twitter)

Новости и политикаОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 4

Фото профиля sameer khan
sameer khan5 месяцев назад

@ahejlsberg “surely you're not going to be best of breed in the JavaScript ecosystem by telling people to write in a different programming language” This is where the genius lies.

Фото профиля Vlad Sazonau
Vlad Sazonau5 месяцев назад

@ahejlsberg well… that was an unexpected twist

Фото профиля Curious Coder
Curious Coder5 месяцев назад

@ahejlsberg Typescript made debugging and my life easier.

Фото профиля Sebastian Buzdugan
Sebastian Buzdugan3 месяцев назад

@ahejlsberg one design choice mattered more than outlook: gradual typing let existing javascript migrate incrementally

Похожие видео

Ever heard of Script#? Us neither, and that's probably a good thing. Anders Hejlsberg, creator of Turbo Pascal and Delphi, the lead architect of C#, and the designer of TypeScript, talks about how TypeScript came about from a need for "grown-up tooling" and the question "How can we fix JavaScript?" Watch the full interview 👉
1:31

Ever heard of Script#? Us neither, and that's probably a good thing. Anders Hejlsberg, creator of Turbo Pascal and Delphi, the lead architect of C#, and the designer of TypeScript, talks about how TypeScript came about from a need for "grown-up tooling" and the question "How can we fix JavaScript?" Watch the full interview 👉

GitHub

36,036 просмотров • 9 месяцев назад

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,894 просмотров • 5 месяцев назад

There's no divide between TypeScript and JavaScript. TypeScript loves JavaScript. Want to use JSDoc in JavaScript? TypeScript will help you out. Want to write ZERO types? TypeScript will still try its best to help. Here's me, Anders Hejlsberg and Ryan Cavanaugh 👉 searyanc.dev on bsky to explain.
2:09

There's no divide between TypeScript and JavaScript. TypeScript loves JavaScript. Want to use JSDoc in JavaScript? TypeScript will help you out. Want to write ZERO types? TypeScript will still try its best to help. Here's me, Anders Hejlsberg and Ryan Cavanaugh 👉 searyanc.dev on bsky to explain.

Matt Pocock

52,002 просмотров • 3 лет назад

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 просмотров • 5 месяцев назад

🚨 JAVASCRIPT JUST GOT A NATIVE COMPILER. Vercel Labs just built scriptc to turn TypeScript and JavaScript into native executables. No Node runtime required in the final binary. → Compile JS/TS → native executable → Emit C, LLVM IR, assembly, objects → Build WebAssembly modules → Use supported Node APIs → Bundle npm packages with --dynamic → Check exactly what can compile statically → Works across macOS, Linux, Windows + WASI The crazy part? scriptc build hello.ts -o hello ./hello You write JavaScript. You get a native binary. And it’s not just a demo — the project has its own native runtime and compiler pipeline. Vercel Labs calls it experimental, so this is still early-stage tech. 🔗 #Vercel #JavaScript #TypeScript #Compiler #WebAssembly #NodeJS #DeveloperTools #OpenSource #Programming
0:30

🚨 JAVASCRIPT JUST GOT A NATIVE COMPILER. Vercel Labs just built scriptc to turn TypeScript and JavaScript into native executables. No Node runtime required in the final binary. → Compile JS/TS → native executable → Emit C, LLVM IR, assembly, objects → Build WebAssembly modules → Use supported Node APIs → Bundle npm packages with --dynamic → Check exactly what can compile statically → Works across macOS, Linux, Windows + WASI The crazy part? scriptc build hello.ts -o hello ./hello You write JavaScript. You get a native binary. And it’s not just a demo — the project has its own native runtime and compiler pipeline. Vercel Labs calls it experimental, so this is still early-stage tech. 🔗 #Vercel #JavaScript #TypeScript #Compiler #WebAssembly #NodeJS #DeveloperTools #OpenSource #Programming

Vikas gupta

45,513 просмотров • 1 месяц назад

Code Execution If you ask Grok to generate code, you can quickly see how it runs in a “preview” tab. You can preview HTML snippets, run Python, C++, Javascript, Typescript and bash scripts.
0:24

Code Execution If you ask Grok to generate code, you can quickly see how it runs in a “preview” tab. You can preview HTML snippets, run Python, C++, Javascript, Typescript and bash scripts.

Grok

560,687 просмотров • 1 год назад

Why Microsoft didn't have LLMs do their recent Typescript native rewrite in Go Anders Hejlsberg (Creator of Typescript): "If we just let AI loose on, what is it, half a million lines of code that we have in the old compiler? Well, I don't know that that would absolve us from then having go in and carefully examining every line that came out of it to make sure that there were no hallucinations. Right. Unless you have 100% perfect test coverage, you probably still gotta go check all of that. Now I think a better approach, quite honestly, would be enlist AI to write a program that helps you translate from TypeScript to go, because at that point you can park the stochastic ness in that program and then you can get deterministic behavior whenever you run the program, which means you get the same transformation every time you run it. Right. That's always the thing about AI that people forget it's not deterministic. Right. So you can't really trust that it's going to do the same thing twice. For the full conversation, you can search Anders Hejlsberg's name on my YouTube, Spotify or Apple Podcasts (link in bio)
0:48

Why Microsoft didn't have LLMs do their recent Typescript native rewrite in Go Anders Hejlsberg (Creator of Typescript): "If we just let AI loose on, what is it, half a million lines of code that we have in the old compiler? Well, I don't know that that would absolve us from then having go in and carefully examining every line that came out of it to make sure that there were no hallucinations. Right. Unless you have 100% perfect test coverage, you probably still gotta go check all of that. Now I think a better approach, quite honestly, would be enlist AI to write a program that helps you translate from TypeScript to go, because at that point you can park the stochastic ness in that program and then you can get deterministic behavior whenever you run the program, which means you get the same transformation every time you run it. Right. That's always the thing about AI that people forget it's not deterministic. Right. So you can't really trust that it's going to do the same thing twice. For the full conversation, you can search Anders Hejlsberg's name on my YouTube, Spotify or Apple Podcasts (link in bio)

Ryan Peterman

84,913 просмотров • 2 месяцев назад

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 просмотров • 4 месяцев назад

How to build an AI agent from scratch. This is the question I get the most, so I recorded this video to show you from the very beginning how you can get started. You can do this in Python, TypeScript, JavaScript, or Ruby.
30:13

How to build an AI agent from scratch. This is the question I get the most, so I recorded this video to show you from the very beginning how you can get started. You can do this in Python, TypeScript, JavaScript, or Ruby.

Santiago

71,826 просмотров • 1 год назад

You can ask Opus 5.5 to write extreme music theory wankery and it will do it in javascript. Theory-porn as a genre? everything you see and hear is generated from javascript code that claude wrote. no samples, no libraries 🔊
0:24

You can ask Opus 5.5 to write extreme music theory wankery and it will do it in javascript. Theory-porn as a genre? everything you see and hear is generated from javascript code that claude wrote. no samples, no libraries 🔊

dadabots

44,295 просмотров • 1 месяц назад

Dive into the highlights from JavaScript Sessions Ankara 's "Internet of Things with JavaScript" event at Ankara TEKMER 📷 Thanks again, Barış Türe , for an informative and enjoyable presentation, and we hope to see you all soon! #internetofthings #javascript #event
0:29

Dive into the highlights from JavaScript Sessions Ankara 's "Internet of Things with JavaScript" event at Ankara TEKMER 📷 Thanks again, Barış Türe , for an informative and enjoyable presentation, and we hope to see you all soon! #internetofthings #javascript #event

Popupsmart

11,803 просмотров • 3 лет назад

Anders Hejlsberg ( Anders Hejlsberg ) is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering. In this episode: • How rewriting the compiler makes it 10x faster • Why they picked Go instead of Rust • Why they didn't use LLMs for the migration • Predictions on AI's impact on software engineering Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:48 Why write a compiler in JavaScript 07:29 Why rewrite the compiler in Go 14:49 LLMs for large migrations 20:12 Why Javascript is so popular 26:32 Why ever use Javascript on the backend 32:59 What it takes to build a programming language 37:06 Will there be fewer languages in 10 years 42:57 Hands on engineering vs delegation 49:14 Why fast tooling matters more now 51:16 AI software engineering predictions 58:52 The most technically challenging work 01:02:04 Top book recommendation 01:03:50 Advice for his younger self 01:05:00 Outro
1:05:57

Anders Hejlsberg ( Anders Hejlsberg ) is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering. In this episode: • How rewriting the compiler makes it 10x faster • Why they picked Go instead of Rust • Why they didn't use LLMs for the migration • Predictions on AI's impact on software engineering Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsors of this episode for supporting my work: • WorkOS: makes your app Enterprise Ready with easy to use APIs to add SSO, SCIM, RBAC, and more in just a few lines of code, check them out at • Jira by Atlassian: Get more work done with your favorite agents and models all in one place, check them out at Chapters: 00:00 Intro 00:48 Why write a compiler in JavaScript 07:29 Why rewrite the compiler in Go 14:49 LLMs for large migrations 20:12 Why Javascript is so popular 26:32 Why ever use Javascript on the backend 32:59 What it takes to build a programming language 37:06 Will there be fewer languages in 10 years 42:57 Hands on engineering vs delegation 49:14 Why fast tooling matters more now 51:16 AI software engineering predictions 58:52 The most technically challenging work 01:02:04 Top book recommendation 01:03:50 Advice for his younger self 01:05:00 Outro

Ryan Peterman

104,338 просмотров • 2 месяцев назад

i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS
0:59

i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS

Rebane

1,078,247 просмотров • 8 месяцев назад

Bjarne Stroustrup (Creator of C++) on the costs of abstraction: "It's compiled away. This is why I talk about zero overhead abstraction. And people are beginning to take me to task for that because that's underestimating the ability of the C++ compiler. We can do negative overhead abstraction." Ryan: "What if you're really good at writing assembly and had all the time in the world to write it?" Bjarne: "If you are very smart and you have infinite time, you can do better. By and large, we are not as smart as the optimizers anymore, and we don't have infinite time."
0:36

Bjarne Stroustrup (Creator of C++) on the costs of abstraction: "It's compiled away. This is why I talk about zero overhead abstraction. And people are beginning to take me to task for that because that's underestimating the ability of the C++ compiler. We can do negative overhead abstraction." Ryan: "What if you're really good at writing assembly and had all the time in the world to write it?" Bjarne: "If you are very smart and you have infinite time, you can do better. By and large, we are not as smart as the optimizers anymore, and we don't have infinite time."

Ryan Peterman

145,117 просмотров • 5 месяцев назад

I asked Luke Kornet about his memories from stretches where he was a DNP for many games in a row, and what his message is to the young guys who find themselves in that position now: “It's just a lot of peace to come to life of accepting the position that you're in and then just doing the best with that, versus trying to fight it and want to be in a different one.” “You can spend a lot of time worrying about things that you can't really control. But when you just take the opportunity that you have and do the best with that, you can have days like today where a lot of guys came in and were able to contribute. You can have peace about knowing that you did your job well, just as you did the day before, the day after. It might just look a different way every time. I feel like that's what I've been taught through my life. That's the only thing attitude that you can have that you can actually do something with – versus trying to control things that are outside of what you can control.”
2:15

I asked Luke Kornet about his memories from stretches where he was a DNP for many games in a row, and what his message is to the young guys who find themselves in that position now: “It's just a lot of peace to come to life of accepting the position that you're in and then just doing the best with that, versus trying to fight it and want to be in a different one.” “You can spend a lot of time worrying about things that you can't really control. But when you just take the opportunity that you have and do the best with that, you can have days like today where a lot of guys came in and were able to contribute. You can have peace about knowing that you did your job well, just as you did the day before, the day after. It might just look a different way every time. I feel like that's what I've been taught through my life. That's the only thing attitude that you can have that you can actually do something with – versus trying to control things that are outside of what you can control.”

Noa Dalzell 🏀

48,992 просмотров • 1 год назад

Learn JavaScript in 72 steps for FREE 💥 In this list of resources, I've curated all JavaScript topics for you stepwise. You do not need to pay a single dollar to learn JavaScript. Get it 🚀 ↓
0:54

Learn JavaScript in 72 steps for FREE 💥 In this list of resources, I've curated all JavaScript topics for you stepwise. You do not need to pay a single dollar to learn JavaScript. Get it 🚀 ↓

Ajay Yadav

53,654 просмотров • 3 лет назад

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."
2:04

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,073 просмотров • 5 месяцев назад

We can just decide that our world should be different. That modern JavaScript can be made with #nobuild. That SaaS services can move out of the cloud. That Apple is not the end of history.
1:15

We can just decide that our world should be different. That modern JavaScript can be made with #nobuild. That SaaS services can move out of the cloud. That Apple is not the end of history.

DHH

242,388 просмотров • 6 месяцев назад

Our first Generative AI short course in JavaScript! GitHub recently reported that JavaScript is again the world’s most popular programming language. To support web developers exploring and developing with generative AI, we just launched a new short course in JavaScript taught by Jacob Lee, founding engineer at . In ​​Build LLM Apps with LangChain.js you’ll learn elements common in AI development, including: (i) Using data loaders to pull data from common sources such as PDFs, websites, and databases (ii) Prompts, which are used to provide the LLM context (iii) Modules to support RAG such as text splitters and integrations with vector stores (iv) Working with different models to write applications that are not vendor-specific (v) Parsers, which extract and format the output for your downstream code to process You’ll also build with the LangChain Expression Language, which lets you easily compose sequences (also called chains) of modules to perform complex tasks using LLMs. Putting all this together, you’ll also work on a conversational question-answering LLM application capable of using external data as context. Please sign up here:
3:07

Our first Generative AI short course in JavaScript! GitHub recently reported that JavaScript is again the world’s most popular programming language. To support web developers exploring and developing with generative AI, we just launched a new short course in JavaScript taught by Jacob Lee, founding engineer at . In ​​Build LLM Apps with LangChain.js you’ll learn elements common in AI development, including: (i) Using data loaders to pull data from common sources such as PDFs, websites, and databases (ii) Prompts, which are used to provide the LLM context (iii) Modules to support RAG such as text splitters and integrations with vector stores (iv) Working with different models to write applications that are not vendor-specific (v) Parsers, which extract and format the output for your downstream code to process You’ll also build with the LangChain Expression Language, which lets you easily compose sequences (also called chains) of modules to perform complex tasks using LLMs. Putting all this together, you’ll also work on a conversational question-answering LLM application capable of using external data as context. Please sign up here:

Andrew Ng

284,512 просмотров • 2 лет назад