Podcast appearances and mentions of david cramer

Scott and Wes break down the Model Context Protocol (MCP), a new open standard that gives AI agents secure, tool-like access to your dev environment. They cover how it works, why it's a big deal for AI coding workflows, and real-world use cases like GitHub, Sentry, and YouTube. Show Notes 00:00 Welcome to Syntax! 00:49 The lore of ICP. Wes MCP Shirt. 03:09 Brought to you by Sentry.io. 03:33 What is MCP? 05:06 The steps of AI coding. 07:11 MCP hosts. 07:28 MCP clients. 07:35 MCP servers. 08:24 Why you might want to do this. 10:39 How this works in VS Code. 14:10 Wes built an MCP server. SVGL. 14:57 Playwright. 17:24 Sentry's implementation. Building Sentry's MCP with David Cramer. 18:54 YouTube implementation. 21:19 DaVinci Resolve implementation. Smithery. 23:02 Postgres. 24:40 Transport protocols. 24:49 STDIO. 25:19 SSE. 25:32 Streaming. 26:24 Writing you own MCP server. 26:28 FastMCP. 27:00 Cloudflare. 28:01 Data validation. 28:47 Standard schema. Episode 873. 29:27 Other parts of MCP. 29:35 MCP resources. 30:37 MCP prompts. 30:48 MCP roots. 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

David Cramer, co-founder of Sentry talks M&As and why they should be utilized more when you don't achieve huge success. Plus we talk about the importance of good branding.We discuss:The biggest mistake small startup founders make by not exploring potential acquisitions.The role of ego in startupsProduct-market-fitHiring entrepreneurial talent and why acqui-hiring is so big.The significance of branding beyond just marketing – how it builds trust, recognition, and demand.Sentry's approach to branding, emphasizing authenticity, community, and accessibility.What DevTools can learn from Liquid Death and PorscheWhy brand mattersThis episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign-On and audit logs. https://workos.com/Links:David Cramer's blogDavid Cramer on XSentry

Today, we have David Cramer on the show. David is one of the co-founders of Sentry, an application monitoring tool that's one of the most widely-adopted tools for developers. Sentry does over 300,000 events per second on average, and there's a lot of fancy work to process these application errors, from rate limiting to fingerprinting to counting to source map unminifying. We walk through some of the architectural changes and systems design work here, including some of David's thoughts on shipping. David and Sentry also have a unique approach to developer marketing. They do some cool things -- sponsoring and then buying the amazing SyntaxFM podcast, sending $100k of free gifts to developers, and launching the Open Source Pledge with $500k donated to open source developers.

We're fortunate on the Fireside podcast to be able to speak to so many people at the top of their game, and today we're revisiting our chat from earlier this year, with someone who's no different. David Cramer is the Co-Founder and CTO of Sentry, the app monitoring platform designed to quickly help developers get to the root of code problems. David has helped bring Sentry to the top of the pile in this category - to the extent where, in his words, they don't have competitors, they have “ankle-biters”. But does “heavy is the head that wears the crown” have any bearing for a company at the top? We're excited to find out. David has worn many hats at Sentry since its founding, but as a software engineer at heart, he's currently taking up the position of CTO. He dives into how strategy helped set Sentry apart in the early days, and how they manufactured the way they wanted the business to run, as opposed to simply responding to hurdles as they came up. The Sentry team, ultimately, is made up of developers, and David explains how this fact has led to the creation of a platform that is highly developer focused, in both user experience and in sales. He tells us about how yearly price hikes are not something Sentry wants to engage in, and how valuing affordability has allowed them to skyrocket in popularity since their first launch. Community is at the forefront of David's current plans for Sentry, and he talks us through this, and other aspects of what he hopes to achieve with the company the future. Reach out to David here: https://www.linkedin.com/in/dmcramer/ Check out Sentry here: https://sentry.io/welcome/ Find out more and listen to previous podcasts here: https://www.voxgig.com/podcast Subscribe to our newsletter for weekly updates and information about upcoming meetups: https://voxgig.substack.com/ Join the Dublin DevRel Meetup group here: www.devrelmeetup.com

In this episode of Breaking Changes, Postman Head of Product-Observability Jean Yang sits down with David Cramer, co-founder and CTO of Sentry. David shares his journey as an engineering leader and discusses the importance of a developer-centric approach in monitoring. Tune in as he reflects on implementing smooth changes, embracing emerging technologies, and navigating challenges in leadership and hiring. David emphasizes the value of consistency in values and principles—and reveals surprising changes he allowed, like embracing sales and AB testing. He also shares his insights on transitioning from CEO to hiring an external CEO.     For more on David Cramer, check out the following: LinkedIn: https://www.linkedin.com/in/dmcramer/ Twitter: https://twitter.com/zeeg Personal Website: https://cra.mr/archive/ Sentry Website: https://sentry.io/welcome/   Follow Jean on Twitter/X @jeanqasaur. And remember, never miss an episode by subscribing to the Breaking Changes Podcast on your favorite streaming platform or Postman's YouTube Channel—just hit that bell for notifications.   #BreakingChanges #apis #postman #sentry #TechLeadership #EntrepreneurialJourney #ProfessionalGrowth #TechInnovation #StartupSuccess #BusinessInsights #EntrepreneurMindset #careersuccess #PersonalGrowthJourney #engineering

Explore the evolution of both a product and the role of its co-founder in this CTO podcast featuring David Cramer (co-founder + CPO @ Sentry). You will discover the pros and cons of each stage in Sentry's journey (open source -> bootstrap -> VC) and why David's role evolved (CEO -> CTO -> CPO). Listen to find out

Milin Desai is the CEO at Sentry, an application monitoring tool for developers. Sentry has recently passed two key milestones: 100K customers and over $100M in ARR. Before Sentry, Milin was a GM at VMware and scaled their cloud networking into a billion-dollar business. Prior to stepping into leadership roles, Milin was a PM at Riverbed and a software engineer at Veritas. — In today's episode, we discuss: The key ingredients of Sentry's success Sentry's developer-centric approach Lessons on pricing, packaging, and product from VMware Being an external CEO at a startup Forging successful relationships with founders — Referenced: Building for the Fortune 500,000: https://blog.sentry.io/building-for-the-fortune-500-000/ Carl Eschenbach: https://www.linkedin.com/in/carl-eschenbach-980543/ Chris Jennings: https://www.linkedin.com/in/chriskjennings/ David Cramer: https://www.linkedin.com/in/dmcramer/ FRC's product market fit framework: https://pmf.firstround.com/ Martin Casado: https://www.linkedin.com/in/martincasado/ Pat Gelsinger: https://www.linkedin.com/in/patgelsinger/ Raghu Raghuram: https://www.linkedin.com/in/raghuraghuram/ Riverbed: https://www.riverbed.com/ Sentry: https://sentry.io/ Todd Bazakas: https://www.linkedin.com/in/todd-bazakas-b5a2533/ Veritas: https://www.veritas.com/ VMware: https://www.vmware.com/ — Where to find Milin Desai: LinkedIn: https://www.linkedin.com/in/milin-desai-464757/ Twitter/X: https://twitter.com/virtualmilin — Where to find Brett Berson: LinkedIn: https://www.linkedin.com/in/brett-berson-9986094/ Twitter/X: https://twitter.com/brettberson — Where to find First Round Capital: Website: https://firstround.com/ First Round Review: https://review.firstround.com/ Twitter/X: https://twitter.com/firstround YouTube: https://www.youtube.com/@FirstRoundCapital This podcast on all platforms: https://review.firstround.com/podcast — Timestamps: (00:00) Introduction (03:03) Joining Sentry as an external CEO (06:27) The CEO/founder relationship (09:37) Lessons from VMware (13:04) What PMs did differently at VMware (18:04) Becoming the need, not the want (20:53) Scaling Sentry (23:07) Building for the “Fortune 500,000” (27:02) Open versus closed source product (30:43) The key ingredients to Sentry's success (36:21) How Milin updated his playbook at Sentry (38:49) Focus on packaging, not pricing (40:29) “Build for the many, not the few” (41:53) Sentry's B2D model (45:10) The second product mindset (51:03) Contrarian take on building for enterprise (52:50) Several people who influenced Milin

We're fortunate on the Fireside podcast to be able to speak to so many people at the top of their game, and this week's guest is no different. David Cramer is the Co-Founder and CTO of Sentry, the app monitoring platform designed to quickly help developers get to the root of code problems. David has helped bring Sentry to the top of the pile in this category - to the extent where, in his words, they don't have competitors, they have “ankle-biters”. But does “heavy is the head that wears the crown” have any bearing for a company at the top? We're excited to find out. David has worn many hats at Sentry since its founding, but as a software engineer at heart, he's currently taking up the position of CTO. He dives into how strategy helped set Sentry apart in the early days, and how they manufactured the way they wanted the business to run, as opposed to simply responding to hurdles as they came up. The Sentry team, ultimately, is made up of developers, and David explains how this fact has led to the creation of a platform that is highly developer focused, in both user experience and in sales. He tells us about how yearly price hikes are not something Sentry wants to engage in, and how valuing affordability has allowed them to skyrocket in popularity since their first launch. Community is at the forefront of David's current plans for Sentry, and he talks us through this, and other aspects of what he hopes to achieve with the company the future. Reach out to David here: https://www.linkedin.com/in/dmcramer/ Check out Sentry here: https://sentry.io/welcome/ Find out more and listen to previous podcasts here: https://www.voxgig.com/podcast Subscribe to our newsletter for weekly updates and information about upcoming meetups: https://voxgig.substack.com/ Join the Dublin DevRel Meetup group here: www.devrelmeetup.com

Whether you're a seasoned coder or just starting out, the tech you choose can make a big difference. Sometimes choosing the wrong tech can be frustrating and ruin a great project. David Cramer, Co-Founder and CTO of Sentry, joins Chuck and Robbie to talk about some well-known frameworks in the tech space. They discuss the challenge of selecting a good tech stack. David sheds light on the considerations behind choosing Vercel for Remix apps and the complexities of integrating Fastify for backend services. David also explains the downsides of GraphQL and why it is only relevant for Facebook. Later, he reflects on his gaming nostalgia, sharing experiences of gaming as a teenager and the struggle to find time for immersive gaming as an adult. In this episode, David talks to Robbie and Chuck about hot takes on GraphQL, crucial development stack decisions, and some of the challenges with adult gaming. Key Takeaways [00:42] - Introduction to David Cramer. [01:26] - A whiskey review: High Wire Distilling Co New Southern Revival Jimmy Red Bourbon [10:10] - David talks about the history of Sentry and lessons learned. [14:38] - Tech hot takes. [26:05] - David's take on work-life balance. [33:36] - Why David built Peated. [42:03] - David talks about his interest in eFoils. [45:07] - Chuck, Robbie, and David discuss gaming. [48:18] - If David wasn't in tech, what career would he choose? Quotes [19:31] - “The maturity I've gotten as a developer over the years is to stop caring about silly things.” ~ David Cramer [27:42] - “Nothing great in history has ever been done without a lot of effort.” ~ David Cramer [34:51] - “One of the best things you can do, if you actually want to get good at something is to have a side project.” ~ David Cramer Links David Cramer LinkedIn David Cramer Twitter Sentry Peated High Wire Distilling Co New Southern Revival Jimmy Red Bourbon Starburst Jim Beam Maker's Mark Jack Daniel's Tennessee Whiskey Twitter Django GitHub Microsoft Tailwind CSS Vanilla CSS Remix Next JS Dropbox Facebook National Geographic Rust GraphQL Google Bottle Blue Book Vercel React Miami The Primeagen World of Warcraft Steam Factorio SimCity The Legend of Zelda: Tears of the Kingdom FIFA 23 Walmart Spotify Connect with our hosts Robbie Wagner Chuck Carpenter Ship Shape Subscribe and stay in touch Apple Podcasts Spotify Google Podcasts Whiskey Web and Whatnot Whiskey Web and Whatnot Merch Need a last minute holiday gift and want to support the podcast? We have just the thing! Pick up a Whiskey Web and Whatnot Holiday Sweater on our new merch store: https://whiskey.fund/ --- Send in a voice message: https://podcasters.spotify.com/pod/show/whiskey-web-and-whatnot/message

In this new episode of Sit Down Startup, Adam interviews Sentry's founder David Cramer, who shares insights from his illustrious journey that led to successfully raising $217 million. Tune in as David delves into diverse topics such as unraveling unique product monetization, cultivating unwavering belief in success (00:05:41), the power of focus and core concepts (00:08:45), and managing feedback at scale (00:18:37). The conversation touches upon customer engagement wisdom: distinguishing valuable feedback and exploring how focus and determination pave the path to tech success. David emphasizes the criticality of aligning with prospects who inherently understand and connect with your vision rather than convincing all.Thank you to this week's partners Ignition and Slack!Ignition is a GTM operating system which helps unlock revenue opportunity by aligning product, marketing, and sales teams around new market initiative launches, with a single suite for planning, execution, and measurement. Zendesk Startups members get 90% off Ignition for their first year when they enter the coupon code ZENDESK90 at checkout. http://haveignition.comCheck out Slack for 25% off Slack Pro - Unlock features like huddles, Slack Connect, automations and unlimited apps in Slack. http://slack.com/promo/partner?remote_promo=1d1d4669

This week PDM coaches Hugh + Ryan talk with David Cramer, Co-founder and CTO of Sentry!They delve into the journey of Sentry and its rise as an essential tool for developers.David highlights how Sentry's developer-first approach significantly contributed to its growth.They touch upon community-centric decisions and the emphasis Sentry places on giving back.The discussion also ventures into the synergy between Sentry and Python and the attributes they prioritize when hiring.This episode is a treasure trove of insights for anyone in the tech industry.Chapters00:00 Introduction03:00 Wins of week06:32 What is Sentry?09:37 Growth of Sentry + developer centered14:20 Top down decisions + giving back18:24 Industry events and branding21:18 Sentry and Python synergies24:50 Htmx developments and Python features27:19 Attracting talent in Sentry31:10 Valuable attributes of people you hire34:43 Pairing app and infrastructure metrics41:06 "Blade runner concept" to debugging production system41:46 Key message / insight / final thought for audience45:48 What do you do in your free time?47:20 Books & videos tips: Cal Newport + YT construction content49:48 Wrap up and resources50:36 Outro musicLinks and resources:- Check out Sentry here- David Cramer on LinkedIn- Factorio game- Blade runner movie

Sentry is an application monitoring tool that surfaces errors and performance problems. It minimizes the need to manually look at logs or dashboards by identifying common problems across applications and frameworks. David Cramer is the co-founder and CTO of Sentry. This episode originally aired on Software Engineering Radio. Topics covered: What's Sentry? Treating performance problems as errors Why you might no need logs Identifying common problems in applications and frameworks Issues with Open Telemetry data Why front-end applications are difficult to instrument The evolution of Sentry's architecture Switching from a permissive license to the Business Source License Related Links Sentry David's Blog Sentry 9.1 and Upcoming Changes Re-Licensing Sentry Transcript You can help edit this transcript on GitHub. [00:00:00] Jeremy: Today I'm talking to David Kramer. He's the founder and CTO of Sentry. David, welcome to Software Engineering Radio. [00:00:08] David: Thanks for having me. Excited for today's conversation. What's Sentry? [00:00:11] Jeremy: I think the first thing we could start with is defining what Sentry is. I know some people refer to it as an error tracker. Some people have referred to it as, an application performance monitoring tool. I wonder if you could kind of describe in, in your words what it is. [00:00:30] David: You know, as somebody who doesn't work in marketing, I just tell it how it is. So Sentry started out doing error monitoring, which. You know, dependent on who you talk to, you might just think of as logging, right? Like that's the honest truth. It is just logging just a different shape or form. these days it's hard to not classify us as just an APM tool that's like the industry that exists. It's like the tools people understand. So I would just say it's an APM tool, right? We do a bunch of things within that space, and maybe it's not, you know, item for item the same as say a product like New Relic. but a lot of the overlap's there, so it's like errors performance, which is like latency and sort of throughput. And then we have some stuff that just goes a little bit deeper within that. The, the one thing i would say that is different for us versus a lot of these tools is we actually only do application monitoring. So we don't do any since like systems or infrastructure monitoring. Meaning Sentry is not gonna tell you when you need to replace a hard drive or even that you need new hard, like more disk space or something like that because it's just, it's a domain that we don't think is relevant for sort of our customers and product. Application Performance Monitoring is about finding crashes and performance problems that users would associate with bugs [00:01:31] Jeremy: For people who aren't familiar with the term application performance monitoring, what is that compared to just error tracking? [00:01:41] David: The way I always reason about it, this is what I tell new hires and what I would tell, like my mother, if I had to explain what I do, is like, you load Uber and it crashes. We all know that's bad, right? That's error monitoring. We capture the crash report, we send it to developers. You load Uber and it's a 30 second spinner, like a loading indicator as a customer. Same outcome for me. I assume the app is broken, right? So we also know that's bad. Um, but that's different than a crash. Okay. Sentry captures that same thing and send it to developers. lastly the third example we use, which is a little bit more. I think, untraditional, but a non-traditional rather, uh, you load the Uber app and it's like a blank screen or there's no button to submit, like log in or something like this. So it's kind of like a, it's broken, but it maybe isn't erroring and it's not like a slow thing. Right. Same outcome. It's probably a bug of some sorts. Like it's what an end user would describe it as a bug. So for me, APM just translates to there are bugs, user perceived bugs in your application and we're able to monitor and, and help the software teams sort of prioritize and resolve those, those concerns. [00:02:42] Jeremy: Earlier you were talking about actual crashes, and then your second case is, may be more of if the app is running slowly, then that's not necessarily a crash, but it's still something that an APM would monitor. [00:02:57] David: Yeah. Yeah. And I, I think to be fair, APM, historically, it's not a very meaningful term. Like I as a, when I was more of just an individual contributor, I would associate APM to, like, there's a dashboard that will tell me what's slow in my application, which it does. And that is kind of core to APM, but it would also, none of the traditional tools, pre sentry would actually tell you why it's broken, like when there's an error, a crash. It was like most of those tools were kind of useless. And I don't know, I do actually know, but I'm gonna pretend I don't know about most people and just say for myself. But most of the time my problems are errors. They are not like it's fast or slow, you know? and so we just think of it as like it's a holistic thing to say, when I've changed the application and something's broken, or it's a bug, you know, what is that bug? How do we help people fix it? And that comes from a lot of different, like data signals and things like that. the end result is still the same. You either are gonna fix it or it's not important and you ignore it. I don't know. So it's a pretty straightforward, premise for us. But again, most companies in the space, like the traditional company is when you grow a big company, what happens is like you build one thing and then you build lots of check boxes to sell more things. And so I think a lot of the APM vendors, like they've created a lot of different products. Like RUM is a good example of another acronym that lives with an APM. And I would tell you RUM is completely meaningless. It, it stands for real user monitoring. And so I'm like, well, what's not real about monitoring the application? Well, nothing's not real, but like they created a new category because that's how marketing engines work. And that new category is more like analytics than it is like application telemetry. And it's only because they couldn't collect the app, the application telemetry at the time. And so there's just a lot of fluff, i would say. But at the end of the day too, like developers or engineering teams, it's like new version of the application. You broke something, let's tell you about it so you can fix it. You might not need logging or performance monitoring [00:04:40] Jeremy: And, and so earlier you were saying how this is a kind of logging, but there's also other companies, other products that are considered like logging infrastructure. Like I, I would think of companies like Paper Trail or Log Tail. So what space does Sentry fill that's that's different than that kind of logging? [00:05:03] David: Um, so the way I always think about it, and this is both personally true, and what I advise other folks is when you're building something new, when you start from zero, right, you can often take Sentry put it in, and that's good enough. You don't even need performance monitoring. You just need like errors, right? Like you're just causing bugs all the time. And you could do that with logging, but like the delta between air monitoring and logging is night and day. From a user experience, like error monitoring for us, or what we built at the very least, aggregates the errors. It, it helps you understand the frequency. It helps you when they're new versus old. it really gives you a lot of detail where logs don't, and so you don't need logging often. And I will tell you today at Sentry. Engineers do not use logs for the most part. Uh, I had a debate with one of our, our team members about it, like, why does he use logs recently? But you should not need them because logs serve a different purpose. Like if you have traces which tell you like, like fast and slow in a bunch of other network data and you have this sort of crash report collection or error monitoring thing, logs become like a compliance or an audit trail or like a security forensics, tool, and there's just not a lot of value that you would get out of them otherwise, like once in a while, maybe there's like some weird obscure use case, but generally speaking, you can just pretend that you don't need logs most days. Um, and to me that's like an evolution of the industry. And so when, when Sentry is getting started, most people were still logs. And if you go talk to SRE teams, they're like, oh, login is what we know. Some of that's changed a little bit, but. But at the end of the day, they should only be needed for more complicated audit trails because they're just not a good solution to the problem. It's just free form data. Structured or not, doesn't really matter. It's not aggregated. It's not something that you can really use. And it's why whenever you see logging tools, um, not even the papertrails of the world, but the bigger ones like Splunk or Cabana, it's like this weird, what we describe as choose your own adventure. Like go have fun, build your dashboards and try to make the logs useful kind of story. Whereas like something like Sentry, it's just like, why would you waste any time trying to build dashboards when we can just tell you when something new is broken? Like that's the ideal situation. [00:06:59] Jeremy: So it sounds like maybe the distinction is with a more general logging tool, like you mentioned Splunk and Kibana it's a collection of all this information. of things happening, even though nothing's necessarily wrong, whereas Sentry is more Sentry is it's going to log things, but it's only going to log things if Sentry believes something is wrong, either because of a crash or because of some kind of performance issue. People don't want to dig through logs or dashboards, they want to be told when something is wrong and whyMost software is built the same way, so we know common problems [00:07:28] David: Yeah. I, i would say it's about like actionability, right? Like, like nobody wants to spend their time digging through logs, digging through dashboards. Metrics are another good example of this. Like just charts with metrics on them. Yeah. They tell me something's happening. If there's lots of log statements, they tell me something's going on, but they're not, they're not optimized to like, help me solve a problem, right? And so our philosophy was always like, we haven't necessarily nailed this in all cases for what it's worth, but. It was like, the goal is we identify an actual problem, like close to like a root cause kind of problem, and we escalate that up and that's it. Uh, versus asking somebody to like go have to like build these dashboards, build these things, figure out what data matters and all this because most software looks exactly the same. Like if you have a web service, it doesn't matter what language it's written in, it doesn't matter how different you think your architecture is from somebody else's, they're all the same. It's like you've got a request, you've got a database, you've got some cache, you've got all these like known, known quantity things, and the slowness comes from the same places. Errors are structured while logs are not [00:08:25] David: The errors come from the same places. They're all exhibiting the same kinds of behavior. So logging is very unstructured. And what I mean by that is like there's no schema. Like you can hypothetically like make it JSON and everybody does that, but it's still unstructured. Whereas like errors, it's, it's a tight schema. It's like there's a type of error, there's a message for the error, there's a stack trace, there's all these things that you know. Right. And as soon as you know and you define those things, you can just build better products. And so distributed tracing is similar. Hypothetically, it's a little bit abstract to be fair, but hypothetically, distributed tracing is creating a schema out of basically network annotations. And somebody will yell at me for just simplifying it to that. I would tell 'em that's what it is. But, same goal in mind. If you know what the data is, you can take action on it. It's not quite entirely true. Um, because tracing is much more freeform. For example, it doesn't say if you have a SQL statement, it should be like this, it should be formatted this way, things like that. whereas like stack traces, there's a file name, there's there's a line number, there's like all these things, right? And so that's how I think about the delta between what is useful information and what isn't, I guess. And what allows you to actually build things like Sentry versus just build abstract exploration. Inferring problems rather than having user identify them [00:09:36] Jeremy: Kind of paint the picture of how someone would get started with a tool like Sentry. Do they need to tell Sentry anything about their application? Do they need to modify their source code at all? give us a picture of how that works. [00:09:50] David: Yeah, like one of our fundamentals, which I think applies for any real business these days is you've gotta like reduce user friction, right? Like you've gotta make it dead simple to use. Uh, and for us there were, there was like kind of a fundamental driving constraint behind that. So in many situations, um, APM vendors especially will require you to run an agent a basically like some kind of process that runs on your servers somewhere. Well, if you look at modern tech stacks, that doesn't really work because I don't run the servers half my stuff's in the browser, or it's a mobile app or a desktop app, and. Even if I do have those servers, it's like an entirely different team that controls them. So deploying like a sidecar, an agent is actually like much more complicated. And so we, we looked at that and also because like, it's much easier to have control if you just ship within the application. We're like, okay, let's build like an SDK and dependency that just injects into the, the application that runs, set an API key and then you're done. And so what that translates for Sentry is we spend a lot of time knowing what Django is or what Rails is or what expresses like all these frameworks. And just knowing how to plug into the right signals in those frameworks. And then at that point, like the user doesn't have to do anything. And so like the ideal outcome for Sentry is like you install the dependency in whatever language makes sense, right? You somehow configure the API key and maybe there's a couple other minor settings you add and that gives you the bare bones and that's it. Like it should just work from there. Now there's a lot you can do on top of that to enrich data and whatnot, but for the most part, especially for errors, like that's good enough. And that, that's always been a fundamental goal of ours. And I, I think we actually do it phenomenally well. [00:11:23] Jeremy: So it sounds like it infers things about the application without manual configuration. Can you give some examples of the kind of things that Sentry knows without the user having to tell it? [00:11:38] David: Yeah. So a good example. So on the errors side, we know literally everything because an error object in each language has all these attributes with it. It, it gives you the stack trace, it gives you a lot of these things. So that one's straightforward. On the performance side, we use a combination of leveraging some like open source, I guess implementations, like open telemetry where it's got all this instrumentation already and we can just soak that in, um, as well as we automatically instrument a bunch of stuff. So for example, say you've got like a Python application and you're using, let's say like SQL Alchemy or something. I don't actually know if this is how our SDK works right now, but, we will build something that's aware of that library and make sure it can automatically instrument the things it needs to get the right information out of it. And be fair. That's always been true for like APM vendors and stuff like that. The delta is, we've often gone a lot deeper. And so for Python for example, you plug it into an application, we'll capture things like the error, error object, which is like exception class name exception value, right? Stack trace, file, name, line number, all those normal things, function name. We'll also collect source code. So we'll, we'll give you sort of surrounding source code blocks for each line in the stack trace, which makes it infinitely easier to consume. And then in Python and, and php, and I forget if we do this anywhere else right now, we'll actually even allow you to collect what are called stack locals. So it'll, it'll give you basically the variables that are defined almost like a debugger. And that is actually, actually like game changing from a development point of view. Because if I can go look in production when there's an incident or a bug and I can actually see the state of the application. , I, I never need to know like, oh, what was going on here? Oh, what if like, do I need to go reproduce this somehow? I always have the right information. And so all of that for us is automatic and we only succeed like, it, it's, it's like by definition inside of Sentry, it has to be automatic. Like if we ask the user to do anything whatsoever, we're failing. And so whenever we design any product or anything, and to be fair, this is how every product company should operate. it's gotta be with as little user input as humanly possible. And so you can't always pull that off. Sometimes you have to have users configure stuff, but the goal should always be no input. Detecting errors through unhandled exceptions [00:13:42] Jeremy: So you, you're talking about getting a stack trace, getting, the state of variables, source code. That sounds like that's primarily gonna be through unhandled exceptions. Would you say that's, that's the primary way that you get error? [00:13:58] David: Yeah, you can integrate in other ways. So you can like trigger our API to capture an, uh, an exception. You can also, for better or worse, it's not always good. You can integrate through logging adapters. So if you're already using a logging framework and you log their errors there, we can often capture those. However, I will say in most cases, people use the logging APIs wrong and the data becomes junk. A good, a good example of this is like, uh, it varies per language. So I'm just gonna go to Python because Python is like sort of core to Sentry. Um, in Python you have the ability to log messages, you can log them as errors, you can log like actual error objects as errors. But what usually happens is somebody does a try-catch. They, they capture the error they rescue from it. They create a logging call, like log dot error or something, put the, the error message or value in there. And then they send that upstream. And what happens is the stack trace is gone because we don't know that it's an error object. And so for example, in Python, there's actually an an A flag. You pass the logging call to make sure that stack trace stays present. But if you don't know that the data becomes junk all of a sudden, and if we don't have a stack trace, we can't actually aggregate data because like there's just not enough information to like, to run hashing on it. And so, so there are a lot of ways, I guess, to capture the information, but there are like good ways and there are bad ways and I think it, it's in everybody's benefit when they design their, their apt to like build some of these abstractions. And so like as an example, when, whenever I would start a new project these days, I will add some kind of helper function for me to like log an exception when I like, try catch and then I can just plug in whatever I need later if I want to enrich the data or if I wanna send that to Sentry manually or send it to logs manually. And it just makes life a lot easier versus having to go back and like augment every single call in the code base. [00:15:37] Jeremy: So it, it sounds like. When you're using a tool like Sentry, there's gonna be the, the unhandled exceptions, which are ones that you weren't expecting. So those should I guess happen without you catching them. And then the ones that you perhaps do anticipate, but you still consider to be a problem, you would catch that and then you would add some kind of logging statement to your code that talks to Sentry directly. Finding issues like performance problems (N+1 queries) that are not explicit errorsz [00:16:05] David: Potentially. Yeah. It becomes a, a personal choice to be fair at that, at that point. but yeah, the, the way, one of the ways we've been thinking about this lately, because we've been changing our error monitoring product to not just be about errors, so we call it issues, and that's in the guise of like, it's like an issue tracker, a bug tracker. And so we started, we started putting what are effectively like, almost like static analysis concerns inside of this issue tracker. So for example, In our performance monitor, we'll do something called like detect n plus one queries, which is where you execute a, a duplicate query in a loop. It's not necessarily an error. It might not be causing a problem, but it could be causing a problem in the future. But it's like, you know, the, the, the qualities of it are not the same as an error. Like it's not necessarily causing the user to experience a bug. And so we've started thinking more about this, and, and this is the same as like logging errors that you handle. It's like, well, they're not really, they're not really bugs. It's like expected behavior, but maybe you still want to keep it like tracking somewhere. And I think about like, you know, Lins and things like that, where it's like, well, I've got some things that I definitely should be fixing. Then I've got a bunch of other stuff that's like informing me that maybe I should take action on or not. But only I, the human can really know at the end of the day, right, if I, if I should prioritize that or not. And so that's how I kind of think about like, if I'm gonna try catch and then log. Yeah, you should probably collect that data. It's probably less important than like the, these other concerns, like, like an actual unhandled exception. But you do, you do want to know that they're happening and whatnot. And so, I dunno, Sentry has not had a strong opinion on this historically. We're just like, send us whatever you want to capture in this regard, and you can pay for it, that's fine. It's like usage based, you know? we're starting to think a lot more about what should that look like if we, if we go back to like, what's the, what's the opinion we have for how you should use the product or how you should solve these kinds of software problems. [00:17:46] Jeremy: So you gave the example of detecting n plus one queries is, is that like being aware of the framework or the ORM the person is using and that's how you're determining this? Or is it at more of a lower level than that? [00:18:03] David: it is, yeah. It's at the framework level. So this is actually where Open Telemetry causes a lot of harm, uh, for us because we need to know what a database query is. Uh, we need to know like the structure of the query because we actually wanna parse it out in a lot of cases. Cause we actually need to identify if it's duplicate, right? And we need to know that it's a database query, not a random annotation that you've added. Um, and so what we do is within these traces, which is like if you, if you don't know what a trace is, it's basically just like, it's a tree, like a tree structure. So it's like A calls B, calls C, B also calls D and E and et cetera, right? And so you just, you know, it's a trace. Um, and so we actually just look at that trace data. We try to find these patterns, which is like, okay, B was a, a SQL query or something. And every single sibling of B is that same SQL query, but sort of removing certain parameters and stuff for the value. So we'll look at that data and we'll try to pull out anomalies. So m plus one is an example of like a fairly obvious anti pattern that everybody knows is bad and can be optimized. Uh, but there's a lot of other that are a little bit more subjective. I'll give you an example. If you execute three SQL statements back to back, one could argue that you could just batch those SQL statements together. I would argue most of the time it doesn't matter and I don't need to do that. And also it's not guaranteed that that is better. So it becomes much more like, well, in my particular situation this is valuable, but in this other situation it might not be. And that's where I go back to like, it's almost like a linter, you know? But we're trying to infer all of that from the data stream. So, so Sentry's kind of, we're kind of a backwards product company. So we build our product from a technology vision, not from customers want this, or we have this great product vision or anything like that. And so in our case, the technology vision is like, there's a lot of application data that comes in, a lot of telemetry, right? Errors, traces. We have a bunch of other streams now. within that telemetry there is like signal. And so one, it's all structured data so we know what it is so we can actually interpret it. And then we can identify that signal that might be a problem. And that signal in our case is often going to translate to like this issue concept. And then the goal is like, well, can we identify these problems for people and surface them versus the choose your own adventure model, which is like, we'll just capture everything and feed it to the user and they can figure out what matters. Because again, a web service is a web service. A database is a database. They're all the same problems for everybody. All you know, it's just, and so that's kind of the model we've built and are continuing to evolve on and, and so far works pretty well to, to curate a lot of these workflows. Want to infer everything, but there are challenges [00:20:26] Jeremy: You talked a little bit about how people will sometimes use tracing. And in cases like that, they may need some kind of session ID to track. Somebody making a call to a service and that talks to a database and that talks to other services. And you, inside of your application, you have to instrument some way of tracking. This all came from this one request. Is that something that Sentry can infer or is there something that the developer has to put into play so that you can track that sort of thing? [00:21:01] David: Yeah, so it's, it's like a bit of both. And i would say our goal is that we can infer everything. The reality is there is so much complexity and there's too much of a, like, too many technologies in the world. Like I was complaining about this the other day, like, the classic example on web service is if we have a middleware hook, We kind of know request response, usually that's how middleware would work, right? And so we can infer a lot from there. Like basically we can infer the boundaries, which is a really big deal. Okay. That's one thing is boundaries is a problem. What we, we describe that as a transaction. So like when the request starts. When the request ends, right? That's a very important boundary for everybody to understand because when I'm working on the api, I care about the API boundary. I actually don't care about what the database is doing at its low level or what the JavaScript application might be doing above it. I want my boundary. So that's one that we kind of can do. But it's hard in a lot of situations because of the way frameworks and technology has been designed, but at least traditional stuff like a, a traditional web stack, it works like a Rails app or a DDjango app or PHP app kind of thing, right? And then within that it becomes, well, how do you actually build a trace versus just have a bunch of arbitrary labels? And so we have a bunch of complicated tech within each language that tries to establish that tree. and then we annotate a lot of things along the way. And so we will either leverage Open Telemetry, which is an open format spec that ideally has very high quality data. Ideally, not realistically, but ideally it has high quality data. Every library author implements it great, everybody's happy. We don't have to do anything ever again. The reality is that data is like all over the map because there's not like strict requirements for what, how the data should be labeled and stuff. And not everything even has that data. Like not everything's instrumented with open telemetry. So we also have a bunch of stuff that, unrelated to using that we'll say, okay, we know what this library is, we're gonna try to infer some characteristics from this library, or we know what maybe like the DDjango template engine is. So we're gonna try to infer like when the template renders so you can capture that block of information. it is a very imperfect science and I would tell you like it's not, even though like Open Telemetry is a very fun topic for people. It is not necessarily good, like it's not in a good state. Could will it ever be good? I don't know in all honesty, but like the data quality is like all over the map and so that's honestly one of our biggest challenges to making this experience that, you know, tells you what's going on in your database so it tells you what's going on with the cash or things like this is like, I dunno, the cash might be called something completely random in one implementation and something totally different in another. And so it's a lot of like, like data normalization that you have to deal with. But for the most part, those libraries of things you don't control can and will be instrumented. Now the other interesting thing, which we'll see how this works out, so, so one thing Sentry tries to do there, we have all these layers of telemetry, so we have errors and traces, right? Those are pretty high level concepts. We also have profiling data, which is very, very, very, very low level. So it's usually only if you have like disc. I like. It's where is all the CPU time being spent in my application? Mostly not waiting. Like waiting's usually like a network call, right? But it's like, okay, I have a loop that's doing a lot of math, or I'm writing a bunch of stuff to disc and that's really slow. Like often those are not instrumented or it's like these black box areas of a performance. And so what we're trying to do with profiling data, instead of just showing you flame charts and stuff, is actually say, could we fill in these gaps in these traces? Like basically like, Hey, I've got a long period of time where the app's doing something. You know, here's an API call, here's the database stuff. But then there's this block, okay, what's that function or something? Can we pull that out of the profiling data? And so in that case, again, that's just automatic because the profile actually knows everything about the application and know it. It has full access to the function and the stack and everything, right? And so the dream is that you would just always have everything filled in the, the customer never has to do anything with one minor asterisk. And the asterisk is what I would call like business context. So a good example would be, You might wanna associate requests with a specific customer or something like that. Like you might wanna say, well it's uh, I don't know, Goldman Sachs or one of these big companies or something. So you can know like, well when Goldman Sachs is having performance issues or whatever it is, oh maybe I should focus on them cuz maybe they pay you a lot of money or something. Right. Sentry would never know that at the end of the day. So we also have these like kind of tagging contextual APIs that will say like, tell us some informations, maybe it's like customer, maybe it's something else that's relevant to your application. And we'll keep that data associated with the telemetry that's like present, you know, um, but the, at least the telemetry, like again, application's just worth the same, should be, there should be a day in the next few years that it's just all automatic. and again, the only challenge today is like, can it be high quality and automatic? And so that, that's like to be determined. [00:25:50] Jeremy: What you're kind of saying is the ideal is being able to look at this profiling information and be able to build a full picture of. a, a call from beginning to end, all the different things to talk to, but I guess what's the, what's the reality today? Like, what, what is Sentry able to determine, in the world we live in right now? [00:26:11] David: So we've done a lot of this like performance detection stuff already. So we actually can do a lot now. We put a lot of time into it and I, I will tell you, if you look at other tools trying to do tracing, their approach is much more abstract. It's like your traditional monitoring tool that's like, we're just gonna collect a lot of signals and maybe we'll find magic anomaly detection or something going on in it, which, you know, props, but that can figure that out. But, a lot of what we've done is like, okay, we kind of know what this data looks like. Let's go after this very like known quantity problem. Let's normalize the data. And let's make it happen like that's today. Um, the enrichment of profiles is new for us, but it, we actually can already do it. It's not perfect. Detection of blocking the UI thread in mobile apps [00:26:49] David: Um, and I think we're launching something in April or May, something around the, that timeframe where hopefully for the, the technologies we can instrument, we're actually able to surface that in a useful way. but as an example that, that concept that I was talking about, like with n plus one queries, the team built something using profiling data. and I think this, this might be for like a mobile app more so than anything where mobile apps have this problem of, it's, you've got a main thread and if you block that main thread, the app is basically frozen. You see this on desktop apps all the time. You, you very rarely see it on web apps anymore. But, but it's a really big problem when you have a web, uh, a mobile or desktop app because you don't want that like thing to be non-responsive. Right? And so one of the things they did was detect when you're doing like file io on the main thread, you know, right. When you're writing a disc, which is probably a slow thing or something like that, that's gonna block the whole thing. Because you should just do it on a separate thread. It's like an easy fix, potentially may not be a problem, but it could become a problem. Same thing as n plus one. But what's really interesting about it is what the team did is like they used the profiling data to detect it because we already know threads and everything in there, and then they actually recreated a stack trace out of that profiling data when it's surfaced. So it's actually like useful data with that. You could like that I or you as a developer might know how to take and actually be like, oh, this is where it happens at the source code. I can actually figure it out and go fix it myself. And to me, like as like I, I'm still very much in the weeds with software that is like one of the biggest gaps to most things. Is it just, it doesn't make it easy to consume or like take action on, right? Like if I've got a, a chart that says my error rate is high, what am I gonna do with that? I'm like, okay, what's breaking? That's immediately my next question. Right? Okay. This is the error. Where is that error happening at? Again, my next question, it, it's literally just root cause analysis, right? Um, and so that, that to me is very exciting. and I, I don't know that we're the first people to do that, I'm not sure. But like, if we can make that kind of data, that level of actionable and consumable, that's like a big deal for me because I will tell you is like I have 20 years of software experience. I still hate flame charts and like I struggle to use them. Like they're not a friendly visualization. They're almost like a, a hypothetically necessary evil. But I also think one where nobody said like, do we even need to use that? Do we need that to be like the way we operate? and so anyways, like I guess that's my long-winded way of saying like, I'm very excited for how we can leverage that data and change how it's used. [00:29:10] Jeremy: Yeah. So it sounds like in this example, both in the mobile app blocking the UI or the n plus one query is the Sentry, suppose, SDK or instrumentation that's hooked inside of your application. There are certain behaviors that it knows are, are not like ideal I guess, just based on. people's prior experience, like your own developers know that, hey, if you block the UI thread in this mobile application, then you're gonna have performance problems. And so that way, rather than just telling you, Hey, your app is slow, it can tell you your app is slow and it's because you're blocking the UI thread. Don't just aggregate metrics, the error tracker should have an opinion on what actual problems are [00:29:55] David: Exactly, and I, and I actually think, I don't know why so many people don't recognize this gap, because at the end of the day, like, I don't know, I don't need more people to tell me response times are bad or anything. I need you to have an opinion about what's good because. The only way it's like math education, right? Like, yeah, you learn the basics, but you're not expected to say, go to calc, but, and then like, do all the fundamentals. You're like, don't get a calculator and start simplifying the problem. Like, yeah, we're gonna teach you a few of these things so you understand it. We're gonna teach you how to use a calculator and then just use the calculator and then make it easier for everybody else. But we're also not teaching you how to build a calculator because who cares? Like, that's not the purpose of it. And so for me, this is like, we should be helping people sort of get to the finish line instead of making them run the entirety of the race over and over if they don't need to. I don't, I don't know if that's a good analogy, but that has been the biggest gap, I think, in so much of this software throughout the industry. And it's, it's, it's common everywhere. And there's no reason for that gap to exist these days. Like the technology's fine. And the technology's been fine for like 10 years. Like Sentry started in oh eight at this point. And I think there was only one other company I recall at the time that was doing anything that was even similar to like air monitoring and Sentry when we built it, we're just like, what if we just go deeper? What if we collect all this information that will help you debug the problem instead of just stopping it like a log aggregator or something kind of thing, so we can actually have an opinion about it. And I, I genuinely, it baffles me that more people do not think this way because it was not a hard problem at the time. It's certainly not hard these days, but there's still very, I mean, a lot more people do it now. They've seen Sentry successful and there's a lot of similar implementations, but it's, it's just amazes me. It's like, why don't you, why don't people try to make the data more actionable and more useful, the teams versus just collect more of it, you know? 40 people working on learning the common issues with languages and frameworks [00:31:41] Jeremy: it, it sounds like maybe the, the popularity of the stack the person is using or of the framework means that you're gonna have better insights, right? Like if somebody makes a, a Django application or a Rails application, there's all these lessons that your team has picked up in terms of, Hey, if you use the ORM this way, your application is gonna be slow. Whereas if somebody builds something totally homegrown, you won't know these patterns and you won't be able to like help as much basically. [00:32:18] David: Yeah. Yeah, that's exactly, and, and you might think that that is a challenge, but then you look at how many employees exist at like large tech companies and it's, it's not that big of a deal, like, , you might even think collecting all the information for each, like programming, runtime or framework is a challenge. We have like 40 people that work on that and it's totally fine. Like, and, and so I think actually all these scale just fine. Um, but you do have to understand like the domain, right? And so the counter version of this is if you look at say like browser applications, like very rich, uh, single page application type experiences. It's not really obvious like what the opinions are. Like, like if, if you, and this is like real, like if you go to Sentry, it's, it's kind of slow, like the app is kind of slow. Uh, we even make fun of ourselves for how slow it is cuz it's a lot of JavaScript and stuff. If you ask somebody internally, Hey, how would we make pick a page fast? They're gonna have no clue. Like, even if they have like infinite domain experience, they're gonna be like, I'm not entirely sure. Because there's a lot of like moving parts and it's not even clear what like, like good is right? Like we know n plus one is bad. So we can say not doing that is the better solution. And so if you have a JavaScript app, which is like where a lot of the slowness will come from is like the render times itself. Like how do you fix it? You, you can't actually build a product that tells you what to fix without knowing how to fix it, right? And so some of these newer and very fast moving targets are, are frankly very difficult for us. Um, and so that's one thing that I think is a challenge for the entire industry. And so, like, as an example, a lot of the browser folks have latched onto web vitals, which are just metrics that hopefully tell you something about the application, but they're not always actionable either. It'll be like, the idea with like web vitals is like, okay, time to interactive is an an important metric. It's like how long until the page loads that a user can do what they're probably there to do. Okay. Like abstractly, it makes sense to us, but like put into action. How do I optimize time to interactive? Don't block the page. That's one thing. I don't know. Defer assets, that's another thing. Okay. So you've gotta like, you've gotta build a technology that knows these assets could be deferred and aren't. Okay, which ones can be deferred? I don't know. Like, it, it, it's like such a deep rabbit hole. And then the problem is, six months from now, the tech will have completely changed, right? And it won't have like, necessarily solved some of these problems. It will just have changed and they're now a completely different shape of problem. But still the same fundamental like user experience is the same, you know? Um, and to me that's like the biggest challenge in the industry right now is that like dilemma of the browser at the end of the day. And so even from our end, we're like, okay, maybe we should step back, focus on servers again, focus on web services. Those are known quantities. We can do that really well. We can sort of change that to be better than it's been in the past and easier to consume with things like our n plus one detections. Um, and then take like a holistic, fresh look at browser and say, okay, now how would we solve this to make sure we can actually really latch onto the problems that like people have and, and we understand, right? And, you know, we'll see when we get there. I don't think any product does a great job these days for helping, uh, solve those problems. . But I think even without the, the products, like I said, like even our team would be like, fixing this is gonna take months because it's gonna take months just to figure out exactly where the, the common bottlenecks are and all these other things within an application. And so I, I guess what I mean to say with that is there's a lot of opportunity, I think with the moving landscape of technology, we can find a way to, whether it's standardized or Sentry, can find a way to make that data actionable want it something in between there. There are many ways to build things on the frontend with JavaScript which makes it harder to detect common problems compared to backend [00:35:52] Jeremy: So it sounds like what you're saying, With the, the back end, there's almost like a standard way of doing things or a way that a lot of people do it the same way. Whereas on the front end, even if you're looking at a React application, you could look at tenant react applications and they could all be doing state management a totally different way. They could be like the, the way that the application is structured could be totally different, and that makes it difficult for you to infer sort of these standard patterns on the front end side. [00:36:32] David: Yeah, that's definitely true. And it, it goes, it's even worse than that because well, one, there's just like the nature of JavaScript, which is asynchronous in the sense of like, it's a lot of callbacks and things like that. And so that already makes it hard to understand what's going on, uh, where things are happening. And then you have these abstractions like React, which are very good, but like they pull a lot of that away. And so, as an example of a common problem, you load the application, it has to do a lot of stuff to make the page render. You might call that hydration or whatever. Okay. And then there's a completely different state, which is going from, it's already hydrated. Page one, I, I've done an interaction or something. Or maybe I've navigated a page too, that's an entirely different, like, sort of performance problem. But that hydration time, that's like a known thing. That's kind of like time to interactive, right? But if the problem is in your framework, which a lot of it is like a lot of the problems today exist because of frameworks, not because of the technology's bad or the framework's bad, but just because it's abstracted and it's really hard to make it work in all these situations, it's complicated. And again, they have the same problem where it's like changing non sem. And so if the problem is the framework is somehow incorrectly re rendering the page as an example, and this came up recently, for some big technology stack, it's re rendering the page. That's a really bad problem for the, the customer because it's making the, it's probably actually causing a lot of CPU seconds. This is why like your Chrome browser tabs are using so much memory in cpu, right? How do you fix that? Can you even fix that? Do you just say, I don't know, blame the technology? Is that the solution? Maybe that is right, but how would we even blame the technology like that alone, just to identify why it's happening. and you need to know the why. Right? Like, that is such a hard problem these days. And, and personally, I think the only solution is if the industry sort of almost like standardizes on a way to like, on a belief of how this should be optimized and how it should be measured and monitored kind of thing. Because like how errors work is like a standardization effectively. It may not be like a formal like declaration of like, this is what an error is, but more or less they always have the same attributes because we've all kind of understood that. Like those are the valuable things, right? Okay. I've got a server rendered application that has client interaction, which is sort of the current generation of the technology. We need to standardize on what, like that web request, like response life cycle is, right? and what are the moving targets within there. And it just, to me, I, I honestly feel like a lot of what we use every day in technology is like beta. Right. And it's, I think it's one of the reasons why we're constantly always having to up, like upgrade and, and refactor and, and, and shift dependencies and things like that because it is not, it's very much a prototype, right? It's a moving target, which I personally do not think is great for the industry because like customers do not care. They do not care that you're using some technology that like needs a change every few months and things like that. now it has improved things to be fair. Like web applications are much more like interactive and responsive sometimes. Um, but it is a very hard problem I think for a lot of people in the world. [00:39:26] Jeremy: And, and when you refer to, to things feeling like beta, I suppose, are, are you referring to the frameworks people are using or the libraries they're using to support their front end development? I, I'm curious what you're, you're thinking there. [00:39:41] David: Um, I think it's everything. Even like the browser APIs are constantly shifting. It's, that's gotten a little bit better. But even the idea like type script and stuff, it's just like we're running like basically compilers to make all this code work. And, and so the, even that they're constantly adding features just because they can, which means behaviors are constantly changing. But like, if you look at a real world example, like React is like the, the most dominant technology. It's very well designed for managing the dom. It's basically just a rendering engine at the end of the day. It's like it's managed to process updates to the dom. Okay. Makes sense. But we've all learned that these massive single page applications where you build all your application logic and loaded into a bundle is a problem. Like, like, I don't know how big Sentry's bundle is, but it's multiple megs in size and it takes a little while for like a, even on fast fiber here in the Bay Area, it takes a, you know, several seconds for the UI to load. And that's not ideal. Like, it's like at some point half of us became okay with this. So we're like, okay, what we need to do is go back, literally just go back 10 years and we need to render it on the server. And then we need some stuff that makes interactions, you know, highly responsive in the UI or dynamic content in the ui, you know, bring, it's like bringing back jQuery or something. And so we're kind of going full circle, but that is actually like very complicated because the way people are trying to do is like, okay, we wanna, we wanna have the rendering engine operate the same on the server and is on as on the client, right? So it's like we just write one, path of code that basically it's like a template engine to some degree, right? And okay, that makes sense. Like we can all get behind that kind of model. But that is actually really hard to make work with a lot of people's software and, and I think the challenge and framers have adopted it, right? So they've taken this, so for example, it's like, uh, react server components, which is basically just like, can we render it on the server and then also keep that same interaction in the ui. But the problem is like frameworks take that, they abstract it and so it's another layer of complexity on something that is already enormously complex. And then they add their own flavor onto it, like their own opinions for maybe what the world way the world is going. And I will say like personally, I find those. Those flavors to be very hard to adapt to like things that are tried and true or importantly in this context, things that we know how to monitor and fix, right? And so I, I don't know what, what the be all end all is, but my thesis on this is you need to treat the UI like a template engine, and that's it. Remove all like complexity behind it. And so if you think about that, the term I've labeled it as, which I did not come up with, I saw this from somebody at some point, is like, it's like your front end as a service. Like you need to take that application that renders on the server and the front end, and it's just an entirely different application, which is annoying. and it just calls your APIs and that's how it gets the data it needs. So you're literally just treating it as if it's like a single page application that can't connect to your database. But the frameworks have not quite done that. And they're like, no, no, no. We'll connect to the database and we'll do all this stuff, but then it doesn't work because you've got, like, it works this way on the back end and this way on the front end anyways. Again, long winded way of saying like, it's very complicated. I don't think the technology can solve it today. I think the technology has to change before these problems can actually genuinely become solvable. And that's why I think the whole thing is like a beta, it's like, it's very much like a moving target that we're eventually we'll get there and it's definitely had value, but I don't know that, um, responsiveness for low latency connections is where the value has been created. You know, for like folks with bad internet and say remote Africa or something, like I'm sure the internet is not a very fun place for them to use these days. Some frontend code runs on the server and some in the browser which creates challenges [00:43:05] Jeremy: I guess one of the things you mentioned is there's this, almost like this split where you have the application running on the server. It has its own set of rules because it, like you said, has access to the database and it can do things that you can't do in the browser, and then you have to sort of run the same application in the browser, but it's not quite the same application because it doesn't have access to the same things in the browser. So you have this weird disconnect, I suppose. [00:43:35] David: Yeah. Yeah. And, and, and then the challenges is like a developer that's actually complicated for you from the experience point of view, cuz you have to know somehow, okay, these things are ta, these are actually running on the server and only on the server. And like, so I think the two biggest technologies that try to do this, um, or at least do it well enough, or the two that I've used, there might be some others, um, are NextJS and remix and they have very different takes on how to do this. But, remix is the one I use most recently. So I, I'll comment on that. But like, there's a, a way that you kind of say, well, this only runs on, I think the client as an example. And that helps you a little bit. You're like, okay, this is only gonna render on the client. I can, I actually can think about that and reason about that. But then there's this thing like, okay, sometimes this runs on the server, only this part runs on the server. And it's, it just becomes like the mental capacity to figure out what's going on and debug it is like so difficult. And that database problem is like the, the normal problem, right? Like of like, I can only query the database on the server because I need secure credentials or something. Okay. I understand that as a developer, but I don't understand how to make sure the application is doing what I expect it to do and how to fix it if something goes wrong. And that, that's why I think. , I'm a, I'm a believer in constraints. The only way you make progress is you simplify problems. Like you just give up on solving the complicated thing and you make the problem simpler. Right? And so for me, that's why I'm like, just take the database outta the equation. We can create APIs from the client, from the server, same security levels. Okay? Make it so it can only do that and it has to be run as almost like a UI only thing. Now that creates complexity cuz you have to run this other service, right? And, and like I personally do not wanna have to spin up a bunch of containers just to write like a simple like web application. but again, I, I think the problem has not been simplified yet for a lot of folks. Like React did this to be fair, um, it made it a lot easier to, to build UI that was responsive and, and just updated values when they changed, you know, which was a big deal for a long period of time. But I feel like everything after has not quite reached that that area, whereas it's simple and even react is hard to debug when it doesn't do what you want it to do. So I don't know, there, there's so gaps I guess is what i would say. And. Hopefully, hopefully, you know, in the next five years we'll kind of see this come to completion because it does feel like it's, it's getting closer to that compromise. You know, where like we used to have pure server rendered apps with some weird janky JavaScript on top. Now we've got this bridge of really complicated, you know, JavaScript on top, and the server apps are also complicated and it's just, it's a nightmare. And then this newer generation of these frameworks that work for some types of technology, but not all. And, and we're kind of almost coming full circle to like server rendered, you know, everything. But with like allowing the same level of interactions that we've been desiring, I guess, on the web. So, and I, fingers crossed this gets better, but right now I do not see like a clear like, oh, it's definitely there. I can see it coming. I'm like, well, we're kind of making progress. I don't love being the beta tester of the whole thing, but we're kind of getting there. And so, you know, we'll see. There are multiple ways to write mobile apps as well (flutter, react native, web views) [00:46:36] Jeremy: I guess you, you've been saying this whole shifting landscape of how Front End works has made it difficult for Sentry to provide like automatic instrumentation and things like that for, for mobile apps. Is that a different story? Like is it pretty standardized in terms of how do you instrument an Android app or an iOS app. [00:46:58] David: Sort of, but also, no, like, a good example here is like early days mobile, it's a native application. You ship a binary known quantity, right? Or maybe you embedded a web browser, but like, that was like a very different thing. Okay. And then they did things where like, okay, more of it's like embedded web browser type stuff, or dynamically render content. So that's now a moving target. the current version of that, which I'm not a mobile dev so like people have strong opinions on both sides of this fence, but it's like, okay, do you use like a, a hybrid framework which allows you to build. Say, uh, react native, which is like arou you to sort of write a JavaScript ish thing and it runs on both Android and mobile, but not really well on either. Um, or do you write a native, native app, which is like a known quantity, but then you may maintain like two code bases, have two degrees of expertise and stuff. Flutters the same thing. so there's still that version of complexity that goes on within it. And I, I think people care less about mobile cuz it impacts people less. Like, you know, there's that whole generation of like, oh, mobile's the future, everything's gonna be mobile, let's not become true. Uh, mobile's very important, but like we have desktops still. We use web software all the time, half the time on mobile. We're just using the web software at the end of the day, so at least we know that's a thing. And I think, so I think that investment in mobile has died down some. Um, but some companies like mobile is like their main experience or one of their driving experience is like a, like a company like DoorDash, mobile is as important as web, if not more, right? Because of like the types of customers. Spotify probably same thing, but I don't know, Sentry. We don't need a mobile app, who cares? It's irrelevant to the problem space, right? And so I, I think it's just not quite taken on. And so mobile is still like this secondary citizen at a lot of companies, and I think the evolution of it has been like complicated. And so I, I think a lot of the problems are known, but maybe people care less or there's just less customers. And so the weight doesn't, like, the weight is wildly different. Like JavaScript's probably like a hundred times the size from an investment point of view for everyone in the world than say mobile applications are, is how I would think about it. And so whether mobile is or isn't solved is almost irrelevant to the, the, the like general problem at hand. and I think at the very least, like mobile applications, there's like, there's like a tool chain where you can debug a lot of stuff that works fairly well and hasn't changed over the years, whereas like the web you have like browser tools, but that's about it. So. Mobile apps can have large binaries or pull in lots of dependencies at runtime [00:49:16] Jeremy: So I guess with mobile. Um, I was initially thinking of native apps, but you're, you're bringing up that there's actually people who would make a native app that's just a web view for a webpage, or there's React native or there's flutters, so there's actually, it really isn't standard how to make a mobile app. [00:49:36] David: Yeah. And even within those, it comes back to like, okay, is it now the same problem where we're loading in a bunch of JavaScript or downloading a bunch of JavaScript and content remotely and stuff? And like, you'll see this when you install a mobile app, and sometimes the binaries are huge, right? Sometimes they're really small, and then you load it up and it's downloading like several gigs of data and stuff, right? And those are completely different patterns. And even within those like subsets, I'm sure the implementations are wildly different, right? And so, you know, I, that may not be the same as like the runtime kind of changing, but I remember there was this, uh, this must be a decade ago. I, I used, I still am a gamer, but. Um, early in my career I worked a lot with like games like World of Warcraft and stuff, and I remember when games started launching progressive loading where it's like you could download a small chunk of the game and actually start playing and maybe the textures were lower, uh, like resolution and everything was lower fidelity and, and you could only go so far until the game fully installed. But like, imagine like if you're like focused on performance or something like that, measuring it there is completely different than measuring it once, say everything's installed, you know? And so I think those often become very complex use cases. And I think that used to be like an extreme edge case that was like such a, a hyper-specific optimization for like what The Warcraft, which is like one of the biggest games of all time that it made sense, you know, okay, whatever. They can build their own custom tooling and figure it out from there. And now we've taken that degree of complexity and tried to apply it to everything in the world. And it's like uhoh, like nobody has the teams or the, the, the talent or the, the experience to necessarily debug a lot of these complicated problems just like Sentry like. You know, we're not dealing with React internals. If something's wrong in the React internals, it's like somebody might be able to figure it out, but it's gonna take us so much time to figure out what's going on, versus, oh, we're rendering some html. Cool. We understand how it works. It's, it's a known, known problem. We can debug it. Like there's nothing to even debug most of the time. Right. And so, I, I don't know, I think the industry has to get to a place where you can reason about the software, where you have the calculator, right. And you don't have to figure out how the calculator works. You just can trust that it's gonna work for you. How Sentry's stack has become more complex over time [00:51:35] Jeremy: so kind of. Shifting over a little bit to Sentry's internals. You, you said that Sentry started in, was it 2008 you said? [00:51:47] David: Uh, the open source project was in 2008. Yeah. [00:51:50] Jeremy: The stack that's used in Sentry has evolved. Like I remembered that there was a period where I think you could run it with a pretty minimal stack, like I think it may have even supported SQLite. [00:52:02] David: Yeah. [00:52:03] Jeremy: And so it was something that people could run pretty easily on their own. But things have, have obviously changed a lot. And so I, I wonder if you could speak to sort of the evolution of that process. Like when do you decide like, Hey, this thing that I built in 2008, Is, you know, not gonna cut it. And I really need to re-architect what this system is. [00:52:25] David: Yeah, so I don't know if that's actually the reality of why things have changed, that it's like, oh, this doesn't work anymore. We've definitely introduced complexity in the sense of like, probably the biggest shift for Sentry was like, it used to be everything, and it was a SQL database, and everything was kind of optional. I think half that was maintainable because it was mostly built by. And so I could maintain like an architectural vision that kept it minimal. I had the experience to figure it out and duct tape the right things. Um, so that was one thing. And I think eventually, you know, that doesn't scale as you're trying to do more and build more into the product. So there's some complexity there. but for the most part you can, it can still

In this episode, David Cramer, co-founder and CTO of Sentry, joins host Jeremy Jung for a conversation about error tracking. The discussion starts with treating performance problems as errors, why you might not need logs, and how most applications share the same problems. From there they consider other topics including capturing information by hooking into runtimes and frameworks, issues with the quality of Open Telemetry data, how front-end applications are constantly changing and why that makes them hard to instrument. Finally, they discuss how Sentry's architecture has evolved, and why they switched from a permissive license to the Business Source License.

david cramer speaks on why he believes in open source businesses, and why specifically you should use BSL and not the other stuff.https://www.se-radio.net/2023/05/se-radio-563-david-cramer-on-error-tracking/ 1hr in

In the 600th episode of Syntax, Wes and Scott talk about the big announcement about Syntax's future, exciting new opportunities coming for the show, and more! Show Notes 00:11 Scott's big announcement 00:58 Our big announcement 01:39 Guest introduction David Cramer (@zeeg) Application Performance Monitoring & Error Tracking Software | Sentry Sentry (@getsentry) 02:28 Background on how we got here 05:53 What does this mean for the podcast? 08:58 Why did Sentry want to partner with Syntax? 15:39 What does this mean for more + better Syntax? 18:56 We want to hear from you 23:17 Clarifications 23:42 What's David Cramer's background? 31:44 Helping spread the Syntax vibe World Famous HOTBOYS 35:40 Silly questions 37:52 What's the ROI on Wes' TikToks? 38:37 Is Syntax going to become purple? 40:46 The new Syntax website 47:16 Giveaway coming! 51:32 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× David Cramer: Vitest | A blazing fast unit test framework powered by Vite Scott: Valley Heat Podcast - A Podcast About The Neighborhood Wes: CCS - The Premier Online Skate Shop for Skateboards & Skate Gear Shameless Plugs Scott: LevelUp Tutorials Wes: Wes Bos Tutorials Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets

Freedom House called on Georgian authorities to revise the draft law on detecting "foreign agents," David Cramer criticized the draft law, a women's march was held in Tbilisi, special forces used water cannons and tear gas against the demonstrators, President Zurabishvili appealed to ambassadors abroad to protect Georgia's European future, and much more!Thanks for tuning in!Let us know what you think and what we can improve on by emailing us at georgia@rorshok.com or follow us on Instagram @Rorshok_G or Twitter @RorshokGeorgia or Mastodon @georgia@rorshok.socialLike what you hear? Subscribe, share, and tell your buds.

This week on Unpacked we are chatting with guest David Cramer, Founder and Managing Director, Sparrow Downhole Tools LTD. We talk with David about his experiences as an enneagram type 4, how he learned his type, and stories it shows up in his past and present. Plus the gifts and burdens he carries and practices for growth.Everyday Enneagram is co-hosted by Tara Linsley and Evan Dewald unpacking life as each enneagram type with regular, growing people like you and me.  Evan and Tara go through all 9 types of the personality tool that reveals motive and helps to shed light on the truth present in our lives.The goal is to talk about the path to discovering your core number AND develop compassion for yourself and the other 8 types. As all content under Unpacked we aim to have conversations that grow in self awareness and help our audience improve relationships at work and home. Using the lens of the enneagram and story telling we unpack the messiness of life, because we believe that's where we find growth.Everyday Enneagram is brought to you by Recess Creek Coaching and Magna Engineering ServicesRecess Creek Coaching with Evan DewaldHelping you to look at your story through the enneagram and encouraging you towards writing a new story,  greater health and relationships in all areas of your life. Book a free 15 minute discovery call today at unpackedpod.ca/coaching    Magna Engineering Services is a civil engineering consulting firm dedicated to delivering innovative, cost-effective infrastructure solutions for municipalities and communities throughout Western Canada. Learn more about Magna Engineering Services at magnaengineering.ca Support the showUnpacked is a podcast exploring life as messy people. It's conversations with counsellors, leaders, and storytellers discussing the experiences of being human. We talk about the strength that comes from big messy failures and vulnerable moments so we can learn to live more authentically. Subscribe and leave us a review!Instagram:@theunpackedpodFacebook: @theunpackedpodunpackedpod.caSupport the show*music by Bensound

Sentry@zeeg on TwitterCodecovSupport the ShowThis podcast does not have any ads or sponsors. To support the show, please consider purchasing a book, signing up for Button, or reading the Django News newsletter.

Welcome to episode sixty-eight of New Creation Conversations. I'm excited to get to share with you today a second conversation with Dr. Myles Werntz. Myles is the Director of Baptist Studies and Associate Professor of Theology at Abilene Christian University, where he directs the Baptist Studies Center in the Graduate School of Theology. He is the author and editor of several books in theology and ethics and writes broadly on the Christian ethics of war and peace, immigration, ecclesiology, and discipleship. We had a conversation a few months ago with is friend David Cramer about their co-authored book A Field Guide to Christian Nonviolence. In this conversation Myles and I discuss his brand-new book, From Isolation to Community: A Renewed Vision for Christian Life Together – published by Baker Academic.Like many others, the works of Dietrich Bonhoeffer have been deeply influential. Bonhoeffer's Letters, Ethics, and The Cost of Discipleship have been important formative works in my journey. However, perhaps the work that I have returned to repeatedly is his little tract Life Together. In his new book, Myles takes Bonhoeffer's work and reflects on the theme of isolation as one of the key problems of our age. Profoundly, Myles reflects on how the church, even while meeting together lives into and exacerbates the problem of isolation. He even points to the ease with which most congregations were able to navigate the separation created by the pandemic as a sign of the way isolation has taken hold of our imaginations. Like Bonhoeffer himself, Myles goes beyond analysis and offers theological depth and describes the practices that might heal our isolation. It is a thoughtful book that resonated deeply with me, and I know you'll find this conversation helpful as well.

Ryan Yazel and David Cramer - Last week we asked the question, "What difference does 'Everyone an Icon' make?" This week we learn through a practical interview about the Christian tradition of nonviolence through with David Cramer, the Pastor of Keller Park Church in South Bend and co-author of "A Field Guide to Christian Nonviolence: Key Thinkers, Activists, and Movements for the Gospel of Peace". If you're a part of the growing digital SBCC community, we'd love to hear from you! Drop us a note letting us know how you found us and what keeps you listening at: info@southbendcitychurch.com. You can also support the ongoing work of SBCC by giving at: southbendcitychurch.com/give. Just select the “podcast” option from the drop-down menu to let us know how you're participating in the life of SBCC. South Bend City Church is a 501(c)3 tax-exempt organization. All donations are tax-deductible.

David Cramer is the Co-Founder & CTO of Sentry, the open source error tracking and performance monitoring unicorn company used by over 3.5M developers and 85K organizations. The company's most popular open source project, also called sentry, has over 31K stars and lets users monitor and fix crashes in real-time. The server is in Python, but it contains a full API for sending events from any language, in any app. Sentry has raised $217M from investors including Accel, NEA, and Bond. In this episode, we talk with David about starting Sentry before open source business models were mainstream, how he's adapted as a leader holding the CEO and CTO seats at different points in time, and his candid advice to open source founders (particularly first-time founders) starting out today.

Joel takes over the podcast for another wide-ranging "reviewer round-up" with two excellent first-time guests. They talk a lot about books that intersect with the conversation about race in America, and of course, list off the titles they are currently reading.Joshua E. Livingston is a writer and community developer currently residing in Indianapolis. He is the director of Cultivating Communities and the author of Sunrays on the Beachhead of the New Creation (Wipf & Stock, 2021).Myles Werntz is associate professor of theology and director of Baptist studies at Abilene Christian University in Abilene, Texas. He is the author or editor of several books, including Bodies of Peace, A Field Guide to Christian Nonviolence, and the brand new book, From Isolation to Community: A Renewed Vision for Christian Life Together (Baker Academic).Books and Writing Mentioned in this Episode:If you'd like to order any of the following books, we encourage you to do so from Hearts and Minds Books(An independent bookstore in Dallastown, PA, run by Byron and Beth Borger) Asian Americans and the Spirit of Racial Capitalism by Jonathan TranJosh's written review of Asian Americans and the Spirit of Racial CapitalismSunrays on the Beachhead of the New Creation by Josh LivingstonBodies of Peace: Ecclesiology, Nonviolence & Witness by Myles WerntzA Field Guide to Christian Nonviolence: Key Thinkers, Activists & Movements for the Gospel of Peace by David Cramer & Myles WerntzFrom Isolation to Community: A Renewed Vision for Christian Life Together by Myles WerntzThe Loneliest Americans by Jay Caspian KangMinor Feelings: An Asian American Reckoning by Cathy Park HongHow to Be Normal: Essays by Phil ChristmanMyles' written review of How to Be NormalMidwest Futures by Phil ChristmanBreaking Ground: Charting Our Future in a Pandemic Year by Plough/CommentRacecraft: The Soul of Inequality in American Life by Barbara Fields & Karen FieldsHeathen: Religion and Race in American History by Kathryn Gin LumShared Wisdom: Use of the Self in Pastoral Care and Counseling by Pamela Cooper-WhiteThe Psychology of Christian Nationalism: Why People are Drawn in and How to Talk Across the Divide by Pamela Cooper-WhiteThat We May Be One: Practicing Unity in a Divided Church by Gary B. AgeeHumbler Faith, Bigger God: Finding a Story to Live By by Samuel WellsThe Internet is not What You Think it is: A History, a Philosophy, a Warning by Justin E. H. SmithLife Together: The Classic Exploration of Christian Community by Dietrich BonhoefferTools for Conviviality by Ivan IllichH20 & the Waters of Forgetfulness by Ivan IllichDeschooling Society by Ivan IllichConfessions by Augustine (Translated by Sarah Ruden)Paul Among the People: The Apostle Reinterpreted and Reimagined in His Own Time by Sarah RudenSimone Weil: An AnthologyLeisure: The Basis of Culture by Josef PieperIndigenous Theology and the Western Worldview by Randy WoodleyLisey's Story by Stephen King

​​"There's some things on a grander scale, and there's some very small things that we can do on a daily basis to be allies that help people come to work in the morning and do their best work." In this episode of Pause for Payments, David Cramer of Visa speaks to our very own Founder & CEO, Kristy Duncan, about the importance of allyship in the workplace. About Pause for Payments Pause for Payments is a weekly podcast produced by Women in Payments, where in each episode, we sit down with an inspiring woman leading the way in the payments world and discuss industry and career-related topics, and share personal success stories to inspire and empower the next generation of women leaders. On behalf of International Women's Day, we are dedicating the month of March to honor and celebrate women's achievements while taking a closer look at topics surrounding this year's theme #BreaktheBias. To learn more, visit us at www.womeninpayments.org You can gain access to our global member portal, where you'll find the latest industry trends, exciting career opportunities, and so much more by becoming a member: https://www.womeninpayments.org/membership Connect with us: Twitter: https://twitter.com/WomeninPayments OR @WomeninPayments LinkedIn: www.linkedin.com/company/women-in-payments/

As Russian tanks and troops invade our peaceful, democratic ally Ukraine, the conversation about the Christian response to war and violence moves from the theoretical to the real and urgent. David Cramer and Myles Werntz join Doug Pagitt and Dan Deitrich to talk about their new book: A Fieldguide to Christian Nonviolence.   Doug Pagitt is the Executive Director and one of the founders of Vote Common Good. He is also a pastor, author, and social activist.  @pagitt   The Common Good Podcast is produced and edited by Daniel Deitrich. @danieldeitrich Our theme music is composed by Ben Grace. @bengracemusic   votecommongood.com votecommongood.com/podcast facebook.com/votecommongood twitter.com/votecommon  

Welcome to episode fifty-one of New Creation Conversations. In this first episode of this second year and second season of this podcast, I'm delighted to be joined in conversations by the co-authors of a wonderful new book on the complex history of Christian peacemaking Dr. David Cramer and Dr. Myles Werntz. David teaches at the Anabaptist Mennonite Biblical Seminary in Elkhart, Indiana, and he is the Managing Editor of the Institute of Mennonite Studies. David's scholarship focuses on Christian social ethics and the difference faith makes for how Christians live in contemporary society. Like me, David serves in both the academy and the local church. He is currently the teaching pastor at Keller Park Church – an urban congregation in South Bend, Indiana. His writing has appeared in scholarly journals and popular periodicals including Christian Century and Sojourners. Myles is Director of Baptist Studies and Associate Professor of Theology at Abilene Christian University, where he directs the Baptist Studies Center in the Graduate School of Theology. He is the author and editor of five books in theology and ethics and writes broadly on Christian ethics of war and peace, immigration, ecclesiology, and discipleship.David and Myles became friends while working on their PhDs together in theology and ethics at Baylor University. Their mutual interest in the practice and history of Christian nonviolence led to a twenty-year conversation and exploration of the complicated and varied approaches of Christians across the centuries to the call of disciples to make peace in the world in Jesus' name. That twenty-years of dialogue recently was released as a very helpful book, A Field Guide to Christian Nonviolence: Key Thinkers, Activists, and Movements for the Gospel of Peace – published by Baker Academic. In their book, Cramer and Werntz explore eight different streams of Christian nonviolence that not only take different approaches to peacemaking, but they also think about the call to take up the cross of Christ in different ways. In such a divided and violent age, I'm thankful for those who keep reminding us that it is the call of the disciple to participate in the new creation by making peace. However, I found David and Myles' Field Guide so helpful in showing how complicated obedience to this call can be, and how different followers of Jesus have found different ways to pursue this call with faith. I think you will find their work helpful and I'm excited to bring this conversation to you. 

Myles Werntz (PhD, Baylor University) is associate professor of theology and director of Baptist studies at Abilene Christian University in Abilene, Texas. He is the author or editor of several books, including Bodies of Peace and A Field Guide to Christian Nonviolence. David C. Cramer (PhD, Baylor University) is managing editor at the Institute of Mennonite Studies, sessional lecturer at Anabaptist Mennonite Biblical Seminary, and teaching pastor at Keller Park Church in South Bend, Indiana. David and Myles recently wrote a book called A Field Guide to Christian Nonviolence and this is the topic of our conversation. We discuss a biblical case for nonviolence and some pushbacks including the conquest of Canaan. We also discuss the killer at the door, policing, nonviolent revolts, and pulling up violent systems by the roots. Theology in the Raw Conference - Exiles in Babylon At the Theology in the Raw conference, we will be challenged to think like exiles about race, sexuality, gender, critical race theory, hell, transgender identities, climate change, creation care, American politics, and what it means to love your democratic or republican neighbor as yourself. Different views will be presented. No question is off limits. No political party will be praised. Everyone will be challenged to think. And Jesus will be upheld as supreme. Support Preston Support Preston by going to patreon.com Venmo: @Preston-Sprinkle-1 Connect with Preston Twitter | @PrestonSprinkle Instagram | @preston.sprinkle Youtube | Preston Sprinkle Check out Dr. Sprinkle's website prestonsprinkle.com Stay Up to Date with the Podcast Twitter | @RawTheology Instagram | @TheologyintheRaw If you enjoy the podcast, be sure to leave a review.

Aidan Fitzpatrick joins the show to talk about his career, founding the app studio Reincubate, and launching the excellent webcam app Camo. Links & Show Notes Aidan's Twitter (https://twitter.com/afit) Reincubate (https://reincubate.com) Camo (https://reincubate.com/camo/) Reincubate wins Queen's Award (https://reincubate.com/blog/queens-award/) Christian Selig (https://twitter.com/ChristianSelig) Chad Etzel (https://twitter.com/jazzychad) Astropad (https://astropad.com) David Cramer (https://twitter.com/zeeg) Panic (https://panic.com) Cabel Sasser (https://twitter.com/cabel) More Launched Website - launchedfm.com (https://launchedfm.com) Twitter - @LaunchedFM (https://twitter.com/launchedfm) Reddit - /r/LaunchedFM (https://www.reddit.com/r/LaunchedFM/)

David C. Cramer and Myles Werntz talk with Word&Way President Brian Kaylor about their new book A Field Guide to Christian Nonviolence: Key Thinkers, Activists, and Movements for the Gospel of Peace. Cramer is managing editor at the Institute of Mennonite Studies and teaching pastor at Keller Park Church in South Bend, Indiana. Werntz is associate professor of theology and director of the Baptist Studies Center at Abilene Christian University in Abilene, Texas. Note: Don't forget to check out our subscriber e-newsletter A Public Witness that helps you make sense of faith, culture, and politics.

Myles Werntz and David Cramer join host Marty Duren to discuss theories of Christian non-violence.

SPONSORED BY BOUNDLESS DRONE SERVICES. Most people have heard the name Wycliffe before, and that is because of the amazing work they've done in taking the Bible and translating it in thousands of dialects. David Cramer works for Wycliffe Associates, and is responsible for Discipleship in a huge region in the Pacific, working in such areas as New Guinea, where tribal dialects are many and varied.

Jordan, Eric, and second time guest David Cramer discuss the world of sports betting, and how it impacts the games, society, and even a Back to the Future II reference!

Listen now | David Cramer is the co-founder and CTO of Sentry, a monitoring platform helps every developer diagnose, fix, and optimize the performance of their applications. Before this, he worked at Dropbox and Disqus. Apple Podcasts | Spotify | Google Podcasts Get on the email list at www.softwareatscale.dev

Co-Founder and CTO of Sentry, David Cramer joins Ben Rometsch on this episode to talk about his journey from a side project of 70 lines of open source code to the most widely adopted open source crash reporting platform in the world.

In my 2021 web development predictions, I identified 2 key trends heading into this year: serverless expanding into a more full-featured platform (for example, stateful apps becoming a reality on serverless), and the continued growth of JavaScript (and especially React). Jamstack is another growth area, although that's at a much earlier stage. To discuss these and other frontend trends, I spoke to David Cramer, co-founder, and CTO of Sentry, an application monitoring platform. You can hear the full discussion on The New Stack Makers podcast, but in this article, I'll review the main talking points.

David's testimony is a breathtaking journey that includes a terminal diagnosis, a miracle surgery, and a life given a second chance. David's heart for missions opened the way to serve with the internationally known Wycliffe Associates, a group involved in translating the Bible into local dialects around the world.

Jordan and Eric discuss their top 5 all time sports busts with special guest David Cramer. Some picks are easy and everyone knows, others are not...let the debate begin!

Hi, Spring fans! In this episode [Josh Long (@starbuxman)](http://twitter.com/starbuxman) talks about the wide world of webdevelopment with CSS, Figma, AdobeXD and more, and then talks to Sentry CTO [David Cramer (@zeeg)](https://twitter.com/zeeg) about easy error capture and analysis with Sentry and Spring. * Want to see the worldwide flurry of activity as errors make their way to Sentry? [Check this out](https://live.sentry.io)

Today we are talking to David Cramer, the CTO and Founder at Sentry. And we discuss his transition from CEO to CTO, how their software monitoring is helping to enable productivity, and the biggest lesson he’s learned as an entrepreneur and founder. All of this, right here, on the Modern CTO Podcast! Check them out at www.sentry.io !

David Cramer talks about creating Sentry as an open-source side project, maintaining it while working full-time at Dropbox, and ultimately growing it into one of today's leading application error monitoring tools. We chat about the emergence of new computing platforms, his thoughts on what's truly new and what's just marketing-speak for old ideas, and how he sees the landscape of observability and monitoring tools evolving in the future.Notes and transcript: https://about.sourcegraph.com/podcast/david-cramer

David Cramer joined the show to talk about the recent license change of Sentry to the Business Source License from a BSD 3-clause license. We talk about the details that triggered this change, the specifics of the BSL license and its required parameters, the threat to commercial open source products like Sentry, his concerns for the “open core” model, and what the future of open source might look like in light of protections-oriented source-available licenses like the BSL becoming more common.

David Cramer joined the show to talk about the recent license change of Sentry to the Business Source License from a BSD 3-clause license. We talk about the details that triggered this change, the specifics of the BSL license and its required parameters, the threat to commercial open source products like Sentry, his concerns for the “open core” model, and what the future of open source might look like in light of protections-oriented source-available licenses like the BSL becoming more common.

Flute 360 | Episode 44: “Competition Repertoire Guides with Jake Fridkis” (57:22) In today’s episode, Heidi talks with Jake Fridkis who is the principal flutist with the Fort Worth Symphony Orchestra. We talk about specific repertoire requirements for NFA and TFS competitions that are approaching. Repertoire includes Telemann’s Fantasie in A Major, Büsser’s Prélude et Scherzo, and Coleman’s Danza de la Mariposa! Finally, Jake gives some general tips to successfully prepare for a flute competition.    Episode 44 – Main Points: 0:28 – William S. Haynes Co. Website 1:40 – Repertoire requirements for NFA & TFS competitions. See links below. 2:19 – General suggestions for competition preparation. 3:06 – “If I was looking at the piece...the first thing I’d be focused on is how can I get all of this stuff on the page into my performance?” – Jake 4:08 – “If you go into any flute competition trying to improve your flute playing, as your first goal, you can’t lose!” – Jake 5:17 – “You don’t have control over the outcome, so don’t try to control it.” – Jake 6:33 – Telemann’s Fantasie in A Major 6:52 – “For Telemann, you are the show!” – Jake   10:14 – Jasmine Choi, James Galway, Emmanuel Pahud, Jean-Pierre Rampal 10:21 – Amy Porter’s DVD of Telemann’s 12 Fantasias 10:41 – Bärenreiter’s Publication, urtext edition 11:17 – Bach’s Partita in A minor for solo flute – BWV 1013 13:20 – Quantz’s “On Playing the Flute” 13:23 – Robert Donington’s “A Performer’s Guide to Baroque Music” 14:23 – Jed Wentz, flutist, conductor, and teacher 15:39 – Nicholas McGegan, conductor 16:57 – Kim Pineda, flutist and musicologist 18:08 – Early music experts 18:31 – Finger vibrato 19:06 – Summary of the Telemann 19:14 – Traverso flute– experiment with this instrument! 20:20 – Büsser’s Prélude et Scherzo 21:09 – Jake talks about the Prélude! 23:12 – “Be flexible with your dynamics.” – Jake 24:30 – “French music is all about flow. If you listen to Ravel and Debussy it’s this amazing wash of colors and sounds.” – Jake 24:49 – Melody at the 6/4 time signature 25:17 – Debussy’s “Prélude à l’après-midi d’un faune” 26:22 – Ravel, composer 26:46 – Conservatoire de Paris 29:25 – “Those are real notes in real time.” – Heidi quoting Dr. Sarah McKoin 31:04 – Büsser’s Scherzo 32:58 – “Don’t be afraid to have fun; this is all happy, fun music!” – Jake 33:37 – Cadenza 35:04 – Film: Matrix (1999) 36:12 – “I practice fast things extremely slowly. It’s effective because I am working on my sound. Then, when I play fast, my air knows where to go.” – Jake 37:01 – NFA’s Professional Flute Choir Competition 38:34 – Valerie Coleman’s “Danza de la Mariposa” 39:10 – Valerie Coleman, flutist and composer 39:24 – “We can show our full range and what we can do with the flute.” – Jake 40:47 – Fanfare opening! 42:44 – Singing and playing as tone exercises. 44:53 – Extended Techniques: Flutter tonguing 46:54 – Butterfly House, Dallas, TX 48:14 – Listen to Valerie play! 48:30 – Listen to “butterfly” pieces for other instruments! 48:50 – Jake’s final competition suggestions. 49:32 – Eastern Music Festival’s Application 50:00 – David Cramer, flutist 53:31 – Jake’s YouTube Channel 54:40 – Jolivet’s Chant de Linos 55:08 – Conclusion 55:37 – Brahms’ Symphony No. 2 – upcoming FWSO concert! 55:48 – Pam Adams, FWSO flutist Episode 44 – Resources Mentioned: Jake’s YouTube Channel Jake’s Instagram Jake’s Twitter FWSO – Jake’s Bio NFA’s Professional Flute Choir Competition NFA’s Convention Performers Competition Texas Flute Society’s Myrna Brown Competition William S. Haynes Co. Flutes’ Instagram William S. Haynes Co. Flutes’ Twitter William S. Haynes Co. Flutes' Facebook Heidi Kay Begay's Website Episode 44 – Sponsors: Gold Level: William S. Haynes Co. Website Silver Level: Contact Heidi for more details! Bronze Level: J&K Productions’ Website

David Cramer dropped out of high school AND college, but that didn’t stop him. He ended up teaching himself programming and eventually landed his first job as the webmaster of a World of Warcraft community website. What a beginning… We talked through “the rough slog” period of Sentry and how David powered through to traction and enough profit for him and his partner to go full time, raise three rounds of funding, and take on New Relic.

David Cramer dropped out of high school AND college, but that didn’t stop him. He ended up teaching himself programming and eventually landed his first job as the webmaster of a World of Warcraft community website. What a beginning… We talked through “the rough slog” period of Sentry and how David powered through to traction and enough profit for him and his partner to go full time, raise three rounds of funding, and take on New Relic.

Here’s a bonus segment from episode #57 of Founders Talk with David Cramer, co-founder and CEO of Sentry. Check the feed for the full length episode (later today). We talked about sales in the full length episode, but this BONUS segment is a completely isolated conversation that’s not included in the full length episode — so don’t gloss over this thinking it’s just a teaser.

Here’s a bonus segment from episode #57 of Founders Talk with David Cramer, co-founder and CEO of Sentry. Check the feed for the full length episode (later today). We talked about sales in the full length episode, but this BONUS segment is a completely isolated conversation that’s not included in the full length episode — so don’t gloss over this thinking it’s just a teaser.

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the Views on Vue panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the Views on Vue panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the React Round Up panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI Loot Crate FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the React Round Up panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI Loot Crate FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI FreshBooks Loot Crate Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI FreshBooks Loot Crate Picks: Charles Socks as Swag David VS Code Kubernetes

Panel:  Charles Max Wood Ayssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the Adventures in Angular panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry  What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more!  Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Linode Angular Boot Camp FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel:  Charles Max Wood Ayssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the Adventures in Angular panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry  What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more!  Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Linode Angular Boot Camp FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel:  Charles Max Wood Ayssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the Adventures in Angular panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry  What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more!  Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Linode Angular Boot Camp FreshBooks Picks: Charles Socks as Swag David VS Code Kubernetes

Panel: Charles Max Wood Alyssa Nicholl Ward Bell Special Guests: David Cramer In this episode, the JavaScript Jabber panelists talk to David Cramer about error tracking and troubleshooting workflows. David is the founder and CEO of Sentry, and is a software engineer by trade. He started this project about a decade ago and it was created because he had customers telling him that things were broken and it was hard to help them fix it. They talk about what Sentry is, errors, workflow management, and more! In particular, we dive pretty deep on: David intro Founder and CEO of Sentry What is Sentry? Working with PHP De-bugger for production Focus on workflow Goal of Sentry Triaging the problem Workflow management Sentry started off as an open-source side project Instrumentation for JavaScript Ember, Angular, and npm Got their start in Python Logs Totally open-source Most compatible with run-time Can work with any language Deep contexts Determining the root cause And much, much more! Links: Sentry JavaScript Ember Angular npm Python Sentry’s GitHub @getsentry David’s GitHub David’s Website @zeeg Sponsors Kendo UI FreshBooks Loot Crate Picks: Charles Socks as Swag David VS Code Kubernetes

Ken and Dave talk with David Cramer of Sparrow Technology about the different types of mud pulsers.

Dave and Ken interview David Cramer of Sparrow Technology to get insight into the best practices for analyzing complex and elusive downhole failures.

The second half of our conversation with David Cramer of Sparrow Technology.

As developers we all have to deal with bugs sometimes, but we don't have to make our users deal with them too. Sentry is a project that automatically detects errors in your applications and surfaces the necessary information to help you fix them quickly. In this episode we interviewed David Cramer about the history of Sentry and how he has built a team around it to provide a hosted offering of the open source project. We covered how the Sentry project got started, how it scales, and how to run a company based on open source.

Bill Mensch, 6502 chip Bill Mensch is co-creator of the 6502 chip, the microprocessor that’s the heart of the Atari 8-bit computers, the Apple ][, Commodore 64, and many other classic computers.  This interview occurred August 6, 2015. Teaser quotes: “These guys at Motorola aren’t going to do the microprocessor that we need to do: that is a low-end microprocessor to complete with the Intel 4040 which sold for about $29.” “I had a bet with Rod Orgle, and Rod Orgle said the 6501 would outsell the 6502.” “I’m in empowerment technology. I want to empower people to do their idea. That’s what I did for Chuck [Peddle], that’s why he came to me.” “Now, you’d think that I was a big fan of Apple, and I’m not. The reason why I’m not is they killed off the Apple II to make room for the Macintosh.” “All of those old brands — Apple II, Commodore, Atari, and the old Nintendo — could all come back to life, with the right relationships. And we have the technology.” Links: Bill and Dianne Mensch Foundation: http://themenschfoundation.org Western Design Center: http://www.westerndesigncenter.com My interview with David Cramer, Western Design Center: http://ataripodcast.libsyn.com/antic-interview-29-david-cramer-western-design-center

David Cramer tells us how to catch and fix critical errors that can affect your bottom line. We also discuss the key differences between exceptions and bugs, and how to handle errors gracefully.

David Cramer - Western Design Center   David Cramer is the VP of Business Development at Western Design Center, the company that still, today, manufacturers and sells the 6502 chip, the CPU that's at the heart of the Atari 800, Apple ][, Commodore 64, and many other classic computers. In fact, the 6502 is used in many modern applications like pacemakers, and it's also available in development kits for hobbyists, as David explains.   This interview occurred on March 27, 2015.   LINKS   Western Design Center 65xx.com mouser   Jameco Electronics  

We talk with Dr. David Cramer and Dr. Myles Werntz about Christian nonviolence, which is not a settled position but rather a vibrant and living tradition. In their book A Field Guide to Christian Nonviolence: Key Thinkers, Activists, and Movements for the Gospel of Peace, they offer a concise introduction to diverse approaches to, proponents of, and resources for Christian nonviolence.Dr. David Cramer is managing editor at the Institute of Mennonite Studies, sessional lecturer at Anabaptist Mennonite Biblical Seminary, and a teaching pastor at Keller Park Church in South Bend, IN.Dr. Myles Werntz is associate professor of theology and director of Baptist studies at Abilene Christian University in Abilene, TX. He is the author or editor of several books, including Bodies of Peace.Connect with Gravity LeadershipLeave us a message or ask a question about this or any other episode and we'll answer it on a future episode.Join our online community for free to get a curated list of interesting and edifying links each week, plus all kinds of other goodies.Check out the Gravity Commons, a place to connect and learn with others in the Gravity community.Check out Gravity Leadership Academy, our 12-month training intensive for Christian leaders who want to bring lasting transformation to their culture.Are you interested in advertising on the Gravity Leadership Podcast? Contact Gino Curcuruto at gino@gravityleadership.com.Support this podcast at — https://redcircle.com/gravity-leadership-podcast/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy