Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

ADSP: Algorithms + Data Structures = Programs

ADSP: Algorithms + Data Structures = Programs artwork

Episode 190: C++, Python and More with Kevlin Henney

Jul 12, 202429 minAudio

In this episode, Conor and Bryce chat with Kevlin Henney about C++, Python and more! Link to Episode 190 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Twitter ADSP: The Podcast Conor Hoekstra Bryce Adelstein Lelbach About the Guest Kevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know. Show Notes Date Recorded: 2024-07-11 Date Released: 2024-07-12 When zombies attack! Bristol city council ready for undead invasion ACCU Conference 97 Things Every Programmer Should Know (GitHub) 97 Things Every Programmer Should Know 97 Things Every Java Programmer Should Know C++Now 2018: Ben Deane “Easy to Use, Hard to Misuse: Declarative Style in C++” When to Use a List Comprehension in Python Intro Song Info Miss You by Sarah Jansen https://soundcloud.com/sarahjansenmusic Creative Commons - Attribution 3.0 Unported - CC BY 3.0 Free Download / Stream: http://bit.ly/l-miss-you Music promoted by Audio Library https://youtu.be/iYYxnasvfx8

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Kevlin HenneyParticularly when you're dealing with a language like C, where it doesn't have guide rails or guardrails. In other words, there's no implicit guidance in the language design. You can do anything you want, but let's go back to the axe conversation. Yeah, cutting your hand off is also an option. Um, you know, uh, and we talk about foot guns and things like that. Yeah, playing your foot off, why why stop at the foot? You know, just just just just take out the whole limb.

ConorWelcome to ADSP the podcast, episode 190, recorded on July 11th, 2024. My name is Connor, and today with my co-host Bryce, we interview Kevlin Henney and we chat about C Python, zombie apocalypses, and more. Note that this is part one of what will probably be a four or five part series.

BryceWell, uh, the listener really just missed out on some uh I mean I had props even.

ConorYeah, we will uh I mean we'll start with our introduction now, but we just spent what uh what's the timestamp? 20 minutes? So I mean, technically we might be able to piece together half of an episode from just Bryce's side of the conversation. Uh, but then uh you'll miss out on everything that Kevlin said. We were talking about what are the topics we covered? We covered uh AI apocalypse, zombie apocalypse.

BryceWait, wait, we covered how training neural nets is hard. Yeah.

ConorData acquisition, especially in the form of videos. Uh your son's admiration and aspiration for axes and more.

BryceI'm not sure if the Henny plan, the Henny family, the uh zombie apocalypse apocalypse clan.

Kevlin HenneyYeah, we we we have it all. Um, you know, and uh and that all kind of connected together um with uh we then ended up with talking about forests and and uh and uh uh different population density.

BryceI insulted the cities of Cambridge and Oxford in Cambridge just accidentally.

Kevlin HenneyYeah, Cambridge accidentally, and then we went back and made sure that you know uh and actually tied that together with zombies. But also, yeah, there's uh there was a little bit in there about uh you've got iodine tablets for radiation, which is what I do. Yeah. Um uh and actually Bryce initially said opened with I'm not really a prepper, and then revealed actually um that perhaps he was and just had not yet acknowledged it and then was masking.

BryceI'm the Manhattan version of a prepper because Manhattanites have no space. And so if you're a Manhattanite prepper, you can't have a bunker, you can't like stock up on like lots of stuff. You have to be space efficient about it. And I I have the space efficient prepper things.

Kevlin HenneyYeah, so you know, that there's all of these things. We talked about the uh the relative efficiency that the the LLM model, you know, you need a lot of training data. That's that's the thing that we see. They are uh LLMs are you know, the modern this paradigm of AI is thirsty for data and for power. Um, but maybe humans, that's one thing, that's a trick that we might want to think about in terms of optimization, is that humans do an awful lot with far less training data and a lot less energy consumption. And and uh you know, so that that's that's potentially an interesting direction.

Kevlin HenneyAnd that all related back to uh your girlfriend learning Swift, bizarrely enough. Yes, um, and wanting to do something with it in an AI system.

BryceUh the type of tennis shot that you're making. And uh this is the per point where a Connor can insert earlier audio.

Kevlin HenneySo, and of course, when we were talking when we the the zombie apocalypse thing was also related to the fact that um uh we we ended up talking about I mean we started off with robot apocalypse or the AI apocalypse, um, and then I said actually we might be strangely prepared in Bristol, because Bristol City Council um uh over ten years ago actually issued a plan for um uh the event of a zombie or undead invasion, and you can actually find it if you Google Bristol City Council Zombie Plan.

BryceI do wonder like why did they do this?

Kevlin HenneyI think it was somebody was bought, you know, sitting in the council office, they kind of put together two or three pages, just brief, um, and uh you know, but that that and we do actually have there for a number of years, and I don't think it's restarted since the pandemic, but there was a there's a zombie walk kind of once a year. Um uh and you know, honestly, the difference between the zombie walk and a standard Saturday night in the centre of Bristol, difficult to distinguish, I have to confess. But uh, you know, that there's a kind of thing there. So there's a kind of an association there, and uh, you know, Bristol marches to the beat of a very different drum sometimes, but having a zombie plan was kind of cool, I have to admit.

Kevlin HenneyEven if done huge just in jest.

BryceI do have to ask, we we had this really nice dinner when we were in Bristol, and it was on like uh uh Tuesday or Wednesday, and it was this very nice restaurant, there was nobody else there. And this and there were a bunch of restaurants where like they were just like closed during the weekdays. Do people not like eat out in Bristol during the weekdays? Is that just not a thing?

Kevlin HenneyUh it is, but it depends where you were, because the so that would have been the OCCU conference, the ICU conference. Yes. And I'm gonna guess you were within five to ten minutes walk of the hotel.

BryceFifte minutes or so.

Kevlin HenneyYeah, fifteen minutes, yeah. So it depends on the direction that you went, but the chances are in the centre of Bristol, you've got um I mean that's that's April, early, middle of the week, centre of Bristol, you're not likely to find as many people. In fact, it's a great time to go for dinner. Um, you're more likely to find people eating out later in the week or elsewhere in Bristol. So the centre of Bristol is more likely to empty out, and particularly certain parts, particularly those near um uh the uh conference hotel, uh, tend to be much more business district, and so you don't tend to have people hanging around as much.

Kevlin HenneyUm whereas Thursday onwards in the centre it tends to get a lot busier, um, but generally later uh early in the week, if people are going out, uh it tends to be much more local, so you're gonna be in different parts of Bristol. So, yeah, in other words, if you're visiting Bristol and you want to make sure that you can get somewhere nice for dinner, then go into the centre because people aren't going to be there if it's it's early in the week. That clearly doesn't work for December. There are Christmas parties um all over the place, but uh uh that's actually quite a good uh uh strategy. Go to the places that people don't go in the evening.

BryceSo we should what what what is the what is the big business pause, pause, pause before we we we still haven't introduced Kevin.

ConorI mean uh our 98% of our listeners know who you are, Kevlin, uh, because I think you've come up I don't know, handful of times. I like to mention your talks now and then, but a brief introduction. Writer, speaker, independent consultant, uh you are probably most well known for both some of your books, all of your books, and your talks. I mean, I for a while used to gift uh 97 things every programmer should know whenever I would leave a company, which I've only done twice, I guess, but I would, for the people that you know I wanted to say goodbye to, uh, that was the go-to book that I would give people.

ConorI would love to say that like these are my top five favorite things from it.

BryceI have to admit, I've never, I've never, I've never even.

ConorYou're famously a not a book or podcast person, though. So you don't listen to podcasts, you don't read books.

BryceSee, I I I know Kevlin for his excellent talks and of course his famous witty humor.

ConorBut yes, 97, I was gonna say, uh, I'd love to rattle off the top four or five, uh, but it was like, I want to say a few years ago. Oh, please. Well, no, I was gonna say I can't because it was like 20, I want to say it was like 2016 that I read the book. I'm not sure if that lines up with roughly when it came out. I had like a t a few of them that I really, really liked, but now it's been like close to a decade that like I've internalized that stuff, and it's just like a part of the way that I program. And I know that um a lot of them overlapped with my favorite talk of yours, which I told you when we met in CraftConf back in May, um, which was declarative thinking, declarative practice.

ConorThere's uh a ton of stuff in that talk that like really influenced the way that I was writing C at the time, because C famously is not, I mean, you can code any way you want in C, but a lot of this stuff that you get out of the box doesn't uh, you know, it's not immutable by default, like Rust or some other language, right? Um anyway, so we will we will link uh some of the books. Uh there's also I I think the Java version of the 97 Things book.

Kevlin HenneyYeah, that that we were talking about the pandemic um earlier on, and um in fact during the during the pre-conversation, um Bryce in his non-prepper mode was basically saying he had a whole load of N95 marks masks before the pandemic, and that was actually air quality in California influencing that. Um uh and uh so therefore that gets to talking about the pandemic. The the Java version of the 97 Things um book was finished in the first wave of lockdowns. Um uh because what else are you gonna do?

Kevlin HenneyUm so it's me and Trisha G. Trisha used to work for JetBrains. Um and then kind of after that I got a I got a I got a call, I got a I got a message from Peter Somerlad, who uh may be known to some of the the listeners. Um Peter's um been involved in C forever. Um and uh particularly some some committee work, unit testing, um stuff that he's done, uh refactoring uh work that he's done.

Kevlin HenneyBut uh Peter uh was interested in oh, maybe there'll be interest in doing a C version, and I unfortunately I Riley worked quite on board with that at that particular point, which is a shame. Um but the 97 Things thing, uh that book actually came out in 2010, so yeah, it predates to predates 2016 by quite a way, and it is um the thing I quite like about that, although I like the Java one I can and and and uh the same if I did a C one or a Python one or whatever.

Kevlin HenneyThe the funny thing about choosing a specific technology is by definition, the technology is going to date. And I'm not saying that um the the general programmer one is timeless, but because it was trying to um because I told people, okay, what do you want to tell other people? This is the idea. People volunteered things, you know, it was it was very um kind of open submission uh type of approach. Uh by definition, they're not anchoring on.

Kevlin HenneyWell, here you are, you're using uh you're currently using C 98, this is what you're gonna do, or you are currently using Java 6, and this is what you're gonna do. So I'm just rescaling the timeline trying to get my versions right, or you're considering using Python 3, 2010, probably won't. You're using Python 2.3 or 2.4. The point there is that that wasn't the goal of the book. It was like, I don't know who I'm speaking to, but they code. That's yeah, what can I tell them? So, what the interesting thing is that only four years after the Java ones come out, um it's probably dated more in some ways than the 97 Things Every Programmer should because the Java one is specifically talking about this version, this framework, this whatever.

Kevlin HenneyUm, and the a C one would have a similar issue because you'd probably have somebody submitting saying, Hey, you're gonna program modern C. Let's pretend that let's pretend that we started uh uh developing that book this year. Um that means that uh you'd have some people saying, Oh, well, maybe we should be pushing C23, but other people say, Oh, you still gotta get on board with 17 and 20. But if I'm reading this in five years' time, 17 and 20 is looking much further in the rearview mirror, and I'm thinking, well, that's over a decade ago. Um and suddenly it's become dated, and the notion of modern has shifted, and there's that constantly moving window.

Kevlin HenneySo the curious thing is that the 2010 book, if you read it in 2016, doesn't seem that doesn't seem that old, but even less than six years after the Java one came out, you can already see the a gap opening up because it's trying to speak to a specific technology. So there's kind of an interesting thing there, and I think it appeals to uh and you were saying kind of that you kind of internalize things, and I think that that's that's the thing, is that it is intentionally about the underlying principles rather than some of the technical specifics that I could go and easily look up in the readme or online somewhere.

Kevlin HenneySo there's it had they the books I guess have slightly different goals, but they also have different aging properties.

ConorYeah, no, it's it's super interesting. Uh and I I haven't read the Java one, but I would definitely think that the 97, uh like the original one, it has just like a lot of the advice given is timeless advice. It's not, like you said, attached to any version or uh is gonna, you know, ten years from now be no longer like some of it's uh very generic, but like I I remember too at the time, like you sort of go through at some point in your career, like you are learning the style that you like to code in. And at the time I was reading it, like I hadn't fully uh you know concretized the way that I like to write code.

ConorBut then like you start to read books like that, and that talk is well, declarative thinking and declarative practice. And there's another one by Ben Dean uh that covers a lot of the same stuff uh called uh what is his called? It's easy to use, hard to misuse, uh like applying declarative thinking or something like that. And like both of those talks, it just showed a way to write C that is not like the default, and it makes it more robust. And uh and anyways, like a few years after that though, I had kind of like settled on like you know, you've seen enough code, you've reviewed enough PRs, and like I very quickly can be like look at a PR and code someone's written and be like, this is I really, really like this, this is high quality code, and then this other stuff, it's like even if it's it's written but just formatted a certain way, it it's like instantly gives you like chills or something.

Kevlin HenneyI'm I'm sure both of you have had that experience when everything is possible, but you don't necessarily have a quality filter in that sense. You don't or you don't know why something is good. And and I think particularly when you're dealing with a language like C where it doesn't have guide rails or guardrails, in other words, there's no implicit guidance in the language design. Right. You can do anything you want, but let's go back to the axe conversation. Yeah, cutting your hand off is also an option, um, you know, uh, and we talk about foot guns and things like that. Yeah, blowing your foot off, why stop at the foot?

Kevlin HenneyYou know, just just just just take out the whole limb.

BryceThe point there is, but you see, see there's that one person who has that very important use case where cutting their their foot off gets them an extra 5% formant. And so you know, we have to have the acts.

Kevlin HenneyAnd we have to have that. So therefore, yeah, and and that uh and so there is that issue that because there isn't uh and it's interesting dealing with different kinds of language programming language cultures, and I think that's actually one of the really interesting things is is the when you look at how people use languages, it's often a cultural thing.

BryceYeah.

Kevlin HenneyIt's not a national culture, but it is there are um so one of the things uh early in my career I worked uh I think most yeah, initially my C ⁇ was under Windows, uh was under Windows, then I went and um and then I was working on Unix and um X Windows, and it was really and and therefore, you know, uh um POSIX standards and all kinds of stuff, and it was really interesting just looking, it's like okay, here's the same language, but already the influences and the way that people think about their just everything from naming to um uh error reporting conventions and things like that was already shaped by the context they were in.

Kevlin HenneySo it was one language, but two very different cultures already well defined, and these days we have an even larger spread. Um, and there isn't quite the normalizing characteristic, anything is possible, but that also is a real challenge for anybody working, and particularly anybody working with code that has been developed over many eras, because you've got all these different eras of language and what is received good practice, and then you've got the individual preferences or the backgrounds of the developers who came in. Um, whereas when you look in the Java space, it's uh I'm not gonna say it's all it's uniform, but there's a much stronger uh core culture, and again, you kind of get the thing.

Kevlin HenneyI think Python's interestingly um uh caught between a couple of extremes. There's a very strong core sense of Pythonic, but Python is also everybody's favourite second language, and they're and a lot of people that are Python tourists, so sometimes you stumble across code that you go, like, yeah, this is elegant, this is Pythonic, this is kind of like the received wisdom, and then you step outside that and you're looking, and it's just like okay, this person is definitely a tourist, they've obviously got the code, they're they're thinking from in a scripting sense, they're using a common subset of the language, and they're kind of just making something work, but that the it's not their primary language, and that shows, um, and they're kind of making do, and they've got a very kind of uh imperative style, even though Python actually allows you to be a lot more expressive than that.

Kevlin HenneyGoing back to Connor's observations about the kind of declarative style of thinking, you can be highly economic in Python, but you can also be staggeringly verbose. Um, and and that that's the you know, and that's it it's from where people are coming from, and that I think is really interesting and is a challenge, I think, for anybody coming into any language is what is the received culture there, um, and how well is it supported as being considered normal. Um, but then also how much ti how does time affect this?

Kevlin HenneyYounger languages have less variation over time. Whereas, but if I picked up a book, you know, I'm just gonna looking over at my C bookshelf, and it's kind of like if I pick up one of those books, I've got so uh if I pick up a book from the early 90s, then its idea of good is gonna be really different from the stuff that's coming out in the early 2000s, it's gonna be different to what is coming out now, and it's like you any legacy code base, that's a real challenge for anybody, isn't it? They're coming into it and it's going like, okay, the file started in the late 90s, and here I am in the 2020s, and I've got everything in between.

Kevlin HenneyUm, and the I think that's a challenge for people working with C when they're learning it, because you know, it's such a large language. It's a case of like, well, what do you teach? And you you almost have to ask the person where are you coming from? Because if you are writing code for yourself or you're writing code for a new project, actually my response may be very, very different to somebody saying, Oh yeah, we're working on uh you know drivers that we've been maintaining since the year 2000, then you are low level, you are historical, you're probably not much past C.

Kevlin HenneyYou know, it's just like it's kind of like it's kind of it's tidy C with a sprinkling of a few C features, um, but it's probably quite imperative and it's quite low level, and it it bears more, it has more in common with C coding style than it does with what somebody would be saying, hey, guess what? You can do this with C23. Um and so you're it's kind of like, am I learning old, am I learning Anglo-Saxon or am I learning modern uh uh uh modern English? Um, you know, it it's it the variation to be that huge, and knowledge of one doesn't necessarily gift you with ability in the other.

BryceYeah, the the this idea of languages have a culture, having a culture is actually very interesting. I I I've been doing more Python stuff at work recently, and in particular trying to figure out how do we go about doing things in a Pythonic way. And it's it's so fascinating to me that that in Python they have this term. They they've coined this term to mean like the way that we do things, you know, like the proper way. And it's really like Pythonic is their culture. And again, so I was talking with my girlfriend the other day about this, and I was telling me, like, it's like we don't have the term for that in C Plusy Plus, we just say like modern C Plus plus.

BryceShe suggested, and I think this is a great term. C plusy. And I kind of like that because it's C plus plusy doesn't sound so good, but C plus C sounds good. But um yeah, it's it's um it's interesting where a lot of the people um do Python. Like 20 or 30 year veterans. Uh they have 20 year veterans of Python.

BryceUm there are people who were C people until um C. They have background C. Um, and then they um became Python people. Um it's not true of all of them, but but some of the folks that I work with in the in a conversation with everyone's like, I feel like Python, like I feel like I don't know how like what the property things in Python is like I don't feel like I necessarily know that either, but we just sort of figure it out as we go along.

BryceAnd it's like we look at how we write Python code for uh GPUs, and we look at it and be like, is this really the Python way, or is this just sort of a way of writing C style code in Python? And is that what we really want? I have to I have to make a timing note for it for kind of which is kind of about five minutes ago. I can't put some audio clock.

BryceTriMe. And uh I I think I I got up real nice and close. I didn't capture the entire TriMe sequence, but uh you'll want to go edit that in maybe for the intro. I don't know.

ConorIf it shows up, I'll I'll do something with it. Back to you, Kevlin.

Kevlin HenneyYeah, I I but that idea that uh particularly where you have this kind of like uh mixed culture, people come from one, they go to another, um, I think is interesting because uh it it it shapes the way you think, um, it shapes the way you phrase stuff. Um, and you know, different people respond in different ways to it, and it's a it's about how you want to learn and integrate integrate knowledge from one language into another um or how you work. And sometimes you compartmentalize things and go, oh, I'm definitely this is you know, sometimes people go, Oh, I've got one way of programming and I'm gonna use that in all languages, and sometimes that pushes the limits of what is considered normal in the other language, and you know, your colleagues are looking at that going, well, that's pretty weird.

Kevlin HenneyThat's you know, oh, I'm using I'm using a C idium here. It's like, well, we call that bad Python where I come from. So you end up with what might be considered good in one case, actually ends up being weird or bad in another. But at the same time, having something from another place can also offer you a solution that you simply wouldn't have come across. You it it that's just a way of thinking. You know, it's just like the kind of the grooves and the grooves were not aligned that way. That's not the way your thinking worked. But if you were working in Python, you go, well, hang on, I would I would do this like this.

Kevlin HenneyI would I would use a comprehension here. Now, what would that mean if I'm working um in C? Well, oh, actually, maybe if I think in terms of ranges and lambdas, that gets me close, but that's a very different way of approaching the problem. And so you've got these these ideas of um differences of expression, but then you have the idea of well, what's the normal culture here? Um, I was talking funny enough, I was talking yesterday to um uh Mike Luchides. Um, he's um an editor at uh O'Reilly, given that we were talking about 97 things earlier.

Kevlin HenneyAnd um uh myself and Mike have uh we we have a call like every two or three weeks. We've been doing that since 2020. We originally started as a pandemic thing, and we've just kind of kept it going. And we talk about all kinds of stuff. We talk about AI, programming language trends, um, you know, what's what's really happening in the workspace, um, you know, is the metaverse a thing that people are genuinely, you know, where's this gonna go? Uh, you know, uh cyber hype, all this kind of stuff. Yeah. So we we were talking about various things, and he was saying, well, I've uh he said, I've been looking at a whole load of Python code, and I'm not seeing a lot of use of comprehensions.

Kevlin HenneyUm and so a comprehension is basically a very tidy, it's a mathematical concept ultimately, it comes from uh set intentions, um, and so set theory and uh uh predicate uh calculus and stuff like that. And you find comprehension forms, you know, very uh pretty much uh pick a pick a um a functional programming language and it'll do that elegantly and directly. Um and that but that's not something that we see in our more imperative languages, it's kind of been brought in later in Python.

Kevlin HenneyWhen they introduced it in Python, it's become very much part of the core language, it integrates with the Syndax nicely, it feels like it was always there, it hasn't always been there. Um, but other languages, when we look at C, it kind of we're having to sort of nudge around and sort of approach it and say, well, you can do this like this, but there's no kind of core concept there. And so there is this idea that suddenly it's become very present in the core Python style. Well, yeah, maybe it has, maybe it hasn't. It's the received or the communicated wisdom on Python.

Kevlin HenneyBut what um but what Mike was saying says, yeah, when I look around a lot of open source Python, I don't see a lot of use of this. I see a lot of imperative style coding. Everybody's firing up their for loops and their variables rather than going, like, you know, I've got a simple expression that just like initializes this the way you want it, and then we can get on with our real work. Whereas instead, what you've got is like, oh, actually, for loops, that's our real work. And you've got all of this stuff that's set up and it distracts from the main purpose of the code, which goes back actually to what Conor was saying in terms of the declarative style.

Kevlin HenneyThe declarative is just like I just want to say this and I want to know that there's machinery or library behind the scenes that gets this done. Um, I don't need to say it again, I don't need to be more explicit about how I'm setting up. That's not my that's not my main goal here. Um, is I want to get uh there's a clear narrative, a simple message, and I want to get that um uh across and use abstraction mechanisms that are available. But what Mike was saying is he says, yeah, when I go out into the wild and look at Python in general, I'm not seeing people using um these constructs that allow them this economy and this direct expression.

BryceWell, I think it's it's a direct expression, but I would argue that um list comprehensions in Python, I think, are more complex and not as like newcomer friendly as just writings and for loops. Um like like the the this inten especially if you've got like you know like all this comprehension where you've got like a um like an if-else in there too.

BryceUm like it gets to be it can get to be pretty unc I think unintuitive maybe.

Kevlin HenneyUm it's possible to make these things um more complex, and I'm never gonna debate that. Um but I think it depends on where the newcomer comes from. Um I was gonna say the same thing.

BryceBut most of them come from most people come from their imperative programming background.

Kevlin HenneyYeah, and and so their instinct in that, and that's the point is they reach for that tool. So it's yeah, it's not that it's not beginner-friendly, it's just that the the grooves of their thinking are aligned on a slightly different way. But when you kind of show, oh yeah, actually this is a really in fact, let me give you an example that's not Python, not C, but actually Fortran. Um I uh so for I presume I must have done something in a past life that was terrible and wicked. Um but I've ended but early in my career, I am old enough that I've ended up actually you know programming Fortran uh and being paid to do it.

Kevlin HenneyAnd uh I which Fortran dialect.

ConorBe sure to check these show notes either in your podcast app or at adspthepodcast.com for links to anything we mentioned in today's episode, as well as a link to a GitHub discussion where you can leave thoughts, comments, and questions. Thanks for listening. We hope you enjoyed and have a great day.

BryceLow quality, high quality, that is the tagline of our podcast.

ConorIt's not the tagline. Our tagline is chaos with sprinkles of information.

Open the transcript file

Hosts and Guests

Guests

  • Kevlin Henney Guest Inferred

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 313: C++26 Reflection vs CRTP, AI, Kids & More with Zach Laine

    Nov 20, 202647 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about C++26 Reflection vs CRTP, AI, kids & more. Link to Episode 313 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP:...

    • Apple Podcasts

    Credit the people on this episode

  2. Episode 312: The C++26 Contracts Fiasco

    Nov 13, 202652 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about the C++26 contracts fiasco. Link to Episode 312 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode

  3. Episode 311: Career Changes, GPUs & More with Zach Laine

    Nov 6, 202628 minAudio

    In this episode, Conor and Bryce talk with Zach Laine about his career and the career changes he has made. Link to Episode 311 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials...

    • Apple Podcasts

    Credit the people on this episode

  4. Episode 310: Leaving NVIDIA for... ?

    Oct 30, 202624 minAudio

    In this episode, Conor and Bryce talk about Bryce's next chapter and where he is leaving NVIDIA for. Link to Episode 310 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The...

    • Apple Podcasts

    Credit the people on this episode

  5. Episode 309: Default Construction & CppCon 2026 with Jason Turner

    Oct 23, 202629 minAudio

    In this episode, Conor and Ben chat with Jason Turner about default construction in C++. Link to Episode 309 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode