Podcasts about Debugging

  • 545PODCASTS
  • 961EPISODES
  • 47mAVG DURATION
  • 5WEEKLY NEW EPISODES
  • Oct 6, 2025LATEST
Debugging

POPULARITY

20172018201920202021202220232024

Categories



Best podcasts about Debugging

Show all podcasts related to debugging

Latest podcast episodes about Debugging

Crazy Wisdom
Episode #495: The Black Box Mind: Prompting as a New Human Art

Crazy Wisdom

Play Episode Listen Later Oct 6, 2025 57:49


In this episode of Crazy Wisdom, host Stewart Alsop talks with Jared Zoneraich, CEO and co-founder of PromptLayer, about how AI is reshaping the craft of software building. The conversation covers PromptLayer's role as an AI engineering workbench, the evolving art of prompting and evals, the tension between implicit and explicit knowledge, and how probabilistic systems are changing what it means to “code.” Stewart and Jared also explore vibe coding, AI reasoning, the black-box nature of large models, and what accelerationism means in today's fast-moving AI culture. You can find Jared on X @imjaredz and learn more or sign up for PromptLayer at PromptLayer.com.Check out this GPT we trained on the conversationTimestamps00:00 – Stewart Alsop opens with Jared Zoneraich, who explains PromptLayer as an AI engineering workbench and discusses reasoning, prompting, and Codex.05:00 – They explore implicit vs. explicit knowledge, how subject matter experts shape prompts, and why evals matter for scaling AI workflows.10:00 – Jared explains eval methodologies, backtesting, hallucination checks, and the difference between rigorous testing and iterative sprint-based prompting.15:00 – Discussion turns to observability, debugging, and the shift from deterministic to probabilistic systems, highlighting skill issues in prompting.20:00 – Jared introduces “LM idioms,” vibe coding, and context versus content—how syntax, tone, and vibe shape AI reasoning.25:00 – They dive into vibe coding as a company practice, cloud code automation, and prompt versioning for building scalable AI infrastructure.30:00 – Stewart reflects on coding through meditation, architecture planning, and how tools like Cursor and Claude Code are shaping AGI development.35:00 – Conversation expands into AI's cultural effects, optimism versus doom, and critical thinking in the age of AI companions.40:00 – They discuss philosophy, history, social fragmentation, and the possible decline of social media and liberal democracy.45:00 – Jared predicts a fragmented but resilient future shaped by agents and decentralized media.50:00 – Closing thoughts on AI-driven markets, polytheistic model ecosystems, and where innovation will thrive next.Key InsightsPromptLayer as AI Infrastructure – Jared Zoneraich presents PromptLayer as an AI engineering workbench—a platform designed for builders, not researchers. It provides tools for prompt versioning, evaluation, and observability so that teams can treat AI workflows with the same rigor as traditional software engineering while keeping flexibility for creative, probabilistic systems.Implicit vs. Explicit Knowledge – The conversation highlights a critical divide between what AI can learn (explicit knowledge) and what remains uniquely human (implicit understanding or “taste”). Jared explains that subject matter experts act as the bridge, embedding human nuance into prompts and workflows that LLMs alone can't replicate.Evals and Backtesting – Rigorous evaluation is essential for maintaining AI product quality. Jared explains that evals serve as sanity checks and regression tests, ensuring that new prompts don't degrade performance. He describes two modes of testing: formal, repeatable evals and more experimental sprint-based iterations used to solve specific production issues.Deterministic vs. Probabilistic Thinking – Jared contrasts the old, deterministic world of coding—predictable input-output logic—with the new probabilistic world of LLMs, where results vary and control lies in testing inputs rather than debugging outputs. This shift demands a new mindset: builders must embrace uncertainty instead of trying to eliminate it.The Rise of Vibe Coding – Stewart and Jared explore vibe coding as a cultural and practical movement. It emphasizes creativity, intuition, and context-awareness over strict syntax. Tools like Claude Code, Codex, and Cursor let engineers and non-engineers alike “feel” their way through building, merging programming with design thinking.AI Culture and Human Adaptation – Jared predicts that AI will both empower and endanger human cognition. He warns of overreliance on LLMs for decision-making and the coming wave of “AI psychosis,” yet remains optimistic that humans will adapt, using AI to amplify rather than atrophy critical thinking.A Fragmented but Resilient Future – The episode closes with reflections on the social and political consequences of AI. Jared foresees the decline of centralized social media and the rise of fragmented digital cultures mediated by agents. Despite risks of isolation, he remains confident that optimism, adaptability, and pluralism will define the next AI era.

Infinite Machine Learning
LLMs, Vibe Coding, and Security | Idan Plotnik, CEO of Apiiro

Infinite Machine Learning

Play Episode Listen Later Sep 30, 2025 37:36 Transcription Available


Idan Plotnik is the CEO of Apiiro, an application security platform built for the AI era. They've raised $135M in funding from investors like Greylock, Kleiner Perkins, and General Catalyst.Idan's favorite books: Zero to IPO (Author: Frederic Kerrest)(00:01) Introduction (00:07) How LLMs Generate Code(02:11) Rise of Vibe Coding: Opportunities and Risks(05:24) Debugging and Security in Vibe Coding(09:13) Vulnerabilities Introduced by AI Code Assistants(12:20) Security Basics for Builders Using AI and Cloud Platforms(15:44) Security by Design and Organizational Standards(18:08) Making Security Dead Simple: The Appiro Approach(22:28) Winning Developer Trust Through UX and Integration(26:59) Biggest Technical and GTM Challenges in Building Appiro(33:55) Rapid Fire Round--------Where to find Idan Plotnik: LinkedIn: https://www.linkedin.com/in/idanplotnik/--------Where to find Prateek Joshi: Newsletter: https://prateekjoshi.substack.com Website: https://prateekj.com LinkedIn: https://www.linkedin.com/in/prateek-joshi-infiniteX: https://x.com/prateekvjoshi 

Software Sessions
Elizabeth Figura on Wine and Proton

Software Sessions

Play Episode Listen Later Sep 24, 2025 64:07


Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

GOTO - Today, Tomorrow and the Future
Building a Debugger • Sy Brand & Tim Misiak

GOTO - Today, Tomorrow and the Future

Play Episode Listen Later Sep 19, 2025 36:12 Transcription Available


This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereSy Brand - Author of "Building a Debugger" and C++ Developer Advocate at MicrosoftTim Misiak - Systems Engineer at Datadog and Co-Founder of AugmendRESOURCESSyhttps://bsky.app/profile/tartanllama.xyzhttps://x.com/tartanllamahttps://github.com/TartanLLamahttps://uk.linkedin.com/in/sy-brand-36520857https://sybrand.inkhttps://blog.tartanllama.xyzTimhttps://bsky.app/profile/timdbg.comhttps://x.com/timmisiakhttps://github.com/timmisiakhttps://www.linkedin.com/in/tim-misiakhttps://www.timdbg.comLinkshttps://dwarfstd.orghttps://lldb.llvm.orghttps://rr-project.orghttps://undo.ioDESCRIPTIONTim Misiak interviews Sy Brand about their book "Building a Debugger". Sy, who has a background in GPU compilers and debuggers, discusses how implementing a debugger offers profound insights into computer systems.The conversation explores the unexpected complexities of debugging fundamentals like stack unwinding and code stepping. They examine how debugging interfaces have evolved and the challenges posed by backward compatibility and language evolution.Sy highlights areas for future advancement in debugging, particularly time travel debugging for non-deterministic issues and better tools for debugging optimized code. Throughout the interview, both experts share fascinating technical details that reveal why debugger implementation serves as an excellent path to deeper understanding of operating systems and hardware.RECOMMENDED BOOKSSy Brand • Building a DebuggerCathy O'Neil • Weapons of Math DestructionCrossing BordersCrossing Borders is a podcast by Neema, a cross border payments platform that...Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Mornings with Carmen
Allegiance to God and love of country - Dan Darling | Suicide and debugging our narrative code - Rick Lawrence

Mornings with Carmen

Play Episode Listen Later Sep 16, 2025 48:59


Cultural analyst Daniel Darling, author of "In Defense of Christian Patriotism," offers a balance to what it means to be a faithful member of God's Kingdom while also loving the country God has placed you well.  Vibrant Faith's Rick Lawrence, author of "The Suicide Solution: Finding Your Way Out of Darkness," talks about how help those dealing with dark self-narratives and suicidal ideation.  How do we help them debug their minds and re-program their thoughts with God's truth about them.   Faith Radio podcasts are made possible by your support. Give now: Click here

Hashtag Trending
Why AI Isn't Getting the Benefits It Should: Project Synapse

Hashtag Trending

Play Episode Listen Later Sep 13, 2025 68:41 Transcription Available


Harnessing AI: From Improving Code to Tackling Real-World Problems - Episode Highlights In this engaging episode of Hashtag Trending Project Synapse, our panel discusses the multitude of ways AI is being implemented today. Hosts John Pinard, Marcel Ganger, and Jim Love explore topics from AI's role in therapy and companionship, generating code, improving organizational tasks, to the use of AI in everyday life such as cooking and learning. They delve into the challenges faced by companies in measuring the financial benefits of AI, emphasize the importance of treating AI as a coworker rather than just a tool, and highlight real-world use cases like generating menus for a small-town restaurant. This episode is packed with insights, practical advice, and suggestions for harnessing AI to solve both complex and mundane problems in innovative ways. 00:00 Introduction and Panel Welcome 00:15 Challenges and Misconceptions of AI Implementation 01:16 Personal Experience with AI in Content Creation 05:26 The Two Camps of AI Utilization 07:08 Financial Benefits and Productivity Gains 07:59 The Importance of Quality Over Financial Metrics 11:44 Sales and Marketing in the Age of AI 20:28 Implementing AI: Practical Steps and Real-World Examples 24:30 The Role of AI in Business Strategy 29:15 Overcoming Resistance to AI Adoption 33:39 Incremental Improvements and Problem Solving with AI 36:41 AI as a Tool and Coworker 38:08 AI in Programming: Productivity and Collaboration 40:35 The Role of AI in Debugging and Problem Solving 45:04 AI's Impact on Learning and Everyday Tasks 47:43 Top Uses of AI in 2025 58:59 Challenges and Solutions in AI Implementation 01:07:25 Concluding Thoughts and Future Directions

Syntax - Tasty Web Development Treats
936: Realtime LED Wall With React + Websockets (I Let Strangers Control It)

Syntax - Tasty Web Development Treats

Play Episode Listen Later Sep 10, 2025 47:12


Scott, Wes, and CJ dive into Wes's Hackweek project: a real-time, web-controlled LED grid. They break down the hardware build, custom 3D-printed diffuser, ESP32 microcontroller, and Cloudflare durable objects powering live pixel art, GitHub activity displays, and interactive web drawings. Show Notes 00:00 Welcome to Syntax! 02:03 Wes' Hackweek project: a web-controlled LED grid 03:52 The hardware: LED panels, soldering, and power WS2812 LED panels 06:38 ESP32 microcontroller and WLED firmware explained ESP32 Microcontroller 10:57 Power supply challenges and injection fixes 15:05 Debugging and testing a DIY LED matrix 15:56 Shorts, blown circuits, and melted wires 17:58 Designing and 3D-printing the diffuser for crisp pixels 21:29 The software: Cloudflare Durable Objects + Party Server Cloudflare Durable Objects Party.server 22:18 Real-time sync and state management across clients Party Client 28:43 Connecting the server to the LED hardware 41:51 Open access fun: scripts, NSFW images, and moderation Cloudflare tunnel 44:10 Live demos 45:34 Future plans: stats, rooms, and making it always-on Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Skeptoid
Skeptoid #1005: Debugging Done Diligently

Skeptoid

Play Episode Listen Later Sep 9, 2025 15:02


Another round of corrections of errors from past episodes, keeping your Skeptoid archive tidy and accurate. Learn about your ad choices: dovetail.prx.org/ad-choices

Lex Fridman Podcast
#479 – Dave Plummer: Programming, Autism, and Old-School Microsoft Stories

Lex Fridman Podcast

Play Episode Listen Later Aug 29, 2025


Dave Plummer is a programmer, former Microsoft software engineer (Windows 95, NT, XP), creator of Task Manager, author of two books on autism, and host of the Dave's Garage YouTube channel, where he shares stories from his career, insights on software development, and deep dives into technology. Thank you for listening ❤ Check out our sponsors: https://lexfridman.com/sponsors/ep479-sc See below for timestamps, and to give feedback, submit questions, contact Lex, etc. CONTACT LEX: Feedback - give feedback to Lex: https://lexfridman.com/survey AMA - submit questions, videos or call-in: https://lexfridman.com/ama Hiring - join our team: https://lexfridman.com/hiring Other - other ways to get in touch: https://lexfridman.com/contact EPISODE LINKS: Dave's X: https://x.com/davepl1968 Dave's YouTube: https://www.youtube.com/@DavesGarage Dave's Secondary YouTube Channel: https://www.youtube.com/@davepl Dave's GitHub: https://github.com/PlummersSoftwareLLC Dave's Books: https://amzn.to/41qd5IB SPONSORS: To support this podcast, check out our sponsors & get discounts: UPLIFT Desk: Standing desks and office ergonomics. Go to https://upliftdesk.com/lex ZocDoc: App that helps patients find healthcare providers. Go to https://zocdoc.com/lex Fin: AI agent for customer service. Go to https://fin.ai/lex Allio Capital: AI-powered investment app that uses global macroeconomic trends. Go to https://alliocapital.com/ Shopify: Sell stuff online. Go to https://shopify.com/lex OUTLINE: (00:00) - Introduction (01:14) - Sponsors, Comments, and Reflections (10:16) - First computer (15:54) - Dropping out of high-school (23:35) - Joining Microsoft (25:47) - MS-DOS (28:59) - Windows 95 (35:46) - The man behind Windows (40:42) - Debugging (45:59) - Task Manager (51:08) - 3D Pinball: Space Cadet (56:07) - Start menu and taskbar (1:07:06) - Blue Screen of Death (1:09:15) - Best programmers (1:17:16) - Scariest time of Dave's life (1:24:44) - Best Windows version (1:26:34) - Slot machines (1:30:17) - Autism and ADHD (1:49:37) - Fastest programming language (1:53:42) - Future of programming PODCAST LINKS: - Podcast Website: https://lexfridman.com/podcast - Apple Podcasts: https://apple.co/2lwqZIr - Spotify: https://spoti.fi/2nEwCF8 - RSS: https://lexfridman.com/feed/podcast/ - Podcast Playlist: https://www.youtube.com/playlist?list=PLrAXtmErZgOdP_8GztsuKi9nrraNbKKp4 - Clips Channel: https://www.youtube.com/lexclips

Syntax - Tasty Web Development Treats
929: Cloudflare Blocks AI Crawlers × Debugging Local Data × Raising Kids with Healthy Digital Habits and More

Syntax - Tasty Web Development Treats

Play Episode Listen Later Aug 18, 2025 53:58


Scott and Wes tackle listener questions on everything from local-first databases and AI-built CRMs to protecting APIs and raising kids with healthy digital habits. They also weigh in on Cloudflare's AI crawler ban, portfolio critiques, and more hot takes from the dev world. Show Notes 00:00 Welcome to Syntax! 00:49 Dreaming about web components. 02:55 Local-First Apps for Customer Support. Brought to you by Sentry.io 08:17 AI-Built CRM: Portfolio or Problem? Ben Vinegar's Engineering Interview Strategy. 18:55 InstantDB vs. Other Local-First Databases. 21:46 Raising Kids with Healthy Digital Habits. Porta Potty Prince on TikTok. 32:55 Cloudflare Blocks AI Crawlers. Good for Creators? Cloudflare Pay Per Crawl. Cloudflare No AI Crawl Without Compensation. Chris Coyier's Blog Response. 41:46 Protecting APIs and Obfuscating Source Code. 44:49 Will Portfolio Critiques Return? 46:45 Sick Picks + Shameless Plugs. Sick Picks Scott: Wifi 7 Eero. Wes: Plastic Welder Shameless Plugs Scott: Syntax on YouTube Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

MindHack Podcast
#096 - Brian Sachetta - Engineer Your Calm: Debugging Mental Loops

MindHack Podcast

Play Episode Listen Later Aug 11, 2025 88:36 Transcription Available


MindHack's Latest Code Drop: We unpack a groundbreaking approach to mental wellness with former software engineer and author, Brian Sachetta. Brian reveals how to 'debug' your mind, treating anxious thought loops and mental overwhelm like 'rogue software' that can be systematically reprogrammed.  Discover his powerful IRA framework: Interrupt, Reframe, Anchor, a concrete algorithm to halt anxiety spirals and transform stress into 'rocket fuel' for enhanced performance. Learn actionable strategies to optimize your mental operating system, tackle imposter syndrome, and cultivate profound resilience.  Tune in to engineer your calm and unlock a sharper, more focused mindset.ℹ️ About the GuestBrian Sachetta, the visionary former software engineer and founder of Get Out Of Your Head. Brian uniquely applies tech-inspired solutions to mental wellness, helping us debug our minds. His powerful books, including 'Get Out of Your Head: A Toolkit for Living with and Overcoming Anxiety' and 'Navigating the Abyss of Depression,' offer concrete strategies to reprogram anxious thought loops and cultivate profound resilience.Website  InstagramFacebook

Remote Ruby
Rolling Out Features and Rails 8 Insights

Remote Ruby

Play Episode Listen Later Aug 1, 2025 47:24


Chris and Andrew catch up on their week, discussing Andrew's recent successful feature launch, their love for South Park, and the recent news about a $1.5 billion deal with Paramount. They go back-and-forth on upgrades to Bundler 2.7 and the intricacies of emoji reactions in their app. Debugging, code refactoring, and the importance of testing are discussed, with mentions of pairing with coworkers and using WebSockets for real-time updates. They dive into technical discussions about Ruby, Rails updates, and their use of Flipper for feature toggles. They also talk about the new Rails tutorial, the implications of ongoing sanitization and upgrades, and the anticipation for upcoming Ruby versions and features. Hit that download button now!LinksJudoscale- Remote Ruby listener giftJeff Dickey (JDX) WebsiteBundler v2.7: last release before Bundler 4 (Bundler Blog)Getting started guide-unsubscribe (reddit)Faster Rails system tests by Lewis BuckleyDaniel Stenberg WebsiteAll the talks from RailsConf 2025-Philadelphia (YouTube)HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleMake your deployments bulletproof with autoscaling that just works.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you. Chris Oliver X/Twitter Andrew Mason X/Twitter Jason Charnes X/Twitter

No Such Thing: K12 Education in the Digital Age
Debugging Efforts in CS Education

No Such Thing: K12 Education in the Digital Age

Play Episode Listen Later Jul 31, 2025 60:29


Guest Diane Levitt shares how Cornell Tech, in collaboration with the City of New York, is reimagining computer science education through an equity-first approach. From pilot programs that stumble to systems that scale, this episode explores how institutional iteration—especially when it fails—can lead to more inclusive and impactful CS learning.Links:https://www.prnewswire.com/news-releases/2024-state-of-computer-science-education-highlights-growing-investment-from-policymakers-continued-gaps-in-access-302282502.htmledc.nyc/press-release/nycedc-and-cornell-tech-advance-new-new-york-initiative-establish-new-york-cityedc.nyc/program/pilot-new-york-citypar.nsf.gov/servlets/purl/10101543https://tech.cornell.edu/about/https://www.linkedin.com/feed/update/urn:li:activity:7344464344660811780/https://csteachers.org/what-is-the-state-of-cs-education-in-2024/ Hosted on Acast. See acast.com/privacy for more information.

Develpreneur: Become a Better Developer and Entrepreneur
Evolving from Coder to Developer: What You Need to Know

Develpreneur: Become a Better Developer and Entrepreneur

Play Episode Listen Later Jul 31, 2025 30:07


In this episode of the Building Better Developers podcast, Rob Broadhead and Michael Meloche revisit one of their most foundational topics: evolving from coder to developer. Explored initially in the “Skill Sets for Success” episode, this updated discussion is guided by fresh talking points generated via ChatGPT—though the core theme remains the same: how to grow from a task-focused coder into a solution-oriented developer. Understanding the Shift: From Coder to Developer At the heart of this episode is the distinction between coders and developers. Coders complete the job. Developers solve the problem—and think beyond the current task. Michael emphasizes that evolving from coder to developer is about ownership. Developers consider reusability, maintainability, and long-term value. They don't just write code—they build tools that scale and adapt.

Toxic Tangents
Debugging the Immune System with Tatyana Dobreva

Toxic Tangents

Play Episode Listen Later Jul 30, 2025 19:17


As many of our followers can attest that we're a huge fan of getting to the root of your health issues. With Million Marker's Detect & Detox Kit, you can receive tools necessary to help you reduce your toxic chemical exposures. This information is extremely important for improving your fertility as well as your health. Another new and cutting edge at home testing company or become a huge fan of is the ImYoo. ImYoo couples at home blood collection and single single cell RNA sequencing to be used in immunology studies. This initiative can be very, very beneficial for collecting life changing and life saving data. And today, we're really glad to be joined by my friend and also ImYoo CEO and founder, Tatiana Dobreva, to tell us a little more about this really innovative technology and what ImYoo is doing. Learn more about ImYoo's services: https://www.imyoo.health/Get tested for BPA, phthalates, parabens, and other hormone-disrupting chemicals with Million Marker's Detect & Detox Test Kit: https://www.millionmarker.com/

Thinking Elixir Podcast
262: Five Years of Perfect Uptime

Thinking Elixir Podcast

Play Episode Listen Later Jul 22, 2025 27:03


News includes Phoenix 1.8.0-rc.4 and LiveView 1.1.0-rc.3 with igniter upgrader support, new libraries including deps_changelog and the Hog process debugging tool by Alex Koutmos, Fly.io's announcement of managed Postgres, an incredible conference talk about Waterpark - a healthcare system built on the BEAM that achieved 100% uptime for 5 years and running, tips on using Elixir compiler directives for function inlining, the full ElixirConf US 2025 schedule with keynotes from José Valim and Chris McCord, CodeBeam Europe speaker announcements, and more! Show Notes online - http://podcast.thinkingelixir.com/262 (http://podcast.thinkingelixir.com/262) Elixir Community News https://paraxial.io/ (https://paraxial.io/utm_source=thinkingelixir&utm_campaign=thinkingelixir-july2025) – Paraxial.io is sponsoring today's show! Sign up for a free trial of Paraxial.io today and mention Thinking Elixir when you schedule a demo for a special offer. https://bsky.app/profile/steffend.me/post/3ltz36vf4ts2u (https://bsky.app/profile/steffend.me/post/3ltz36vf4ts2u?utm_source=thinkingelixir&utm_medium=shownotes) – Phoenix 1.8.0-rc.4 and LiveView 1.1.0-rc.3 released with igniter upgrader for LiveView 1.0 users https://tomkonidas.com/repo-transact/ (https://tomkonidas.com/repo-transact/?utm_source=thinkingelixir&utm_medium=shownotes) – New Ecto 3.13 Repo.transact/2 used in generators Added security.md guide for security best practices and fetch() support for LongPoll in Service Workers https://github.com/serpent213/deps_changelog (https://github.com/serpent213/deps_changelog?utm_source=thinkingelixir&utm_medium=shownotes) – New library called deps_changelog that finds additions to dependency CHANGELOG files upon update https://x.com/akoutmos/status/1935463503164309611 (https://x.com/akoutmos/status/1935463503164309611?utm_source=thinkingelixir&utm_medium=shownotes) – Alex Koutmos announces new Elixir process debugging library called "Hog" https://github.com/akoutmos/hog (https://github.com/akoutmos/hog?utm_source=thinkingelixir&utm_medium=shownotes) – Hog library used to pinpoint and deal with memory hungry processes, helps track down OOM issues https://bsky.app/profile/fly.io/post/3ltlmmz4hq72n (https://bsky.app/profile/fly.io/post/3ltlmmz4hq72n?utm_source=thinkingelixir&utm_medium=shownotes) – Fly.io announces managed Postgres with automatic backups, failover, and monitoring https://www.youtube.com/watch?v=hdBm4K-vvt0 (https://www.youtube.com/watch?v=hdBm4K-vvt0?utm_source=thinkingelixir&utm_medium=shownotes) – Waterpark conference talk - Transforming Healthcare with Distributed Actors achieving 100% uptime for 5 years https://x.com/sasajuric/status/1943601894141640808 (https://x.com/sasajuric/status/1943601894141640808?utm_source=thinkingelixir&utm_medium=shownotes) – Saša Jurić shares about the Waterpark talk https://curiosum.com/blog/interacting-with-google-sheets-in-elixir (https://curiosum.com/blog/interacting-with-google-sheets-in-elixir?utm_source=thinkingelixir&utm_medium=shownotes) – In-depth article about using Elixir and Phoenix to pull data from Google Spreadsheet https://x.com/jskalc/status/1945092835067211929 (https://x.com/jskalc/status/1945092835067211929?utm_source=thinkingelixir&utm_medium=shownotes) – Fun tip about Elixir compiler directive to inline functions for performance https://bsky.app/profile/elixirconf.bsky.social/post/3ltjyeeamwi2s (https://bsky.app/profile/elixirconf.bsky.social/post/3ltjyeeamwi2s?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf US 2025 full schedule published https://elixirconf.com/#keynotes (https://elixirconf.com/#keynotes?utm_source=thinkingelixir&utm_medium=shownotes) – ElixirConf keynotes featuring José Valim, Chris McCord, and others https://ti.to/elixirconf/2025/discount/ThinkingElixir (https://ti.to/elixirconf/2025/discount/ThinkingElixir?utm_source=thinkingelixir&utm_medium=shownotes) – Get ElixirConf 2025 tickets with "ThinkingElixir" discount code for 10% off https://codebeameurope.com (https://codebeameurope.com?utm_source=thinkingelixir&utm_medium=shownotes) – CodeBeam Europe speaker list is up for November 5-6 in Berlin and Online Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Find us online - Message the show - Bluesky (https://bsky.app/profile/thinkingelixir.com) - Message the show - X (https://x.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen on X - @brainlid (https://x.com/brainlid) - Mark Ericksen on Bluesky - @brainlid.bsky.social (https://bsky.app/profile/brainlid.bsky.social) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel on Bluesky - @david.bernheisel.com (https://bsky.app/profile/david.bernheisel.com) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern)

Supermanagers
AI Becomes Your Personal Mentor and Builds Custom Dashboards with Rob Williams

Supermanagers

Play Episode Listen Later Jul 22, 2025 61:03


In this episode, Aydin sits down with Rob Williams, a former Chief Product Officer turned AI consultant, to explore the future of work, apps, and personal development—powered by generative AI. Rob demos Limitless, an AI pendant that helps him become a better human, and Claude Code, an agentic AI development environment that builds apps like a team of tireless developers. Plus, he shares his game-changing discovery-to-deliverable workflow that cuts a week's worth of consulting into a single day.Timestamps:01:00 – Rob's tech background and founding an AI consultancy05:01 – Demo 1: Limitless AI pendant – the wearable mentor08:19 – Rob's daily AI automations for personal growth10:28 – The privacy dilemma and how Rob handles it13:35 – Society's shifting comfort with constant recording18:20 – Rewind: screen-tracking AI and quantified work21:16 – Dystopia or augmentation? Competing views on AI ubiquity27:02 – Demo 2: Claude Code – a real agentic AI dev experience33:10 – Claude Code spins up dashboards from Excel in minutes37:39 – Debugging and security auditing with Claude40:20 – Rob's gamified AI-powered habit tracker41:47 – Claude Code for prototyping with dev teams44:47 – Implications: Will dynamic apps kill the App Store?47:00 – AI as the new operating system50:26 – Future: UIs disappear, apps build themselves52:00 – Demo 3 (Explained): Deep research AI for consulting workflows54:00 – Talking for the AI: How Rob narrates calls for context58:30 – Why you must rethink—not just speed up—your workflows59:36 – Two more tips (in newsletter only!)Tools & Technologies Mentioned:Limitless (limitless.ai) – Wearable AI pendant that records, transcribes, and summarizes your day with daily automations and feedback loops.Claude Code – Anthropic's CLI tool for building full applications using agentic AI workflows, including dependency management and debugging.Rewind – Screen-capturing app that logs your activity with searchable recall capabilities.Fellow – AI meeting tool that transcribes and summarizes meetings. Used by Rob for work-related action tracking.Typora – Markdown editor Rob uses to annotate and refine AI outputs.Deep Research – Rob's name for his long-context LLM-based analysis prompt stack, used for summarizing 20+ hour discovery projects.RescueTime – Productivity analytics tool used to track app usage and categorize time spent.

Behind The Thread
The Replit Insider: How to Build & Deploy a $1M App in the New Era of AI (Step-By-Step Guide)

Behind The Thread

Play Episode Listen Later Jul 21, 2025 103:42


Start your business today with Shopify: https://shopify.com/calumjohnsonGet $350 off the EightSleep Pod 5 Ultra— https://www.eightsleep.com/calumjohnsonCheck out Notion, the best AI tool for work, right now at https://notion.com/calumjohnsonGet More From This Video:Download Our Free Supporting Doc that shares the full steps we go through in this episode: https://bit.ly/CJxMattPalmerWe used Replit AI Agent in this Masterclass: https://bit.ly/ReplitAIFollow Us!https://www.instagram.com/calumjohnson1/https://x.com/calum_johnson9Guest: https://x.com/mattppalTimestamps00:00 INTRO02:01 The golden era for builders!07:16 The wake-up call: are you on the WRONG path?09:40 The fear of being average — escape NPC life12:26 Vibe-coding & the rise of Replit14:40 An $100M company in 5.5 months17:59 Step 0: IDEA MINING (simple notebook exercise)20:45 Find your $100M idea25:22 The 4-Step Framework: PLAN → PROMPT → PERFECT → PUBLISH33:18 LIVE BUILD starts: planning the Zen-Timer app38:57 PROMPT MAGIC — AI Agent writes the entire code45:03 Debugging 101 (You will Believe you can build ANYTHING!)53:50 Perfecting: log-in & data in minutes1:02:45 PUBLISH your AI app in one click — deploy to the web1:06:40 Design tweaks with screenshots & Figma import1:14:50 How To Market Your New Business! ($1M Apps do this!)1:23:20 How to get your FIRST users (Matt's playbook)1:31:40 Consistency • Simplicity • EXECUTIONAbout Matt PalmerMatt Palmer is the Replit Insider and Vibe coding expert. In this masterclass we show step by step how anyone can turn an idea into a profitable app in 30 minutes—even if you've never written a line of code.

The Data Stack Show
253: Why Traditional Data Pipelines Are Broken (And How to Fix Them) with Ruben Burdin of Stacksync

The Data Stack Show

Play Episode Listen Later Jul 16, 2025 58:37


This week on The Data Stack Show, Eric and welcomes back Ruben Burdin, Founder and CEO of Stacksync as they together dismantle the myths surrounding zero-copy ETL and traditional data integration methods. Ruben reveals the complex challenges of two-way syncing between enterprise systems like Salesforce, HubSpot, and NetSuite, highlighting how existing tools often create more problems than solutions. He also introduces Stacksync's innovative approach, which uses real-time SQL-based synchronization to simplify data integration, reduce maintenance overhead, and enable more efficient operational workflows. The conversation exposes the limitations of current data transfer techniques and offers a glimpse into a more declarative, flexible approach to managing enterprise data across multiple systems. You won't want to miss it.Highlights from this week's conversation include:The Pain of Two-Way Sync and Early Integration Challenges (2:01)Zero Copy ETL: Hype vs. Reality (3:50)Data Definitions and System Complexity (7:39)Limitations of Out-of-the-Box Integrations (9:35)The CSV File: The Original Two-Way Sync (11:18)Stacksync's Approach and Capabilities (12:21)Zero Copy ETL: Technical and Business Barriers (14:22)Data Sharing, Clean Rooms, and Marketing Myths (18:40)The Reliable Loop: ETL, Transform, Reverse ETL (27:08)Business Logic Fragmentation and Maintenance (33:43)Simplifying Architecture with Real-Time Two-Way Sync (35:14)Operational Use Case: HubSpot, Salesforce, and Snowflake (39:10)Filtering, Triggers, and Real-Time Workflows (45:38)Complex Use Case: Salesforce to NetSuite with Data Discrepancies (48:56)Declarative Logic and Debugging with SQL (54:54)Connecting with Ruben and Parting Thoughts (57:58)The Data Stack Show is a weekly podcast powered by RudderStack, customer data infrastructure that enables you to deliver real-time customer event data everywhere it's needed to power smarter decisions and better customer experiences. Each week, we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

This Week in Google (MP3)
IM 827: Marco Rubio on Line 1 - The Promise of Personalized Software

This Week in Google (MP3)

Play Episode Listen Later Jul 10, 2025 168:10


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

All TWiT.tv Shows (MP3)
Intelligent Machines 827: Marco Rubio on Line 1

All TWiT.tv Shows (MP3)

Play Episode Listen Later Jul 10, 2025 168:10 Transcription Available


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

Radio Leo (Audio)
Intelligent Machines 827: Marco Rubio on Line 1

Radio Leo (Audio)

Play Episode Listen Later Jul 10, 2025 168:10 Transcription Available


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

This Week in Google (Video HI)
IM 827: Marco Rubio on Line 1 - The Promise of Personalized Software

This Week in Google (Video HI)

Play Episode Listen Later Jul 10, 2025 168:10


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

All TWiT.tv Shows (Video LO)
Intelligent Machines 827: Marco Rubio on Line 1

All TWiT.tv Shows (Video LO)

Play Episode Listen Later Jul 10, 2025 168:10 Transcription Available


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

Radio Leo (Video HD)
Intelligent Machines 827: Marco Rubio on Line 1

Radio Leo (Video HD)

Play Episode Listen Later Jul 10, 2025 168:10 Transcription Available


Interview with Mike Masnick Stop Begging Billionaires To Fix Software — Build Your Own The one secret to using genAI to boost your brain Linda Yaccarino steps down as CEO of Elon Musk's X How the Owner of Hidden Valley Ranch Learned to Love AI As an M.D, here's my 100% honest opinion and observations/advices about using ChatGPT : r/ChatGPT (21) Josh Woodward on X: "The wait is over. @GeminiApp is now shipping Veo 3 *globally* for all Pro members! That means India, Indonesia, all of Europe, and more are starting to get access to create videos right now. As a member, you'll get 3 video generations per day, and that credit will replenish https://t.co/uPa0p0KQZu" / X Chinese robot dog nears Usain Bolt speed, breaks global record Vibe Coder' Who Doesn't Know How to Code Keeps Winning Hackathons in San Francisco A.I.'s Hidden Layer (And Why I Joined Puck) A Marco Rubio impostor is using AI voice to call high-level officials Positive review only': Researchers hide AI prompts in papers Hertz and Other Rental Car Agencies Turn to AI for Damage Detection Zitron: OpenAI May Be in Major Trouble Financially Hugging Face opens up orders for its Reachy Mini desktop robots Grammarly Authorship CalMatters Digital Democracy Hosts: Leo Laporte, Jeff Jarvis, and Mike Elgan Guest: Mike Masnick Download or subscribe to Intelligent Machines at https://twit.tv/shows/intelligent-machines. Join Club TWiT for Ad-Free Podcasts! Support what you love and get ad-free shows, a members-only Discord, and behind-the-scenes access. Join today: https://twit.tv/clubtwit Sponsors: agntcy.org monarchmoney.com with code IM smarty.com/twit

Thinking Elixir Podcast
260: Cheaper testing with AI?

Thinking Elixir Podcast

Play Episode Listen Later Jul 8, 2025 22:04


News includes LiveDebugger v0.3.0 with enhanced debugging capabilities for Phoenix LiveView including redirect following and dead process state browsing, Oban 1.6 featuring sub-workflows and cascading workflows, YOLO v0.2.0 bringing YOLOX support for faster image detection in Elixir, a discussion on the importance of testing and how AI tools are making test creation easier, helpful LiveView tips for opening unique URLs in new tabs, and progress updates on the new Expert LSP project for improved Elixir language server capabilities, and more! Show Notes online - http://podcast.thinkingelixir.com/260 (http://podcast.thinkingelixir.com/260) Elixir Community News https://www.honeybadger.io/ (https://www.honeybadger.io/utm_source=thinkingelixir&utm_medium=podcast) – Honeybadger.io is sponsoring today's show! Keep your apps healthy and your customers happy with Honeybadger! It's free to get started, and setup takes less than five minutes. https://bsky.app/profile/membrane-swmansion.bsky.social/post/3lsgrudmtgk2u (https://bsky.app/profile/membrane-swmansion.bsky.social/post/3lsgrudmtgk2u?utm_source=thinkingelixir&utm_medium=shownotes) – LiveDebugger v0.3.0 release announcement on BlueSky https://github.com/software-mansion/live-debugger (https://github.com/software-mansion/live-debugger?utm_source=thinkingelixir&utm_medium=shownotes) – LiveDebugger GitHub repository - browser-based tool for debugging Phoenix LiveView applications https://bsky.app/profile/oban.pro/post/3lstnmlzd7226 (https://bsky.app/profile/oban.pro/post/3lstnmlzd7226?utm_source=thinkingelixir&utm_medium=shownotes) – Oban 1.6 release announcement on BlueSky https://oban.pro/docs/pro/1.6.0/changelog.html (https://oban.pro/docs/pro/1.6.0/changelog.html?utm_source=thinkingelixir&utm_medium=shownotes) – Oban 1.6 changelog with sub-workflows, cascading workflows, grafting, and more features https://github.com/poeticoding/yolo_elixir (https://github.com/poeticoding/yolo_elixir?utm_source=thinkingelixir&utm_medium=shownotes) – YOLO v0.2.0 GitHub repository - image detection library for Elixir https://www.poeticoding.com/elixir-yolo-v0-2-0-yolox-support-custom-models-and-performance-boost/ (https://www.poeticoding.com/elixir-yolo-v0-2-0-yolox-support-custom-models-and-performance-boost/?utm_source=thinkingelixir&utm_medium=shownotes) – Blog post about YOLO v0.2.0 major release with YOLOX support https://github.com/poeticoding/yolo_elixir/releases/tag/0.2.0 (https://github.com/poeticoding/yolo_elixir/releases/tag/0.2.0?utm_source=thinkingelixir&utm_medium=shownotes) – YOLO v0.2.0 release notes https://bsky.app/profile/germsvel.com/post/3lslzsazcys2r (https://bsky.app/profile/germsvel.com/post/3lslzsazcys2r?utm_source=thinkingelixir&utm_medium=shownotes) – German Velasco's BlueSky post about the importance of testing https://www.germanvelasco.com/blog/why-we-test (https://www.germanvelasco.com/blog/why-we-test?utm_source=thinkingelixir&utm_medium=shownotes) – Blog post by German Velasco on why we test and the benefits of automated testing https://x.com/philipbrown/status/1939630205875663017 (https://x.com/philipbrown/status/1939630205875663017?utm_source=thinkingelixir&utm_medium=shownotes) – Philip Brown's Twitter tip about generating unique URLs from LiveView that open in new tabs https://expert-lsp.org/ (https://expert-lsp.org/?utm_source=thinkingelixir&utm_medium=shownotes) – Expert LSP project website placeholder for the new Elixir Language Server https://bsky.app/profile/expert-lsp.org/post/3lsqragb4ns23 (https://bsky.app/profile/expert-lsp.org/post/3lsqragb4ns23?utm_source=thinkingelixir&utm_medium=shownotes) – Expert LSP BlueSky account first teaser post about the new Elixir Language Server project Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Find us online - Message the show - Bluesky (https://bsky.app/profile/thinkingelixir.com) - Message the show - X (https://x.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen on X - @brainlid (https://x.com/brainlid) - Mark Ericksen on Bluesky - @brainlid.bsky.social (https://bsky.app/profile/brainlid.bsky.social) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel on Bluesky - @david.bernheisel.com (https://bsky.app/profile/david.bernheisel.com) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern)

The Agile Embedded Podcast
AI-augmented software development

The Agile Embedded Podcast

Play Episode Listen Later Jun 25, 2025 45:51


Luca and Jeff dive into how AI tools can supercharge embedded development workflows. Luca shares his extensive hands-on experience, while Jeff brings a fresh perspective as someone just starting to incorporate these tools. They explore how AI can help with coding, testing, and debugging - while emphasizing that good software engineering judgment remains crucial. The conversation is particularly timely since AI tools are evolving rapidly, unlike their usually more "evergreen" podcast topics.A key insight they discuss is that while AI tools offer amazing productivity boosts (much like IDEs did), they're not replacing experienced developers anytime soon. However, they raise interesting questions about the future job market for junior developers. Their take? Modern developers should absolutely embrace AI tools, but use them thoughtfully - especially when learning.Key Timestamps and Topics:00:00:00 - Welcome and episode overview00:00:43 - Why this topic won't age well (but that's okay!)00:02:20 - Breaking down different AI coding tools00:08:00 - Deep dive into aider and workflow integration00:20:02 - Using AI for testing and test-driven development00:27:00 - AI-assisted architecture work and its limitations00:30:40 - How AI helps explore unfamiliar codebases00:33:30 - Debugging with AI - pros and cons00:38:50 - What this means for development jobs00:43:59 - Using AI to learn new frameworks/languages00:46:15 - Embedded Online Conference preview You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click here

Talking Drupal
Talking Drupal #506 - Automated Testing Kit

Talking Drupal

Play Episode Listen Later Jun 9, 2025 68:28


Today we are talking about Automated Testing Kit demo Recipe, Why Automated Testing is important, and How this recipe helps with guest André Angelantoni. We'll also cover Taxonomy Views Integrator as our module of the week. For show notes visit: https://www.talkingDrupal.com/506 Topics What is Automated Testing Kit Features and benefits of Automated Testing Kit Cypress vs Playwright Where should these run Automated Testing Kit recipe Demo configuration Installing and setting up the Kit Using this on an existing site Managing tests and repositories Building and using recipes Debugging and troubleshooting tests Roadmap Resources Automated Testing Kit Demo Recipe Automated Testing Kit Documentation https://performantlabs.com/automated-testing-kit/automated-testing-kit https://performantlabs.com/testor/introduction Thread on nightwatch replacement Testor Automated Testing Kit Intro Video Automated Testing Kit Philosophy Recipes list Testery Testiny Code generators Drupal forge Guests André Angelantoni - drupal.org/project/automated_testing_kit aangel Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Norah Medlin - tekNorah MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to customize the taxonomy display view for a specific vocabulary, or even a specific taxonomy term? There's a module for that. Module name/project name: Taxonomy Views Integrator Brief history How old: created in Sep 2009 by Derek Webb (derekwebb1) though the most recent release was made by Kevin Quillen, who was a guest on the podcast in episodes 406 and 500 Versions available: 2.0.0 which works with Drupal 8, 9, 10, and 11 Maintainership Actively maintained Security coverage Test coverage Documentation Number of open issues: 13 open issues, 4 of which are bugs against the 2.0.x branch Usage stats: 24,130 sites Module features and usage After enabling this module, when you edit a vocabulary or a taxonomy term, users with the necessary permissions will see an option to specify a view to show tagged content, and you can also choose which display to use You can create a new view from scratch, or clone the taxonomy/term/* view provided by core, or a view defined in code. Obvious it's critical for the view to have a contextual filter for a taxonomy term Using this module could allow you to customize the presentation on a view page, for example to make the exposed filters more relevant, or even to split out the content, for example if you wanted to list only news in the main display, and have events and blog posts listed separately in attachments I found this module really helpful during some recent work on the Drupal Event Platform, so I thought I would share it with our listeners

Self-Perfected Podcast
246 Debugging the Demon

Self-Perfected Podcast

Play Episode Listen Later Jun 6, 2025 190:48


In this episode we discuss how we debug the demon, the demons in the system. Veo was also released and this is going to shake up the world system even better. Let's make the world best for all life join www.self-perfected.com 

GOTO - Today, Tomorrow and the Future
Design & Develop Distributed Software Better w/ Multiplayer • Tom Johnson & Julian Wood

GOTO - Today, Tomorrow and the Future

Play Episode Listen Later Jun 6, 2025 44:39 Transcription Available


This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereThomas Johnson - Co-Founder & CTO at MultiplayerJulian Wood - Serverless Developer Advocate at AWSRESOURCESTomhttps://x.com/tomjohnson3https://www.linkedin.com/in/tomjohnson3https://github.com/tomjohnson3Julianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://www.multiplayer.appDESCRIPTIONJulian Wood and Tom Johnson explore the complexities of modern software development, with Tom sharing his journey from machine learning and distributed systems to founding Multiplayer, a company focused on simplifying development by automating documentation, debugging, and system design.They discuss the challenges of building and managing complex software architectures, especially with microservices and cloud platforms, and the need for better tooling to address these issues. Tom emphasizes the importance of simplicity, collaboration, and transparency in development, especially when it comes to API design and managing system dependencies. They also explore best practices for team communication, the evolving role of platform engineering, and the shift toward a future where infrastructure is abstracted away, allowing developers to focus on software creation.Together, they envision a world where better tools and AI lower the barrier to entry for developers, driving innovation and enabling more people to bring their ideas to life.RECOMMENDED BOOKSSimon Brown • Software Architecture for Developers Vol. 2David Farley • Modern Software EngineeringKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookSimon Wardley • Wardley MapsSimon Wardley • Wardley Mapping, The KnowledgeDavid Anderson, Marck McCann & Michael O'Reilly • The Value Flywheel EffectMike Amundsen • Restful Web API Patterns & Practices CookbookBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Superwomen with Rebecca Minkoff
Debugging the Code: How To Rewrite Tech's Playbook with Cristina Mancini, CEO of Black Girls Code

Superwomen with Rebecca Minkoff

Play Episode Listen Later Jun 5, 2025 30:10


This week on SUPERWOMEN, I'm joined by Cristina Mancini, CEO of Black Girls Code, the nonprofit on a mission to change the face of tech. Before joining Black Girls Code, Cristina built a career in film and television, where her curiosity about how to reach audiences between releases led her into the world of technology. What began as a quest to better engage fans soon evolved into a passion for using tech to drive impact and inclusion. Cristina is leading a powerful expansion of the organization's focus: beyond teaching girls to code, she's focused on launching them into the rooms where decisions are made. With her, Black Girls Code has grown to include not just education, but inspiration and real-world opportunity, ensuring that girls and women of color not only learn the skills, but build the confidence and community to thrive in tech. Mancini's vision is clear: access isn't enough, especially in a society in which “people are developing technologies that are not built with inclusion in mind.” Under her leadership, Black Girls Code has evolved beyond education, expanding into college campuses and adult programs that inspire, equip, and launch talent into real-world careers. Whether it's helping a girl build her first app or ensuring she lands a paid internship, Cristina is building a future where representation is the rule, not the exception.In a world where AI and emerging technologies are shaping everything from healthcare to hiring, Cristina is clear: inclusion isn't optional, it's crucial. From building out summer camps and national programming to creating pathways for paid internships and leadership, she's working to ensure no girl is left behind just because the tech world wasn't built with her in mind. Thank you for listening! Don't forget to order my book, “Fearless: The New Rules for Unlocking Creativity, Courage, and Success.”Follow SUPERWOMEN (@rmsuperwomen) and Cristina (@crisbmancini) on Instagram.Support this podcast: https://bit.ly/rmsuperwomen 

Raj Shamani - Figuring Out
Private Detective Stories: Hidden Cameras, Affairs & Investigation | Baldev Puri | FO363 Raj Shamani

Raj Shamani - Figuring Out

Play Episode Listen Later Jun 3, 2025 82:09


Guest Suggestion Form: https://forms.gle/bnaeY3FpoFU9ZjA47Disclaimer: This video is intended solely for educational purposes and opinions shared by the guest are his personal views. We do not intent to defame or harm any person/ brand/ product/ country/ profession mentioned in the video. Our goal is to provide information to help audience make informed choices. The media used in this video are solely for informational purposes and belongs to their respective owners.Order 'Build, Don't Talk' (in English) here: https://amzn.eu/d/eCfijRuOrder 'Build Don't Talk' (in Hindi) here: https://amzn.eu/d/4wZISO0Follow Our Whatsapp Channel: https://www.whatsapp.com/channel/0029VaokF5x0bIdi3Qn9ef2J

SemiWiki.com
Video EP7: The impact of Undo’s Time Travel Debugging with Greg Law

SemiWiki.com

Play Episode Listen Later May 30, 2025 11:41


In this episode of the Semiconductor Insiders video series, Dan is joined by Dr Greg Law, CEO of Undo, He is a C++ debugging expert, well-known conference speaker, and the founder of Undo. Greg explains the history of Undo, initially as a provider of software development and debugging tools for software vendors. He explains that… Read More

The Bitcoin Cash Podcast
BLISS 2025: Debugging with CashScript - Rosco Kalis

The Bitcoin Cash Podcast

Play Episode Listen Later May 27, 2025 21:01


Full playlist of BLISS videos: https://www.youtube.com/watch?v=l8_oZaR9A1Q&list=PLo1CFIKcwE6K6_kZyO7I_UOu0ATOT7U7YBLISS website: https://www.bliss.cash/Bitcoin Cash Podcast: https://bitcoincashpodcast.com/

SemiWiki.com
Video EP6: The Benefits of AI Agents for Waveform Debugging with Zackary Glazewski of Alpha Design

SemiWiki.com

Play Episode Listen Later May 23, 2025 10:10


In this episode of the Semiconductor Insiders video series, Dan is joined by Zackary Glazewski, an ML Engineer at Alpha Design AI. Dan explores the challenges of waveform debugging with Zack, who explains how the process is done today and the shortcoming of existing approaches. He explains why current approaches are time consuming… Read More

Where It Happens
ChatGPT Codex is like 10 AI software developers (tutorial for beginners)

Where It Happens

Play Episode Listen Later May 21, 2025


Join me as I chat with Ben Tossell to discuss how non-technical users can leverage OpenAI's Codex to build and modify websites without writing code. The video showcases a practical example of adding a new tab to a personal website through simple text commands, with Codex handling all the coding work. Ben explains GitHub basics, pull requests, and how to manage code changes while emphasizing that this approach makes coding more accessible to beginners. Timestamps: 00:00 - Intro 01:28 - What is Codex 02:38 - Explanation of GitHub and repositories 05:54 - Demonstration of adding a new tab to a website 10:53 - Why use Codex if you are non-technical 15:26 - Explanation of merging and closing pull requests 18:18 - Best practices for non-technical people using Codex 21:54 - Tips for Debugging using ChatGPT 23:47 - More advanced use cases beyond personal websites 25:30 - Cloning a Repo and using Codex 30:08 - Conclusion and Final Thoughts on Codex Key Points: • Codex is an OpenAI terminal product that allows users to type in tasks, generate code, and push it to GitHub without writing code themselves • The workflow involves creating tasks, reviewing generated code, creating pull requests, and merging changes • For non-technical people, Codex offers a more accessible entry point to coding than traditional development • Best practice is to start with simple personal website projects before attempting more complex applications: LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ BoringMarketing — Vibe Marketing for Sale: http://boringmarketing.com/ Startup Empire - a membership for builders who want to build cash-flowing businesses https://www.startupempire.co FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND BEN ON SOCIAL X/Twitter: https://x.com/bentossell Ben's Bites: https://www.bensbites.com

The Biotech Startups Podcast

"My mind is analytical – so I wondered ‘what is the most exciting, impactful thing I could do?' I felt we're all growing older, so where is the technology of aging? How well do we understand the biochemistry of us as humans?" In this episode, Michael Antonov, Co-Founder of Oculus and Founder & CEO of Deep Origin, shares his bold leap from pioneering virtual reality to tackling the complexities of human aging and biotech innovation. Driven by a lifelong curiosity about biology and the mysteries of longevity, Michael reveals how his software background inspired him to "debug" biology, build better research tools, and launch Formic Ventures to back high-risk, high-reward startups. He discusses his vision for integrating computational and biological approaches, the promise of cellular reprogramming, and his mission to create a new ecosystem that empowers researchers and accelerates breakthroughs in extending human healthspan.

Search Off the Record
Debugging the Internet: HTTP, TCP, and You

Search Off the Record

Play Episode Listen Later May 15, 2025 33:25


In this episode of Search Off the Record, Gary Illyes and Martin Splitt from the Google Search team dive deep into the foundations of how the web works—specifically HTTP, TCP, UDP, and newer technologies like QUIC and HTTP/3. The two reflect on how even experienced web professionals often overlook or forget the mechanics behind these core protocols, sharing insights through technical discussion, playful banter, and analogies ranging from messenger pigeons to teapots. The conversation spans key concepts like packet transmission, connection handshakes, and the importance of status codes such as 404, 204, and even 418 (“I'm a teapot”). Throughout the conversation, they connect these protocols back to real-world implications for site owners, developers, and SEOs—like why Search Console might report network errors, and how browser or server behavior is influenced by low-level transport decisions. With a mix of humor and expertise, Gary and Martin aim to demystify a crucial part of the internet's infrastructure and remind listeners of the layered complexity that makes modern web experiences possible. Resources: Episode transcript →https://goo.gle/sotr091-transcript    Listen to more Search Off the Record → https://goo.gle/sotr-yt Subscribe to Google Search Channel → https://goo.gle/SearchCentral Search Off the Record is a podcast series that takes you behind the scenes of Google Search with the Search Relations team. #SOTRpodcast #SEO #Http Speakers: Lizzi Sassman, John Mueller, Martin Splitt, Gary Illyes Products Mentioned: Search Console - General  

DevZen Podcast
Виниловые искажения — Episode 499

DevZen Podcast

Play Episode Listen Later May 8, 2025 79:00


В этом выпуске: TPU и расширение сознания печатников. Больные ублюдки крутят тестовые пластинки. Стектрейс дифференциация тестов вместо цветовой. [00:01:55] Чему мы научились за неделю https://makerworld.com/models/1031969 https://makerworld.com/models/729562 [00:17:54] Валерин патефон часть 2 Hana SH MK II — HANA PHONO CARTRIDGES Ortofon Test Record [00:54:07] Differential Coverage for Debugging [01:11:02] #темы499 Лог чата в Telegram. Голоса выпуска: Алекс, Ваня, Валера,… Читать далее →

core.py
Beta Frenzy

core.py

Play Episode Listen Later May 6, 2025 79:11


Python 3.14 Beta 1 is coming! And that means we reach feature freeze. BUT QUICK, there's still time to squeeze in one last thing!## Timestamps(00:00:00) INTRO(00:01:58) PART 1: Template strings(00:07:10) PART 2: Asyncio Introspection(00:29:07) PART 3: Syntax highlighting(00:43:00) PART 4: Color themes(00:50:56) PART 5: Debugging a remote process with pdb(01:01:35) PART 6: Python Installation Manager for Windows(01:05:29) PART 7: Worship(01:08:53) PART 8: What else is happening?(01:16:03) OUTRO

Everyday AI Podcast – An AI and ChatGPT Podcast
EP 515: Job Security Is Dead in the Age of AI. What You Should Do Instead.

Everyday AI Podcast – An AI and ChatGPT Podcast

Play Episode Listen Later Apr 30, 2025 28:49


AI didn't just rewrite the rules—it burned the old playbook.The idea of long-term "job security"? Gone.But here's the twist:This isn't a threat. It's a wake-up call.Because the people who adapt aren't just surviving—they're winning.The rest? Still playing by rules that no longer exist.Let's talk about what to do next.Newsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageJoin the discussion: Thoughts on this? Join the convo.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:AI's Impact on Job SecurityFuture of Full-Time EmploymentClarity AI CEO's Personal ExperiencesCoping with AI Layoff AnxietyShopify's AI Workforce StrategyUpskilling to Future-Proof CareersPersonal Branding & Networking ImportanceEmergency Plans for AI LayoffsTimestamps:00:00 "Job Security's End in AI Era"03:59 Navigating AI Layoff Anxiety08:00 Future-Proofing Company Leadership11:34 "Why Companies Struggle with Training"14:35 "AI Predictions Impacting Job Security"20:17 "Financial Preparedness & Career Resilience"22:30 "Future-Ready Skills for Developers"24:53 Work Trends and Future Job SecurityKeywords:Job security in the age of AI, Future of work, Upskill, Reskill, Full-time employment, AI tools, Clarity AI, AI layoffs, Layoff anxiety, Personal branding, Networking, Gig economy, Upwork, Video editing, Debugging generated code, AI systems, Senior positions, Entry-level jobs, Skill set changes, Emergency plan, Financial stability, AI prototyping, Data solutions, Freelance, Income diversification, Automation, Digital twins, Roadmap to careers, AI influencer, Modern careers, AI-driven marketplaces, Team restructuring.Send Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Ready for ROI on GenAI? Go to youreverydayai.com/partner

Gradient Dissent - A Machine Learning Podcast by W&B
Inside Cursor: The future of AI coding with Co-founder Sualeh Asif

Gradient Dissent - A Machine Learning Podcast by W&B

Play Episode Listen Later Apr 29, 2025 49:36


In this episode of Gradient Dissent, host Lukas Biewald talks with Sualeh Asif, the CPO and co-founder of Cursor, one of the fastest-growing and most loved AI-powered coding platforms. Sualeh shares the story behind Cursor's creation, the technical and design decisions that set it apart, and how AI models are changing the way we build software. They dive deep into infrastructure challenges, the importance of speed and user experience, and how emerging trends in agents and reasoning models are reshaping the developer workflow.Sualeh also discusses scaling AI inference to support hundreds of millions of requests per day, building trust through product quality, and his vision for how programming will evolve in the next few years.⏳Timestamps:00:00 How Cursor got started and why it took off04:50 Switching from Vim to VS Code and the rise of CoPilot08:10 Why Cursor won among competitors: product philosophy and execution10:30 How user data and feedback loops drive Cursor's improvements12:20 Iterating on AI agents: what made Cursor hold back and wait13:30 Competitive coding background: advantage or challenge?16:30 Making coding fun again: latency, flow, and model choices19:10 Building Cursor's infrastructure: from GPUs to indexing billions of files26:00 How Cursor prioritizes compute allocation for indexing30:00 Running massive ML infrastructure: surprises and scaling lessons34:50 Why Cursor chose DeepSeek models early36:00 Where AI agents are heading next40:07 Debugging and evaluating complex AI agents42:00 How coding workflows will change over the next 2–3 years46:20 Dream future projects: AI for reading codebases and papers

Adafruit Industries
Deep Dive w/Scott: CircuitPython debugging

Adafruit Industries

Play Episode Listen Later Apr 26, 2025 125:52


Join Scott for his last deep dive before more paternity leave. He'll be debugging CircuitPython code. Not sure what. He'll also answer any questions people ask and provide an update on the garbage collection improvements. Visit the Adafruit shop online - http://www.adafruit.com 0:00 Getting started 1:14 Hello everyone - welcome to Deep Dive w/Scott 1:37 Circuit Python - runs on Adafruit Metro RP2350 and many other microprocessors 2:43 Scott's last Deep Dive for the year - then Dad mode and part time 4:00 question about databases on CP - BTree and SQLite 6:43 New 16 inch Framework Laptop ( upgraded from 13 inch ) 9:00 Garbage Collection last week 10:30 Met with MicroPython developers on Tuesday 11:35 Adjusting GC stack speed things up 13:24 working on USB PR commit #10821 16:57 CI scheduler overview 19:07 Shrinking USB static buffers to get the CI to run again 23:10 Merge the "fix" into gc_selective_collect 25:05 test mimxrt10xx port 28:59 looking at linker scripts for sizes 38:00 checking the esp-idf template memory.ld.in 42:00 found "Internal SRAM0 and SRAM1" in datasheet 45:49 back to PR 10293 51:00 investigate second stage boot loader 54:30 linker scripts "digression" 1:09:00 switch to the Fruit Jam 1:13:30 Fruit Jam booted 1:17:39 debug the startup crash 1:25:30 audio playback buffers 1:33:00 examine rp2350 Datasheet DMA and continue to debug DMA 1:50:22 maybe console uart running background task triggers issue 1:52:43 audio_dma_stop called twice? 1:58:27 any final questions? adfru.it/discord 2:04:00 wrap up - thanks to Tim for future deep dives ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

BSD Now
607: Sign those commits

BSD Now

Play Episode Listen Later Apr 17, 2025 56:27


We should improve libzfs somewhat, Accurate Effective Storage Performance Benchmark, Debugging aids for pf firewall rules on FreeBSD, OpenBSD and Thunderbolt issue on ThinkPad T480s, Signing Git Commits with an SSH key, Pgrep, LibreOffice downloads on the rise, and more NOTES This episode of BSDNow is brought to you by Tarsnap (https://www.tarsnap.com/bsdnow) and the BSDNow Patreon (https://www.patreon.com/bsdnow) Headlines We should improve libzfs somewhat (https://despairlabs.com/blog/posts/2025-03-12-we-should-improve-libzfs-somewhat/) Accurate Effective Storage Performance Benchmark (https://klarasystems.com/articles/accurate-effective-storage-performance-benchmark/?utm_source=BSD%20Now&utm_medium=Podcast) News Roundup Debugging aids for pf firewall rules on FreeBSD (https://dan.langille.org/2025/02/24/debugging-aids-for-pf-firewall-rules-on-freebsd/) OpenBSD and Thunderbolt issue on ThinkPad T480s (https://www.tumfatig.net/2025/openbsd-and-thunderbolt-issue-on-thinkpad-t480s/) Signing Git Commits with an SSH key (https://jpmens.net/2025/02/26/signing-git-commits-with-an-ssh-key/) Pgrep (https://www.c0t0d0s0.org/blog/pgrep-z-r.html) LibreOffice downloads on the rise as users look to avoid subscription costs (https://www.computerworld.com/article/3840480/libreoffice-downloads-on-the-rise-as-users-look-to-avoid-subscription-costs.html) Tarsnap This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups. Feedback/Questions Felix - Bhyve and NVME (https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/607/feedback/Felix%20-%20bhyve%20and%20nvme.md) Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv (mailto:feedback@bsdnow.tv) Join us and other BSD Fans in our BSD Now Telegram channel (https://t.me/bsdnow)

PodRocket - A web development podcast from LogRocket
Debugging apps with Deno and OpenTelemetry with Luca Casonato

PodRocket - A web development podcast from LogRocket

Play Episode Listen Later Mar 27, 2025 24:55


Luca Casanato, member of the Deno core team, delves into the intricacies of debugging applications using Deno and OpenTelemetry. Discover how Deno's native integration with OpenTelemetry enhances application performance monitoring, simplifies instrumentation compared to Node.js, and unlocks new insights for developers! Links https://lcas.dev https://x.com/lcasdev https://github.com/lucacasonato https://mastodon.social/@lcasdev https://www.linkedin.com/in/luca-casonato-15946b156 We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Luca Casonato.

Where It Happens
My honest review of AI Product Designer backed by Y-Combinator (v0 Users Need to See This)

Where It Happens

Play Episode Listen Later Mar 5, 2025 30:43


In this episode, I tests Polymet AI, an AI product designer tool, by creating a YouTube analytics prediction SaaS concept inspired by a viral tweet about predicting tweet performance. I compares Polymet AI with V0, noting that while Polymet required multiple prompts and offered less feedback during the design process, both tools ultimately produced usable designs. I concludes that different AI tools have different strengths, and using multiple tools in combination might yield the best results.Timestamps: 00:00 - Intro02:33 - First Impressions of Polymet03:57 - Startup Idea: Predicting YouTube Engagement05:03 - Initial Design Prompt10:11 - Polymet's First Design Output: TubePredict11:04 - UI and Functionality Issues and Debugging16:08 - Polymet's Second Design Output17:44 - Debugging pt 220:48 - Prompting v0 22:30 - v0's Design Output 23:41 - Polymet's Third Design Output24:49 - Comparing v0 and Polymer and Final Thoughts on Design Outputs27:36 - Conclusion and Recommendations for AI Design ToolsKey Points• I tests Polymet AI a new AI product designer tool that claims to help non-designers create production-ready designs• I compares Polymet AI with v0, a similar tool he's used before, by designing a YouTube analytics prediction tool• Both tools produced functional designs, but with different user experiences and output quality1) First impressions of Polymet AI:• Clean interface similar to ChatGPT• Includes voice input (huge plus!)• Image upload capability for reference designs• Credit-based system (250 free credits to start)• 50 credits per page generation2) The design process with Polymet was... interesting.PROS:• Named the product "TubePredict" automatically• Created decent landing page copy• Saved version historyCONS:• Slow generation (2+ minutes)• No progress indicator (frustrating!)• Initial designs missed the mark completely 3) After 3 attempts with increasingly specific prompts, Polymet finally delivered:• Clean, modern interface• Detailed A/B testing dashboard• Statistical confidence indicators• AI suggestions for optimizationBut the communication was ONE-WAY. No feedback loop!4) Meanwhile, v0 showed its strengths:• Real-time reasoning as it designed• Conversational approach ("I'll create a SaaS that...")• Faster FEELING process (transparency helps!)• Ability to ask clarifying questionsThe difference in experience was NIGHT and DAY.5) The final designs were surprisingly similar in quality!Polymet's strengths:• More detailed product features• Hover states built in• Actual code generationv0's advantages:• Slightly more polished visually• More "glassy" as requested• Better feedback loop6) MAJOR INSIGHT: The future isn't about finding ONE perfect AI design tool.It's about using MULTIPLE tools strategically:• Generate initial concepts in one• Refine in another• Mix and match their strengthsJust like we do with ChatGPT, Claude, Gemini, etc.7) The REAL lesson? Knowing design terminology matters!When I specifically requested "glassmorphism" instead of just saying "glassy," both tools performed MUCH better.The more precise your design vocabulary, the better your AI design results.8) Would I recommend these tools? YES - but with expectations in check.Two years ago this would have been MIND-BLOWING.Today, our standards are higher.But for quick prototyping or inspiration, both tools deliver value in different ways.Notable Quotes:"Two years ago, if I would have seen this, I would have been like, 'Oh my God, everything has changed.' And now our bar for all these AI products is so high that the output needs to be incredible for you to really use it in your workflow.""How do you get the most out of them is just you use all of them, you realize what's best for each individual product... There's these nuances that make these products better."Want more free ideas? I collect the best ideas from the pod and give them to you for free in a database. Most of them cost $0 to start (my fav)Get access: https://www.gregisenberg.com/30startupideasLCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/BoringAds — ads agency that will build you profitable ad campaigns http://boringads.com/BoringMarketing — SEO agency and tools to get your organic customers http://boringmarketing.com/Startup Empire - a membership for builders who want to build cash-flowing businesses https://www.startupempire.coFIND ME ON SOCIALX/Twitter: https://twitter.com/gregisenbergInstagram: https://instagram.com/gregisenberg/LinkedIn: https://www.linkedin.com/in/gisenberg/

Software Engineering Daily
Troubleshooting Microservices with Julia Blase

Software Engineering Daily

Play Episode Listen Later Feb 25, 2025 43:00


A distributed system is a network of independent services that work together to achieve a common goal. Unlike a monolithic system, a distributed system has no central point of control, meaning it must handle challenges like data consistency, network latency, and system failures. Debugging distributed systems is conventionally considered challenging because modern architectures consist of The post Troubleshooting Microservices with Julia Blase appeared first on Software Engineering Daily.

SANS Internet Stormcenter Daily Network/Cyber Security and Information Security Stormcast
SANS Internet Stormcast Feb 7th 2025: Unbreakable Anti-Debugging;

SANS Internet Stormcenter Daily Network/Cyber Security and Information Security Stormcast

Play Episode Listen Later Feb 7, 2025 6:22


The Unbreakable Multi-Layer Anti-Debugging System Xavier found a nice Python script that included what it calls the "Unbreakable Multi-Layer Anti-Debugging System". Leave it up to Xavier to tear it appart for you. https://isc.sans.edu/diary/The%20Unbreakable%20Multi-Layer%20Anti-Debugging%20System/31658 Take my money: OCR crypto stealers in Google Play and App Store Malware using OCR on screen shots was available not just via Google Play, but also the Apple App Store. https://securelist.com/sparkcat-stealer-in-app-store-and-google-play-2/115385/ Threat Actors Still Leveraging Legit RMM Tool ScreenConnect Unsurprisingly, threat actors still like to use legit remote admin tools, like ScreenConnect, as a command and control channel. Silent Push outlines the latest trends and IoCs they found https://www.silentpush.com/blog/screenconnect/ Cisco Identity Services Engine Insecure Java Deserialization and Authorization Bypass Vulnerabilities Java deserializing strikes again to allow arbitrary code execution. Cisco fixed this vulnerability and a authorization bypass issue in its Identity Services Engine https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-multivuls-FTW9AOXF F5 Update F5 fixes an interesting authentication bypass problem affecting TLS client certificates https://my.f5.com/manage/s/article/K000149173