Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

GergelyOrosz's profile picture

Gergely Orosz

343,256 subscribers

128,953 Aufrufe • vor 1 Monat •via X (Twitter)

BildungWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

115,602 Aufrufe • vor 1 Monat

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 Aufrufe • vor 5 Monaten

Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's Anders Hejlsberg explanation from his Wes Bos interview:
4:13

Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's Anders Hejlsberg explanation from his Wes Bos interview:

Travis Fischer

583,816 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 1 Monat

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

51,998 Aufrufe • vor 2 Jahren

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 Aufrufe • vor 24 Tagen

Bjarne Stroustrup is the creator of C++ and a former researcher at Bell Labs at its peak. I interviewed him about: • What made Bell Labs different • Programming language design: types, memory safety, bootstrapping • When abstraction improves performance • Anecdotes from building C++ • Thoughts on AI writing C++ • Mistakes he'd change while building C++ Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsors for supporting my work: • Cursor 3: a unified workspace for building software with agents, check it out at • 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 Timestamps: 0:00 - Intro 0:50 - The origin of C++ 8:46 - What Bell Labs was like 17:24 - Dennis Ritchie 24:00 - When to build a programming language 31:59 - Bootstrapping a language 33:58 - C++ is not object-oriented 37:32 - Discussing type systems 46:20 - Memory safety 49:26 - Standards committee anecdotes 1:09:40 - Adding automatic garbage collection to C++ 1:18:25 - Template instantiation is Turing complete 1:21:57 - Abstraction and performance 1:28:51 - AI writing code 1:35:54 - His motivation 1:39:18 - Famous quotes 1:46:48 - Reflecting on building C++ 1:49:12 - Top C++ book recommendation 1:50:59 - Advice for his younger self 1:58:06 - Outro
1:59:03

Bjarne Stroustrup is the creator of C++ and a former researcher at Bell Labs at its peak. I interviewed him about: • What made Bell Labs different • Programming language design: types, memory safety, bootstrapping • When abstraction improves performance • Anecdotes from building C++ • Thoughts on AI writing C++ • Mistakes he'd change while building C++ Where to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript: Thank you to this episode's sponsors for supporting my work: • Cursor 3: a unified workspace for building software with agents, check it out at • 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 Timestamps: 0:00 - Intro 0:50 - The origin of C++ 8:46 - What Bell Labs was like 17:24 - Dennis Ritchie 24:00 - When to build a programming language 31:59 - Bootstrapping a language 33:58 - C++ is not object-oriented 37:32 - Discussing type systems 46:20 - Memory safety 49:26 - Standards committee anecdotes 1:09:40 - Adding automatic garbage collection to C++ 1:18:25 - Template instantiation is Turing complete 1:21:57 - Abstraction and performance 1:28:51 - AI writing code 1:35:54 - His motivation 1:39:18 - Famous quotes 1:46:48 - Reflecting on building C++ 1:49:12 - Top C++ book recommendation 1:50:59 - Advice for his younger self 1:58:06 - Outro

Ryan Peterman

321,659 Aufrufe • vor 1 Monat

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,011 Aufrufe • vor 1 Monat

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 Aufrufe • vor 4 Monaten

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 Aufrufe • vor 10 Tagen

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.
11:41

Most C Programmers don't have a clue as to how the CPU works. Here is a lecture from my course on the C Language that introduces how to visualise the CPU as a C (or general software) Programmer.... More Details are at: Being able to model the behaviour of CPU provides a solid base to reason about your code. The summary is - - The CPU is a state machine which maintains it's states in registers. - It has busses to memory for requesting data/instruction read/writes. - Interrupts to attend to events. I discuss this and more in my course on the C Language.

Piyush Itankar

28,019 Aufrufe • vor 1 Jahr

On this week’s GitHub Podcast, we talked about how Typescript became the #1 programming language on GitHub. Now hear from the creator, Anders Hejlsberg. 👀 Get his thoughts on this year’s Octoverse findings. 💭⬇️
5:31

On this week’s GitHub Podcast, we talked about how Typescript became the #1 programming language on GitHub. Now hear from the creator, Anders Hejlsberg. 👀 Get his thoughts on this year’s Octoverse findings. 💭⬇️

GitHub

30,986 Aufrufe • vor 8 Monaten

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.
1:05:52

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. • Sentry – application monitoring software considered “not bad” by millions of developers Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Gergely Orosz

51,575 Aufrufe • vor 1 Monat

Why was #TypeScript created? Amanda Silver explains why Microsoft created the language to bring structure, scalability, and a better developer experience to large web apps. TypeScript repo:
1:40

Why was #TypeScript created? Amanda Silver explains why Microsoft created the language to bring structure, scalability, and a better developer experience to large web apps. TypeScript repo:

Microsoft Dev Docs

16,369 Aufrufe • vor 2 Monaten

There are few people who have impacted the software engineering industry like Kent Beck 🌻 has. He'd never before told his career story from start to today in one sitting - until now. What a treat. Timestamps: 00:00 Intro 03:47 Human engineers aren’t going away 08:00 Kent's path into tech 13:50 Undergraduate and graduate studies 17:21 Kent’s first programming job 18:54 The rise and fall of Smalltalk 27:04 Working with Ward Cunningham 37:36 Design patterns 44:05 Working at Apple 51:08 CRC Cards 59:29 Testing tools in the language 1:04:22 The C3 project with Martin Fowler 1:09:54 Extreme Programming 1:16:25 Developing TDD 1:25:07 Writing the Agile Manifesto 1:30:00 Agile’s impact 1:32:40 Agile’s downside 1:37:32 The Dotcom Bust 1:44:30 Lessons from working at Facebook 1:59:44 Kent’s ‘Good to Great’ program at Facebook 2:06:07 Soft skills engineers need to learn 2:09:30 AI and the challenges of acceleration 2:15:53 Explore, expand, extract 2:22:33 What Kent is excited about Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable • WorkOS – everything you need to make your app enterprise ready Kent shared so many previously untold stories - like how he was fired from Apple (!!), how he and Ward Cunningham used a thesaurus to find the right words, how the Agile Manifesto came together. My favorite reflection from is this though: The human part is the most important one in software engineering. As Kent explained: “This is the biggest cosmic, practical joke ever. As young people, we were promised: “Okay, here’s this computer and once you’ve completely understand this computer, you’ll be fine. That’s all you need to do.” So I set out the first part of my career just to become the best programmer that I could be because that’s what it would take to be successful. And then you realize: sorry, there’s this whole human side. Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings. And those are exactly the skills that I thought I didn’t need to learn! So I was promised: just understand the computer and you’ll be successful. And then someone went “just kidding, understand people!” And now I was in a position of being ten years behind.”
2:28:43

There are few people who have impacted the software engineering industry like Kent Beck 🌻 has. He'd never before told his career story from start to today in one sitting - until now. What a treat. Timestamps: 00:00 Intro 03:47 Human engineers aren’t going away 08:00 Kent's path into tech 13:50 Undergraduate and graduate studies 17:21 Kent’s first programming job 18:54 The rise and fall of Smalltalk 27:04 Working with Ward Cunningham 37:36 Design patterns 44:05 Working at Apple 51:08 CRC Cards 59:29 Testing tools in the language 1:04:22 The C3 project with Martin Fowler 1:09:54 Extreme Programming 1:16:25 Developing TDD 1:25:07 Writing the Agile Manifesto 1:30:00 Agile’s impact 1:32:40 Agile’s downside 1:37:32 The Dotcom Bust 1:44:30 Lessons from working at Facebook 1:59:44 Kent’s ‘Good to Great’ program at Facebook 2:06:07 Soft skills engineers need to learn 2:09:30 AI and the challenges of acceleration 2:15:53 Explore, expand, extract 2:22:33 What Kent is excited about Brought to you by: • Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages • turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable • WorkOS – everything you need to make your app enterprise ready Kent shared so many previously untold stories - like how he was fired from Apple (!!), how he and Ward Cunningham used a thesaurus to find the right words, how the Agile Manifesto came together. My favorite reflection from is this though: The human part is the most important one in software engineering. As Kent explained: “This is the biggest cosmic, practical joke ever. As young people, we were promised: “Okay, here’s this computer and once you’ve completely understand this computer, you’ll be fine. That’s all you need to do.” So I set out the first part of my career just to become the best programmer that I could be because that’s what it would take to be successful. And then you realize: sorry, there’s this whole human side. Your ability to affect change in the world is gated by your ability to communicate with, to soothe, to understand other human beings. And those are exactly the skills that I thought I didn’t need to learn! So I was promised: just understand the computer and you’ll be successful. And then someone went “just kidding, understand people!” And now I was in a position of being ten years behind.”

Gergely Orosz

26,364 Aufrufe • vor 9 Tagen

Take any Python code and build a dynamic GUI on top of it by dragging and dropping components. Python is already the most popular language in the world. This makes it even better! The attached video is only 45 seconds. It will show you how it works. Here is the important part: You can now build an interface for your Python code without learning HTML, JavaScript, or CSS. Go to this link to try this: Remember to work smarter, not harder! Thanks to the team behind Taipy for partnering with me on this post.
0:45

Take any Python code and build a dynamic GUI on top of it by dragging and dropping components. Python is already the most popular language in the world. This makes it even better! The attached video is only 45 seconds. It will show you how it works. Here is the important part: You can now build an interface for your Python code without learning HTML, JavaScript, or CSS. Go to this link to try this: Remember to work smarter, not harder! Thanks to the team behind Taipy for partnering with me on this post.

Santiago

155,179 Aufrufe • vor 2 Jahren

"Find the stuff that's boring and uninteresting, but you know still costs you, and try to get AI to do that for you." TypeScript's creator, Anders Hejlsberg, on how AI should get rid of all the toil you deal with when coding. Watch the full interview.
0:57

"Find the stuff that's boring and uninteresting, but you know still costs you, and try to get AI to do that for you." TypeScript's creator, Anders Hejlsberg, on how AI should get rid of all the toil you deal with when coding. Watch the full interview.

GitHub

39,948 Aufrufe • vor 2 Monaten

For Anders Hejlsberg, it was finding that rare thing in the 70's: A high school that offered access to computers.
0:45

For Anders Hejlsberg, it was finding that rare thing in the 70's: A high school that offered access to computers.

GitHub

13,930 Aufrufe • vor 5 Monaten

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsor 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 Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self
1:27:52

Simon Peyton Jones is the co-creator of Haskell (pure functional programming language) and I interviewed him about functional programming, why it matters, and his thoughts on other programming languages. In this episode: • Useful and useless programming languages • Rust vs C • Haskell vs OCaml • Why functional programming matters • Static languages and their value for LLMs • Why Excel is his 2nd favorite programming language Where to watch: • YouTube - • Spotify - • Apple Podcasts - • Transcript - Thank you to the sponsor 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 Chapters: 00:00 - Intro 00:39 - What functional programming is 09:18 - Downsides of functional programming 10:53 - Specialized hardware for functional programming 21:47 - Haskell is useless 25:59 - Rust vs C 28:26 - Haskell vs OCaml 35:26 - Side effects in Haskell 44:26 - Type systems 57:30 - How the Haskell compiler works 01:04:35 - Why Haskell is talked about more than used 01:09:07 - Avoiding success at all costs 01:11:12 - LLMs and programming languages 01:13:57 - New programming language design 01:15:59 - Should students continue to learn programming 01:22:33 - Why Excel is is 2nd favorite programming language 01:25:04 - Advice for his younger self

Ryan Peterman

127,146 Aufrufe • vor 1 Monat