Discover
Inside DuckDuckGo
Inside DuckDuckGo
Author: DuckDuckGo
Subscribed: 11Played: 151Subscribe
Share
© DuckDuckGo
Description
Behind the scenes with the DuckDuckGo team — sharing insights on product, engineering, leadership, and AI.
insideduckduckgo.substack.com
insideduckduckgo.substack.com
49 Episodes
Reverse
As long as humans have been doing business, people have found ways to nudge others into accepting terms that are less than ideal. Fast forward to today, and many internet companies have mastered the art of the “dark pattern” — design and pricing decisions that trick users into acting against their own self-interest. In this episode, DuckDuckGo product director Robin Schlinkert walks us through some common dark patterns and explains how big tech’s use of them has hurt consumer choice and competition.If you have feedback on Duck Tales, or episode ideas, email us at [email protected]: (1) The audio, video (above), and transcript (below) are only lightly edited and may contain minor inaccuracies or transcription errors. (2) This website is operated by Substack. This is their privacy policy. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit insideduckduckgo.substack.com
The “second opinion” option in Duck.ai acts almost like a shuffle button, automatically choosing a different AI model to take a second shot at your query. This lets you compare answers side by side, learn the strengths and weaknesses of different models, and avoid overconfidence in a given chatbot’s answers. In this episode, Tatum and Beah (product) discuss how the feature came about and how it addresses multiple challenges with AI search.If you have feedback on Duck Tales, or episode ideas, email us at [email protected]: (1) The audio, video (above), and transcript (below) are only lightly edited and may contain minor inaccuracies or transcription errors. (2) This website is operated by Substack. This is their privacy policy.Tatum: Hello and welcome to DuckTales, where we go behind the scenes at DuckDuckGo and talk about the people, stories, and technology that are building privacy tools for everyone. This week I’m talking to DuckDuckGo Chief Product Officer Beah about a feature in Duck.ai called Second Opinion that lets you compare answers from different AI models side by side. Beah, thank you so much for coming on DuckTales to tell me about second opinion.Beah: My pleasure. Thanks for having me.Tatum: Will you explain what this feature is?Beah: Sure. and in fact, let me show you, which I think will be even better. So we’re at Duck.ai. I’m gonna ask a question that’s at the forefront of everybody’s mind, which is best trick for removing a butternut squash soup stain from white t-shirt. and I’m getting a response here. The model that provided it was GPT-6 Luna and it says to blot off excess, flush the stain from the back with cold water, liquid laundry detergent,Tatum: So we’ve got about two short paragraphs of instructions from GPT-6 Luna. And then at the bottom of the answer, we see a couple buttons like a share button, a copy button, and a button that says second opinion.Beah: Yes, so I I’m like, all right, this answer seems okay, but I don’t want to get this wrong and forever have a yellow stain on my white t-shirt. So I’m gonna click the second opinion and see what another model’s advice is. So in this case, Duck.ai is using Gemma 4, which is an open weight model, asking the same question and we get a slightly different answer here. So we got to treat the grease first and the color second. So looks like there’s a lot of overlap with the first answer, but some additional detail and some additional steps that give me a little bit more confidence here. and so yeah the idea like roughly with this second opinion is that Sometimes you ask AI a question, you get an answer, and you’re like, maybe, okay, I don’t know. Like I would ask another friend if I was at a sitting at a table looking for advice. And so you get to roll the dice again and and ask another model and get another question, and then you can kind of figure out the the diffTatum: Interesting. Okay, so you just used the image of like rolling a dice. Why that?Beah: Yeah, because answers from AI are non-deterministic, meaning, they are generated on the spot using a prediction basically of what you want to hear um based on some huge data training set and They can be wrong and they can be like totally wrong. They can hallucinate and be crazy, so that I think is one of the reasons that people are rightly cautious about using AI to answer their questions because they are not guaranteed right answers. And so Running the same question on different two different models gives you kind of a sense of the universe of possibilities and a little bit more data to make an informed decision.Tatum: Yeah, and it seems like DuckDuckGo is uniquely able to build a feature like this because an AI company would never encourage you and has no reason to show you an answer from a different company’s models. Whereas, you know, we have all these models in the same place with a privacy layer that is now letting us do this kind of fun and useful thing of seeing two answers side by side. How did this feature come to be? Like what kind of problem is it solving for people as they search?Beah: There’s a few answers to that. Anecdotally, when I’m using AI, which I use Duck.ai every day many times over, I often find myself kind of wanting to like second guess or fact check or get another opinion on. The answers that I’m getting. sometimes you’re like asking for some, like, you know, what’s Tom Hanks’ birthday? There’s one answer to that that’s correct. All the other answers are wrong. most of the things that I’m using AI for don’t have one right answer. And so getting kind of a a spread of perspectives is is part of my reasoning and decision making process. So that’s like the anecdotal answer. There’s like a more kind of meta-societal answer, which is people don’t trust AI answers for good reasons because they often, spit out an answer that is just one perspective and maybe wrong in varying degrees, but they present it with great confidence and don’t really necessarily signal the extent to which it could be wrong or how it might be wrong or what other answers might be. And so I think second opinion gives you a literally a one tap or one click way to mitigate that downside of using AI.Tatum: Yeah, so it seems like it solves, a problem for the user or it’s useful to that one person on their search of getting, you know, more information or a second, a second perspective. But it seems to also be useful as a critical thinking tool or useful to shape the way that people use AI search. It this made me think of some research that Microsoft did about how relying on AI help affects people’s cognitive engagement with the task that they’re doing. And a lot of people pointed at this study saying, like, look, using AI makes you stupider. when I went and read the study, what it seemed to be more related to was actually your confidence in the AI’s answers. The more kind of confident you become that it’s correct, then the less critical thinking you’re you’re doing. Whereas when you have a healthy amount of skepticism, you it doesn’t affect your cognitive engagement the same way. So so how can a feature like this kind of help shape the way that people use AI to make it kind of less risky, more useful?Beah: Yeah, I mean I think like an interesting analog is like if you were doing research on something, the old fashioned way without AI, you would probably read several sources. Like if you’re planning a trip, you might read like this guide book and this person’s blog post and this official website. And so, you know, AI is handy in that you can kick a button and get like one tidy answer. But if that tidy answer is misleading or incomplete, then that’s problematic. And so my hope with second opinion is that it gives you an equally, low friction way to round out those data points a bit and kind of require or accommodate a little bit more critical thinking where it’s appropriate,Tatum: Is it fair to say that the different models and different companies excel at different things? And as a lay person, is there any hope for me to like know what they are?Beah: There’s no hope for you, Tatum. Tatum: No!Beah: Yeah, no, I I it’s a good question. I I mean I do think the short answer is no. I think they’re like the the things are changing too fast and the nuances are too great. I think that there are some dimensions at which a consumer could make informed choices, like one that I think probably is reasonable is you might have an intuition of whether your question is like, a very quick answer is sufficient or whether you need it to do some like deeper thinking and research and challenging itself. And so on a given model, you can turn the reasoning up or down. but like in terms of the distinction, you know, when you’re trying to figure out how to like remove butternut squash soup from a t shirt, the distinction between GPT six Luna and GPT 5.6 Luna and Claude latest model, like I do not think that a normal human could or should need to like ho… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit insideduckduckgo.substack.com
In this episode, Jeffrey (Operations) and Anne (People Ops) discuss how performance reviews work in a distributed leadership model, and how the process has scaled as we’ve grown. If you have feedback on Duck Tales, or episode ideas, email us at [email protected]: (1) The audio, video (above), and transcript (below) are only lightly edited and may contain minor inaccuracies or transcription errors. (2) This website is operated by Substack. This is their privacy policy.Jeffrey: Hello everyone, and welcome to Duck Tales, where we go behind the scenes at DuckDuckGo. We discuss the stories, technology, and the people that help build privacy tools for everyone. In each of these episodes you’ll hear from the employees about our vision, product updates, engineering, or things like approaches to AI.Anne: There’s a lot ofJeffrey: My name is Jeffrey and I’m on the internal efficiency team at DuckDuckGo.Anne: Yeah,Jeffrey: And today I’m joined with my colleague Anne. Anne, do you want to introduce yourself?Anne: Hi, I’m Anne. I’m on the People Ops team at DuckDuckGo. It’s been about five years now, which I can’t believe, but lots of exciting stuff over that time.Jeffrey: Great. Today we’re gonna be talking about our internal performance reviews and how we run them. And how would you describe our performance review process to someone who’s never heard of DuckDuckGo?Anne: Well, I think the important thing to start with is sort of describing DuckDuckGo’s distributed leadership model, because with distributed leadership, that’s going to feed into performance reviews. And so the short answer I would give with that is that there’s no one decider of performance. There’s multiple different ways, multiple different people that give input, as well as a really strict requirement that it be evidence-based. And we’ll get into this a bit later, I’m sure. But we’ve done a lot of work on the evidence-based piece and being an asynchronous organization really helps with that because mostly everything is written down. So that’s that’s the high level that I would give.Jeffrey: Who do we how do we decide what collaborators get involved with each person’s reviews?Anne: Yeah, this has been a really interesting question over the years. And I would I would just love to brag a bit about how we used to do it when it was, you know, we were a smaller organization and then talk about how we’ve evolved that because well, I think way long ago it was the organization was small enough to just kind of know. You knew who should be giving input for who. And then the organization grew to the point where we needed help figuring out, right? You can’t one person couldn’t hold it all in their head.And so you very generously helped us create an algorithm that put out a spreadsheet that basically it ingested information about people’s leadership relationships to one another, their work overlap with one another, and their experience giving feedback, among other things, calculated all of those relationships, also taking into account load.Because you know, maybe one person should review 50 people, but that’s just too many, right? So balancing those trade-offs and then making a suggestion, which was really cool. And then those suggestions obviously had to be reviewed by humans and still, you know, load adjusted and everything. And there were several rounds of human review. So that was great. And then that also came to the point where we outgrew that because even those suggestions were gonna start fraying at a point, and the human review was cumbersome.And so we’ve moved, I think quite naturally toward leaning on functional calibrators who are closer to the functional work and then pulling in the objective side of the house, which is sort of like where work is getting executed and having those be the default inputs for people. But yeah, that’s kind of how that’s changed over time. And it’s really, it’s been a really exciting problem, fun problem to be a part of.Jeffrey: For the most part it’s scaled with as the company has grown and we’ve just had to make small changes here and there.Anne: Yeah, I it’s as a people person, I also say, you know, people say how do we keep our culture as we grow? And this is similar to that where you say we don’t keep something, right? We s how do we scale something in accordance with our values as we grow? And then this I think would be a really good example of that in a really unique one too.Jeffrey: Cool. What makes evaluating performance here different from a typical company?Anne: Well, similar to what I said before, right? Distributed leadership means you have to figure out who it’s not like a managerial chain where the manager writes a performance review with peer feedback and then that gets approved by their manager and that gets approved. You know, it’s not a chain of approvals, it’s a collaborative process, which is also why that was one of the main reasons. There were several, but one of the bigger but bigger blockers for us purchasing performance review software from a company was that none of them had the functionality to have the level of collaboration that we have, like back and forth collaboration. And so there’s that. And then the real just like I said earlier, reliance on data. We are an asynchronous organization that really leverages processes in our project management tool, Asana, to fill the gaps of what a lot of live meetings would be. And I would imagine other Duck Tales have talked about no meeting Wednesdays, which is like for real. At other companies, it’s kind of in air quotes, but I would say here, not all of their companies to be clear, but oftentimes that can slip. But here it’s pretty, pretty legit. And so yeah, we’re generally meeting light, and so everything is in Asana, and you can pull that in to work summaries. And that’s also something you’ve been involved with, is really having a set of validated summary of work over the period of the year with links, right? So you can actually go and dig into the work over the course of the year as needed. And yeah, that’s the other thing I would really be I would say is is unique that the reliance on evidence and links and things you can actually see and look at and review is pretty high.Jeffrey: Right. You touched on this a little bit, but can you go into how the process has scaled as we’ve grown? Or evolved.Anne: Yeah, so yeah, that was one of the things is obviously sw figuring out how to fill those collaborative evaluator roles. Another is automation. We’ve really, you know, built our own system that integrates with where work gets done for us, which is Asana. And as a people operator, I feel blessed that I’m just given IT resources to be like, hey, you need this system to work. Here’s some really awesome skilled IT folks to help you make it a reality. And we have some really cool people on the team working to build our own performance review system that integrates exactly with where work happens for us. And so I’d say that is one that we’ve built that system and it’s evolved over time alongside other systems, right? So we have things like our daily asynchronous personal stand-up.Right. So everybody does a stand-up for themselves every day and that gets recorded. And so then that can filter back into this whole performance review process because you have a record of what you were focused on every day. You have a record of the project you were focused on every week. You we have a whole summary of the relationships of your project advisory, career advisory, everything. You know, we’ve basically been automating more of these things to be centralized in a way that’s digestible for users. And those two things have really evolved together in in a way that’s pretty cool.Jeffrey: I’m really proud of the our daily stand up we call our daily one must, but it’s been with us for a while now and it’s all asynchronous where people can fill it in in the morning and then everybody who needs to know ca… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit insideduckduckgo.substack.com
In this episode, Beah (Chief Product Officer) and John (Support) discuss our customer support process, why we read all tickets (good or bad), and how we actually use them to improve all aspects of the user experience.If you have feedback on Duck Tales, or episode ideas, email us at [email protected]: (1) The audio, video (above), and transcript (below) are only lightly edited and may contain minor inaccuracies or transcription errors. (2) This website is operated by Substack. This is their privacy policy.Beah: Hello, and welcome to Duck Tales, where we go behind the scenes at DuckDuckGo and discuss the stories, technology, and people that help build privacy tools for everyone. In each episode, you’ll hear from employees about our vision, product updates, engineering, or approach to AI. Today you’re gonna hear about how we do support at DuckDuckGo, and my guest is John. John, do you wanna introduce yourself briefly?John: Yeah, for sure. Yep, I’m John. I work within our marketing and communications team. And for the past few years, my main goal has been managing and improving how our support operates for the DuckDuckGo subscription and beyond.Beah: Sweet. So if you’ve used DuckDuckGo support, perhaps you’ve gotten a message from John or one of the other teammates who we’ll learn more about in this call or in this pod. So I’m Beah. If you haven’t met me, I’m on the product team at DuckDuckGo. All right, let’s jump in. I’m gonna ask John some questions and we’ll go from there. So tell me John, just to kind of set the scene, what sort of things do we provide customer support for?John: A lot. The bulk of the support that we offer is through the DuckDuckGo subscription. So for us who handle support, it means handling things like billing questions, assisting with activation across multiple devices, questions about the plans that we offer, and more technical troubleshooting related things. The subscription can be bought a few different ways, each with its own different path to activation. So a good bit of the support that we offer is helping our users navigate these paths to get more comfortable with our subscription and its features. So some of our great front-end team members built a support form where most of our tickets run through. It was built to be kind of as self-service as possible, but a category is picked and depending on what the selection is, a potential solution gets surfaced. This way, plenty of users can get an answer without really needing to submit anything or wait for us to respond to them. But basically, our help pages kind of sit behind this and there’s links to that support form on every one of our subscription help pages. It’s the first stop for most of these tickets. We’ve been piloting an AI agent on a few help pages and I’m sure we’ll get into that as well.Beah: So like if we don’t, if we can answer, if we can get people an article right then and there that answers their questions, that’s the best case scenario for everybody because they get an immediate answer, but if not, then we have a process to kind of hand it off to a human or an in-between, which is like AI assisted answers.John: Exactly. That’s right.Beah: And maybe I should say like before we had the subscription, which is the first paid product that DuckDuckGo offered, and the only one we offer, we didn’t really have a support team or support process. I mean, we had emails for different things, but like effectively we didn’t have to worry about customer support. And it was the introduction of the paid subscription that sort of like brought this problem to our doorstep and to you. Is that fair to say? Yeah, yeah.John: Yes. Absolutely. Yeah. Yeah. Perfect.Beah: Okay, cool. So tell me a little bit more about like how this all works like team-wise, who’s working on this, how have we structured that?John: Absolutely. We have a small but mighty team. So when that subscription first launched, there were a few of us that kind of rotated handling these support tickets. After a few months, we streamlined it significantly to where I was the only one who was handling things, which probably seemed like it was unfeasible and it really was. Early last year, we brought on an awesome specialist as...Beah: It, I mean it, it worked, you just didn’t sleep great.John: Yes, yeah, it worked. It worked. But there was a lot that was dependent on me and it caused a lot of lead time for some people to get responses. It was a lot to manage basically. So we brought on an awesome specialist as we continued to grow. She’s been awesome in the organization and the optimization of our entire end-to-end process. She’s got more support experience than I do by far and is a great Swiss Army knife of skill sets. So with her help, we, along with dozens of other teammates throughout the organization, we kind of overhauled the whole support structure at DuckDuckGo. And then recently, earlier this year, we brought on two more support rockstars to kind of help shoulder the ticket load to ensure that our users aren’t waiting too long before getting a real human response. So they’ve been a great addition. They’ve been working fantastically. And they’ve added an additional support layer to the mix. But yeah.Beah: Got it. And you, you, you mentioned like lots of other people. I mean, so there’s like the people who are actually writing the emails back. And then I think part of what you’re getting at, tell me if this is right, is like, you know, they are likely in many, not in all cases, but in some cases, like need to go talk to an engineer to understand what’s going on, or like a product manager or somebody else who’s been working on the product directly day in and day out and like they’re just kind of interfacing between like this huge, you know, pool of resources who know different things about DuckDuckGo.John: Yes, yeah, and that, the whole concept of working out in the open really helps make that a lot easier. So we have engineers and developers that really plug in whenever a support signal points to the need to escalate for a better response that we don’t know or we can’t handle.Beah: It has been for you.John: So that direct line to the actual builders that are behind the scenes ensures that we go straight to the source and we don’t have to wade through multiple layers of people to get an answer that’s accurate.Beah: Gotcha. Cool. So tell me, like, kind of riffing off of that, how does this fit into like our broader approach to customer feedback loops? Like we have this email support system, but we also like interface with users or get feedback from users like on social media or, you know, all these various ways, which I would say for context for listeners, like we really, we like really read that stuff and really pay attention to it. Like we’re pretty, I’d say we’re pretty obsessed in fact with understanding. Like if you’re sending us, if you’re a user and you’re sending us signals about your experience, like we are pretty hungry for that. So yeah, tell me about like the boundary, the interface boundary between like that kind of feed, those customer feedback loops and the support that you’re talking about.John: Yeah, so it’s a big circle. So essentially, the support piece to me, from what I’ve seen, I feel like I’ve been in every aspect of support, internal and external, that we offer. And this support for the subscription that we do is truly one of the most honest and raw feedback channels that we have. Most of the time, people write in when there’s a problem. Like, you’re not going to be contacting support to be like, hey, great job. Each ticket gets categorized in those categories.Beah: Though feel free to.John: Yeah, you’re more than welcome to, yes.Beah: Yeah.John: But we don’t even, we don’t handle things that are just a subscription, we handle any and all questions that come in, which I might get, we might get a deluge of tickets with me saying that. But, that said, we get a really wide r… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit insideduckduckgo.substack.com
In this episode, Marc (Engineering) and Zach (Data Science) discuss how we use AI internally: our most common uses, how we use it privately, and why our principles matter more when using AI, not less. If you have feedback on Duck Tales, or episode ideas, email us at [email protected]: (1) The audio, video (above), and transcript (below) are only lightly edited and may contain minor inaccuracies or transcription errors. (2) This website is operated by Substack. This is their privacy policy.Marc: Hi, and welcome to Duck Tales, where we go behind the scenes at DuckDuckGo and discuss the stories, technology, and people that help build privacy tools for everyone. In each episode, you’ll hear from employees about our vision, product updates, engineering, or approach to AI. My name is Marc and I’m on the engineering team. I have with me Zach. Zach, you want to introduce yourself?Zach: hi, yeah. I’m Zach Deane-Mayer on our data science team here at DuckDuckGo. I am still a Duckling, so I’ve been here for about ten months. and I work on building our internal AI systems.Marc: Great. yeah, so today we’re gonna talk even more about AI, which is Zach’s specialty. I think today we’re gonna talk specifically about how we use Duck or sorry, how we use AI internally at DuckDuckGo. so yeah, I guess to start out, as a company, you know, we’ve adopted AI pretty pretty heavily internally as a tool to help us move faster. can you talk a little bit, Zach, about the the approach that we’ve taken here? Given that I think this you were in on the ground floor with this, right?Zach: Yeah, yeah. So DuckDuckGo as a company takes I I think a somewhat unique approach to AI as we take a unique approach to everything we do. We very much have a culture of of things like first principles thinking and and you know our own spin on things.Marc: Right.Zach: And a very important part of what we do are our privacy and security. so before we rolled out many of these tools, we spent quite a bit of time internally getting comfortable with their failure modes and the blast radius potential for for those failures. One of the first places we started using AI a lot was with coding tools. So right off the bat with Cursor and then Claude Code. And you know, one, the models are very, very good at writing code. But then two, if you are effectively using tools like git and GitHub, an agent that’s limited to writing code can only do so much damage if your code base is backed up in GitHub and you don’t let, for example, people force push to main or whatever like that. Like if your GitHub is properly configured. And so we had a lot of questions like that early on. And then, you know, once once we were confident, we really were able to kind of let open the floodgates and let people really start start using both Cursor, Claude Code and now to a lesser degree Codex to to write code and automate as much of engineering as they can.Marc: Yeah, yeah, that’s great. you mentioned privacy, right? Like that is obviously it’s a core tenet of our products. It’s also a core tenet of how we operate here. and yeah, to your point, we do tend to do things a little bit differently. so I’m curious how the privacy kind of shaped our internal workflows with respect to AI, given that, you know, w we even though we don’t collect user data, we do still have things that we obviously don’t want to to share more broadly.Zach: Yeah. Yeah, absolutely. so our privacy engineers very much think of like a an information hierarchy of stuff that is you know very I don’t know what the word is I want to use for the scale, but there’s a there’s a high to low scale. and so there’s certain information that we don’t even save to disk in our production servers. There’s certain information that is stored in memory and is never retained anywhere in our systems.Marc: Right.Zach: and that is fundamentally the safest form of data. If you don’t if you don’t store a piece of information, it’s it’s very hard to accidentally store it in the wrong place and in a way that you don’t you don’t want to do. and and that kind of principle thinking applies to AI too. Like if if an AI system doesn’t have access to certain data, it It can’t do the wrong thing with that data. and one of those ways to prevent access is just by by fundamentally not not storing the data in the first place. As you go through that hierarchy, you know, there there’s information that we’re more and more comfortable with working on internally, like for example, you know, time series traffic of you know how many users are on our various websites, like that sort of aggregated data that can’t be tied to an individual person. That’s a lot safer to start saying, hey, I’m gonna, you know, I’m on the data science team, I’m gonna do some data science work and look at, you know, whatever, whatever it is that the set of questions I have. and then I think the kind of the bottom piece that is incredibly important is we pay a lot of attention to our data processing agreements that we have with all of our vendors, but especially our AI vendors. and the contractual agreements you have with people about what they are and aren’t allowed to do with your data are are also very important. so so yeah, there’s there’s a spectrum of things and you go talk to any privacy engineer, I mean you can very quickly learn how just how deep the problem goes.Marc: Yeah, yeah, it’s interesting you mentioned principled thinking, right? Like I I think that’s something that is a core part of the culture here. And I I think it’s fair to say that we have, you know, spent a lot of time talking about how to adapt AI to our principles as opposed to adapting our principles to AI, right? which I feel like you see a lot in the industry right now.Zach: Yeah, yeah. Yeah. Yeah. And and and and that’s I mean that’s a that’s a great point. Like two of our principles that matter a lot to me personally are questioning assumptions and validating direction.Marc: Absolutely, yeah.Zach: and you know, I’m I’m like the the AI, you know, waving, you know, the flag and the the pom-poms and saying, let’s go AI internally.Marc: Right.Zach: but like I I find I have to like, you know, remind people, just because we’re using AI doesn’t mean we throw our principles out the window. Like,Marc: Absolutely.Zach: I am you know, again again as a leader here, I am more interested in like like I want to validate direction too. And so I am very interested to hear from people places where AI isn’t working. Like, like I want to see, you know, the PR that’s a 7,000 line of code wall of text where a team’s going, whoa, like we can’t we can’t review this, let alone ship it.Marc: Right.Zach: And those those kinds of failure modes, like AI is rife with them. And we don’t, you know, we don’t just look at an AI’s output and say, well, an AI made it, so let’s ship it. Like you you should use AI as as you know, a lever against, you know, with your principles, not not as a as a reason to throw your your principles out the window. But like again, like just questioning assumptions and validating direction, like you know, AIs are notoriously bad at questioning assumptions.Marc: Right.Zach: Like this will happen all the time, even with the latest models, where you’ll be like, hang on a sec. Like you said X and then you said Y, which implies not X, like, but you never connected the pieces together in in in in the chain of logic.Marc: Sure, sure.Zach: and so I I think I think your principles matter more when you’re using AI.Marc: that’s interesting. Yeah. Yeah, that I think that’s really well put. actually leads us into our next question to a degree. there’s yeah there’s a lot of hype right now, obviously with AI. I mean to put it mildly, right? the hype cycle is has been super interesting. there’s a lot of concern about AI in the workforce today, right? And we’re certainly not immune to that, although we don’t really see it that way. as a company. So maybe can you… This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit insideduckduckgo.substack.com








