Podcasts about ci cd

Topics covered in this episode: ty: An extremely fast Python type checker and LSP Python Supply Chain Security Made Easy typing_extensions MI6 chief: We'll be as fluent in Python as we are in Russian Extras Joke Watch on YouTube About the show Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Brian #1: ty: An extremely fast Python type checker and LSP Charlie Marsh announced the Beta release of ty on Dec 16 “designed as an alternative to tools like mypy, Pyright, and Pylance.” Extremely fast even from first run Successive runs are incremental, only rerunning necessary computations as a user edits a file or function. This allows live updates. Includes nice visual diagnostics much like color enhanced tracebacks Extensive configuration control Nice for if you want to gradually fix warnings from ty for a project Also released a nice VSCode (or Cursor) extension Check the docs. There are lots of features. Also a note about disabling the default language server (or disabling ty's language server) so you don't have 2 running Michael #2: Python Supply Chain Security Made Easy We know about supply chain security issues, but what can you do? Typosquatting (not great) Github/PyPI account take-overs (very bad) Enter pip-audit. Run it in two ways: Against your installed dependencies in current venv As a proper unit test (so when running pytest or CI/CD). Let others find out first, wait a week on all dependency updates: uv pip compile requirements.piptools --upgrade --output-file requirements.txt --exclude-newer "1 week" Follow up article: DevOps Python Supply Chain Security Create a dedicated Docker image for testing dependencies with pip-audit in isolation before installing them into your venv. Run pip-compile / uv lock --upgrade to generate the new lock file Test in a ephemeral pip-audit optimized Docker container Only then if things pass, uv pip install / uv sync Add a dedicated Docker image build step that fails the docker build step if a vulnerable package is found. Brian #3: typing_extensions Kind of a followup on the deprecation warning topic we were talking about in December. prioinv on Mastodon notified us that the project typing-extensions includes it as part of the backport set. The warnings.deprecated decorator is new to Python 3.13, but with typing-extensions, you can use it in previous versions. But typing_extesions is way cooler than just that. The module serves 2 purposes: Enable use of new type system features on older Python versions. Enable experimentation with type system features proposed in new PEPs before they are accepted and added to the typing module. So cool. There's a lot of features here. I'm hoping it allows someone to use the latest typing syntax across multiple Python versions. I'm “tentatively” excited. But I'm bracing for someone to tell me why it's not a silver bullet. Michael #4: MI6 chief: We'll be as fluent in Python as we are in Russian "Advances in artificial intelligence, biotechnology and quantum computing are not only revolutionizing economies but rewriting the reality of conflict, as they 'converge' to create science fiction-like tools,” said new MI6 chief Blaise Metreweli. She focused mainly on threats from Russia, the country is "testing us in the grey zone with tactics that are just below the threshold of war.” This demands what she called "mastery of technology" across the service, with officers required to become "as comfortable with lines of code as we are with human sources, as fluent in Python as we are in multiple other languages." Recruitment will target linguists, data scientists, engineers, and technologists alike. Extras Brian: Next chapter of Lean TDD being released today, Finding Waste in TDD Still going to attempt a Jan 31 deadline for first draft of book. That really doesn't seem like enough time, but I'm optimistic. SteamDeck is not helping me find time to write But I very much appreciate the gift from my fam Send me game suggestions on Mastodon or Bluesky. I'd love to hear what you all are playing. Michael: Astral has announced the Beta release of ty, which they say they are "ready to recommend to motivated users for production use." Blog post Release page Reuven Lerner has a video series on Pandas 3 Joke: Error Handling in the age of AI Play on the inversion of JavaScript the Good Parts

Introducing Rob Ruiz Meet Rob Ruiz, a seasoned Senior Full Stack Developer with nearly two decades of expertise in WordPress innovation and open-source magic. As the Lead Maintainer of WP Rig since 2020, Rob has been the driving force behind this groundbreaking open-source framework that empowers developers to craft high-performance, accessible, and progressively enhanced WordPress themes with ease. WP Rig isn’t just a starter theme—it’s a turbocharged toolkit that bundles modern build processes, linting, optimization, and testing to deliver lightning-fast, standards-compliant sites that shine on any device. Show Notes For more on Rob and WP Rig, check out these links: LinkedIn Profile: https://www.linkedin.com/in/robcruiz WP Rig Official Site: https://wprig.io GitHub Repository: https://github.com/wprig/wprig Latest Releases: https://github.com/wprig/wprig/releases WP Rig 3.1 Announcement: https://wprig.io/wp-rig-3-1/ Transcript: Topher DeRosia: Hey everybody. Welcome to Hallway Chats. I’m your host Topher DeRosia, and with me today I have- Rob Ruiz: Rob Ruiz. Topher: Rob. You and I have talked a couple of times, once recently, and I learned about a project you’re working on, but not a whole lot about you. Where do you live? What do you do for a living? Rob: Yeah, for sure. Good question. Although I’m originally from Orlando, Florida, I’ve been living in Omaha, Nebraska for a couple of decades now. So I’m pretty much a native. I know a lot of people around here and I’ve been fairly involved in various local communities over the years. I’m a web developer. Started off as a graphic designer kind of out of college, and then got interested in web stuff. And so as a graphic designer turned future web developer, I guess, I was very interested in content management systems because it made the creating and managing of websites very, very easy. My first couple of sites were Flash websites, sites with macro media Flash. Then once I found content management systems, I was like, “Wow, this is way easier than coding the whole thing from scratch with Flash.” And then all the other obvious benefits that come from that. So I originally started with Joomla, interestingly enough, and used Joomla for about two or three years, then found WordPress and never looked back. And so I’ve been using WordPress ever since. As the years have gone on, WordPress has enabled me to slowly transition from a more kind of web designer, I guess, to a very full-blown web developer and software engineer, and even software architect to some degree. So here we are many years later. Topher: There’s a big step from designer to developer. How did that go for you? I’m assuming you went to PHP. Although if you were doing Flash sites, you probably learned ActionScript. Rob: Yeah. Yeah. That was very convenient when I started learning JavaScript. It made it very easy to learn JavaScript faster because I already had a familiarity with ActionScript. So there’s a lot of similarities there. But yeah. Even before I started doing PHP, I started learning more HTML and CSS. I did do a couple of static websites between there that were just like no content management system at all. So I was able to kind of sharpen my sword there with the CSS and HTML, which wasn’t particularly hard. But yeah, definitely, the PHP… that was a big step was PHP because it’s a proper logical programming language. There was a lot there I needed to unpack, and so it took me a while. I had to stick to it and really rinse and repeat before I finally got my feet under me. Topher: I can imagine. All right. So then you work for yourself or you freelance or do you have a real job, as it were? Rob: Currently, I do have a real job. Currently, I’m working at a company called Bold Orange out of Minneapolis. They’re a web agency. But I kind of bounce around from a lot of different jobs. And then, yes, I do freelance on the side, and I also develop my own products as well for myself and my company. Topher: Cool. Bold Orange sounds familiar. Who owns that? Rob: To be honest, I don’t know who the owners are. It’s just a pretty big web agency out of Minneapolis. They are a big company. You could just look them up at boldorange.com. They work for some pretty big companies. Topher: Cool. All right. You and I talked last about WP Rig. Give me a little background on where that came from and how you got it. Rob: Yeah, for sure. Well, there was a period of time where I was working at a company called Proxy Bid that is in the auction industry, and they had a product or a service — I don’t know how you want to look at that —called Auction Services. That product is basically just building WordPress sites for auction companies. They tasked us with a way to kind of standardize those websites essentially. And what we realized is that picking a different theme for every single site made things difficult to manage and increase tech debt by a lot. So what we were tasked with was, okay, if we’re going to build our own theme that we’re just going to make highly dynamic so we can make it look different from site to site. So we want to build it, but we want to build it smart and we want to make it reusable and maintainable. So let’s find a good framework to build this on so that we can maintain coding standards and end up with as little tech debt as possible, essentially. That’s when I first discovered WP Rig. In my research, I came across it and others. We came across Roots Sage and some of the other big names, I guess. It was actually a team exercise. We all went out and looked for different ones and studied different ones and mine that I found was WP Rig. And I was extremely interested in that one over the other ones. Interestingly enough- Topher: Can you tell me why over the other ones? Rob: That’s a great question. Yeah. I really liked the design patterns. I really liked the focus on WordPress coding standards. So having a system built in that checked all the code against WordPress coding standards was cool. I loved the compiling transpiling, whatever, for CSS and JavaScript kind of built in. That sounded really, really interesting. The fact that there was PHP unit testing built into it. So there’s like a starter testing framework built in that’s easy to extend so that you can add additional unit tests as your theme grows. We really wanted to make sure… because we were very into CICD pipelines. So we wanted to make sure that as developers were adding or contributing to any themes that we built with this, that we could have automated tests run and automated builds run, and just automate as much as possible. So WP rig just seemed like something that gave us those capabilities right out of the box. So that was a big thing. And I loved the way that they did it. Roots Sage does something similar, but they use their blade templating engine built in there. We really wanted to stick to something that was a bit more standard WordPress so that there wasn’t like a large knowledge overhead so that we didn’t have to say like, okay, if we’re bringing on other developers, like junior developers work on it, oh, it would be nice if you use Laravel too because we use this templating engine in all of our themes. We didn’t want to have to worry about that essentially. It was all object-oriented and all that stuff too. That’s what looked interesting to me. We ended up building a theme with WP Rig. I don’t know what they ended up doing with it after that, because I ended up getting let go shortly thereafter because the company had recently been acquired. Also, this was right after COVID too. So there was just a lot of moving parts and changing things at the time. So I ended up getting let go. But literally a week after I got let go, I came across a post on WP Tavern about how this framework was looking for new maintainers. Basically, this was a call put out by Morton, the original author of WP Rig. He reached out to WP Tavern and said, “Look, we’re not interested in maintaining this thing anymore, but it’s pretty cool. We like what we’ve built. And so we’re looking for other people to come in and adopt it essentially.” So I joined a Zoom meeting with a handful of other individuals that were also interested in this whole endeavor, and Morton reached out to me after the call and basically just said, “I looked you up. I liked some of the input that you had during the meeting. Let’s talk a little bit more.” And then that eventually led to conversations about me essentially taking the whole project over entirely. So, the branding, the hosting of the website, being lead maintainer on the project. Basically, gave me the keys to the kingdom in terms of GitHub and everything. So that’s how it ended up going in terms of the handoff between Morton and I. And I’m very grateful to him. They really created something super cool and I was honored to take it over and kind of, I don’t know, keep it going, I guess. Topher: I would be really curious. I don’t think either of us have the answer. I’d be curious to know how similar that path is to other project handoffs. It’s different from like an acquisition. You didn’t buy a plugin from somebody. It was kind of like vibes, I guess. Rob: It was like vibes. It was very vibey. I guess that’s probably the case in an open source situation. It’s very much an open source project. It’s a community-driven thing. It’s for everybody by everybody. I don’t know if all open source community projects roll like that, but that’s how this one worked out. There was some amount of ownership on Morton’s behalf. He did hire somebody to do the branding for WP Rig and the logo. And then obviously he was paying for stuff like the WPrig.io domain and the hosting through SiteGround and so on and so forth. So, we did have to transfer some of that and I’ve taken over those, I guess, financial burdens, if you want to think of it like that. But I’m totally okay with it. Topher: All right. You sort of mentioned some of the things Rig does, compiling and all that kind of stuff. Can you tell me… we didn’t discuss this before. I’m sitting at my desk and I think I want a website. How long does it take to go from that to looking at WordPress and logging into the admin with Rig? Rob: Okay. Rig is not an environment management system like local- Topher: I’m realizing my mistake. Somebody sends me a design in Figma. How long does it take me to go from that to, I’m not going to say complete because I mean, that’s CSS, but you know, how long does it take me to get to the point where I’m looking at a theme that is mine for the client that I’m going to start converting? Rob: Well, if you’re just looking for a starting point, if you’re just like, okay, how long does it take to get to like, okay, here’s my blank slate and I’m ready to start adopting all of these rules that are set up in Figma or whatever, I mean, you’re looking at maybe 5 minutes, 10 minutes, something like that. It’s pretty automated. You just need some simple knowledge of Git. And then there are some prerequisites to using WP Rig. You do have to have composer installed because we do leverage some Composer packages to some of it, although to be honest, you could probably get away with not using Composer. You just have to be okay with sacrificing some of the tools the WP Rig assumes you’re going to have. And then obviously Node. You have to have Node installed. A lot of our documentation assumes that you have NPM, that you’re using NPM for all your Nodes or your package management. But we did recently introduce support for Bun. And so you can use Bun instead of NPM, which is actually a lot faster and better in many ways. Topher: Okay. A lot of my audience are not developers, users, or light developers, like they’ll download a theme, hack a template, whatever. Is this for them? Am I boring those people right now? Rob: That’s a great question. I mean, and I think this is an interesting dichotomy and paradigm in the WordPress ecosystem, because you’ve got kind of this great divide. At least this is something I’ve noticed in my years in the WordPress community is you have many people that are not coders or developers that are very interested in expanding their knowledge of WordPress, but it’s strictly from a more of a marketing perspective where it’s like, I just want to know how to build websites with WordPress and how to use it to achieve my goals online from a marketing standpoint. You have that group of people, and then you have this other group of people that are very developer centric that want to know how to extend WordPress and how to empower those other people that we just discussed. Right? Topher: Right. Rob: So, yeah, that’s a very good question. I would say that WP Rig is very much designed for the developers, not for the marketers. The assumption there is that you’re going to be doing some amount of coding. Now, can you get away with doing a very light amount of coding? Yes. Yes, you can. I mean, if you compare what you’re going to get out of that assumed workflow to something that you would get off like Theme Forest or whatever, it’s going to be a night and day difference because those theme, Forest Themes, have hours, hundreds, sometimes hundreds of hours of development put into them. So, you’re not going to just out of the box immediately get something that is comparable to that. Topher: You need to put in those hundreds of hours of development to make a theme. Rob: As of today, yes. That may change soon though. Topher: Watch this space. Rob: That’s all I’ll say. Topher: Okay. So now we know who it’s for. I’m assuming there’s a website for it. What is it? Rob: Yeah. If you go to WPrig.io, we have a homepage that shows you all the features that are there in WP Rig. And then there’s a whole documentation area that helps people get up and running with WP Rig because there is a small learning curve there that’s pretty palatable for anybody who’s familiar with modern development workflows. So that is a thing. So the type of person that this is designed for anybody that wants to make a theme for anything. Let’s say you’re a big agency and you pull in a big client and that client wants something extremely custom and they come to you with Figma designs. Sure, you could go out there and find some premium theme and try to like child theme and overhaul that if you want. But in many situations, I would say in most situations, if you’re working from a Figma design that’s not based off of another theme already that’s just kind of somebody else’s brainchild, then you’re probably going to want to start from scratch. And so the idea here is that this is something to replace an approach, like underscores an approach. Actually, WP Pig was based off of underscores. The whole concept of it, as Morton explained it to me, was that he wanted to build an underscores that was more modern and full-featured from a development standpoint. Topher: Does it have any opinions about Gutenberg? Rob: It does now, but it did not when I took it over because Gutenberg did not exist yet when I took over WP Rig. Topher: Okay. What are its opinions? Rob: Yeah, sure. The opinion right out of the gate is that you can use Gutenberg as an editor and it has support like CSS rules in it for the standard blocks. So you should be able to use regular Gutenberg blocks in your theme and they should look just fine. There’s no resets in there. It doesn’t start from scratch. There’s not a bunch of styling you have to do for the blocks necessarily. Now, if you go to the full site editing or block-based mentality here, there are some things you need to do in WP Rig to convert the out-of-the-box WP Rig into another paradigm essentially. Right when you pull WP Rig, the assumption is you’re building what most people would refer to as a hybrid theme. The theme supports API or whatever, and the assumption is that you’re not going to be using the site editor. You’re just going to kind of do traditional WordPress, but you might be using Gutenberg for your content. So you’re just using Gutenberg kind of to author your pages and your posts and stuff like that, but not necessarily the whole site. WP Rig has the ability to kind of transform itself into other paradigms. So the first paradigm we built out was the universal theme approach. And the idea there is that you get a combination of the full site editing capabilities. But then you also have the traditional menu manager and the settings customizer framework or whatever is still there, right? These are things that don’t exist in a standard block-based theme. So I guess an easy example would be like the 2025 WordPress theme that comes right out of the box. It comes installed in WordPress. That is a true block-based theme, not a universal theme. So it doesn’t have those features because the assumption there is that it doesn’t need those features. You can kind of transform WP Rig into a universal theme that’s kind of a hybrid between a block-based and a classic theme. And then it can also transform into a strictly block-based theme as well. So following the same architecture as like the WordPress 2025 theme or Ollie or something like that is also a true block-based theme as well. So you can easily convert or transform the starting point of WP Rig into either of those paradigms if that’s the type of theme you’re setting out to build. Topher: Okay. That sounds super flexible. How much work is it to do that? Rob: It’s like one command line. Previously we had some tutorials on the website that showed you step-by-step, like what you needed to change about the theme to do that. You would have to add some files, delete some files, edit some code, add some theme supports into the base support class and some other stuff. I have recently, as of like a year and a half ago or a year ago, created a command line or a command that you can type into the command line that basically does that entire conversion process for you in like the blink of an eye. It takes probably a second to a second and a half to perform those changes to the code and then you’re good to go. It is best to do that conversion before you start building out your whole theme. It’s not impossible to do it after. But you’re more likely to run into problems or conflicts if you’ve already set out building your whole theme under one paradigm, and then you decide how the project you want to switch over to block-based or whatever. You’re likely to run into the need to refactor a bunch of stuff in that situation. So it is ideal to make that choice extremely early on in the process of developing your theme. But either way it’ll still work. That’s just one of the many tools that exist in WP Rig to transform it or convert it in several ways. That’s just one example. There are other examples of ways that Rig kind of converts itself to other paradigms as well. Topher: Yeah. All right. In my development life, I’ve had two parts to it. And one is the weekend hobbyist, or I download cadence and I whip something up in 20 minutes because I just want to experiment and the other is agency life where everything’s in Git, things are compiled, there are versions, blah, blah, blah. This sounds very friendly to that more professional pathway. Rob: Absolutely. Yes. Or, I mean, there’s another situation here too. If you’re a company who develops themes and publishes them to a platform like ThemeForest or any other platform, perhaps you’re selling themes on your own website, whatever, if you’re making things for sale, there’s no reason you couldn’t use WP Rig to build your themes. We have a bundle process that bundles your theme for publication or publishing. Whether you’re an agency or whether you’re putting your theme out for sale, it doesn’t matter, during that bundle process, it does actually white label the entire code base to where there’s no mention of WP Rig in the code whatsoever. Let’s say you were to build a theme that you wanted to put up for sale because you have some cool ideas. Say, page transitions now are completely supported in all modern or in most modern browsers. And when I say print page transitions, for those that are in the know, I am talking about not single page app page transitions, but through website page transitions. You can now do that. Let’s say you were like, “Hey, I’m feeling ambitious and I want to put out some new theme that comes with these page transitions built in,” and that’s going to be fancy on ThemeForest when people look at my demo, people might want to buy that. You could totally use WP Rig to build that out into a theme and the bundle process will white label all of the code. And then when people buy your theme and download that code, if they’re starting to go through and look through your code, they’re not going to have any way of knowing that it was built with WP Rig unless they’re familiar with the base WP Rig architecture, like how it does its object-oriented programming. It might be familiar with the patterns that it’s using and be able to kind of discern like, okay, well, this is the same pattern WP Rig uses, so high likelihood it was built with WP Rig. But they’re not going to be able to know by reading through the code. It’s not going to say WP Rig everywhere. It’s going to have the theme all over the place in the code. Topher: Okay. So then is that still WP Rig code? It just changed its labels? Rob: Yeah. Topher: So, it’s not like you’re exporting HTML, CSS and JavaScript? The underlying Rig framework is still there. Rob: Yeah. During the bundle process, it is bundling CSS and HTML. Well, HTML in the case of a block-based theme. But, yeah, it is bundling your PHP, your CSS, your JavaScript into the theme that you’re going to let people download when they buy it, or that you’re going to ship to your whatever client’s website. But all that code is going to be transpiled. In the case of CSS and JavaScript, there’s only going to be minified versions of that code in that theme. The source code is not actually going to be in there. Topher: This sounds pretty cool. You mentioned some stuff might be coming. You don’t have to tell me what it is, but do you have a timeline? When should we be watching for the next cool thing from Rig? Rob: Okay, cool. Well, I’m going to keep iterating on Rig forever. Regardless of any future products that might be built on WP Rig, WP Rig will always and forever remain an open source product for anybody to use for free and we, I, and possibly others in the future will continue to update it and support it over time. We just recently put out 3.1. You could expect the 3.2 anytime in the next six months to a year, probably closer to six months. One feature I’m looking at particularly closely right now is the new stuff coming out in version 6.9 of WordPress around the various APIs that are there. I think one of them is called the form… There’s a field API and a form API or view API or something like that. So WP Rig comes with a React-based settings framework in it. So if you want your theme to have a bunch of settings in it to make it flexible for whoever buys your theme, you can use this settings framework to easily create a bunch of fields, and then that framework will automatically manage all your fields and store all the data from those fields and make it easy to retrieve the values of the input on those fields, without knowing any React at all. Now, if you know React, you can go in there and, you know, embellish what’s already there, but it takes a JSON approach. So if you just understand JSON, you can go in and change the JSON for the framework, and that will automatically add fields into the settings framework. So you don’t even have to know React to extend the settings page if you want. That will likely get an overhaul using these new APIs being introduced into Rig. Topher: All right. How often have you run into something where, “Oh, look, WordPress has a new feature, I need to rebuild my system”? Rob: Over the last four or five years, it’s happened a lot because, yeah, I mean, like I said, when I first took this thing over, Gutenberg had not even been introduced yet. So, you had the introduction of Gutenberg and blocks. That was one thing. Then this whole full site editing became a thing, which later became the site editor. So that became a whole thing. Then all these various APIs. I mean, it happens quite frequently. So I’ve been working to keep it modern and up to date over the past four years and it’s been an incredible learning experience. It not only keeps my WordPress knowledge extremely sharp, but I’ve also learned how various other toolkits are built. That’s been the interesting thing. From a development standpoint, there’s two challenges here. One of the challenges is staying modern on the WordPress side of things. For instance, WordPress coding standards came out with a version 3 and then a version 3.1 about two years ago. I had to update WP Rig to leverage those modern coding standards. So that’s one example is as WordPress changes, the code in WP Rig also needs to change. Or for instance, if new CSS standards change, right, new CSS properties come out, it is ideal for the base CSS in WP Rig, meaning the CSS that you get right out of the box with it, comes with some of these, for instance, CSS grid, Flexbox, stuff like that. If I was adopting a theme framework to build a theme on, I would expect some of that stuff to be in there. And those things were extremely new when I first took over WP Rig and were not all baked in there essentially. So I’ve had to add a lot of that over time. Now there’s another side to this, which is not just keeping up with WordPress and CSS and PHP, 8. whatever, yada yada yada. You’ve also got the toolkit. There are various node packages and composer packages of power WP Rig and the process in which it does the transpiling, the bundling, the automated manipulation of your code during various aspects of the usage of WP Rig is a whole nother set of challenges because now you have to learn concepts like, well, how do I write custom node scripts? Right? Like there were no WP CLI commands built into WP Rig when I first took it over. Now there’s a whole list. There’s a whole library of WP CLI commands that come in Rig right out of the gate. And so I’ve had to learn about that. So just various things that come with knowing how do you automate the process of converting code, that’s something that was completely foreign to me when I first took over WP Rig. That’s been another incredible learning experience is understanding like what’s the difference between Webpack and Gulp. I didn’t know, right? I would tell people I’m using Gulp and WP Rig and they would be like, “Well, why don’t you just use Webpack?” and I would say, “I don’t know. I don’t know what the difference is.” So over time I could figure out what are the differences? Why aren’t we using Webpack? And I’m glad I spent some time on that because it turns out Webpack is not the hottest thing anymore, so I just skipped right over all that. When I overhauled for version 3, we’re now not using Gulp anymore as of 3.1. We’re now using more of a Vite-like process, far more modern than Webpack and far better and faster and sleeker and lighter. I had to learn a bunch about what powers Vite. What is Vite doing under the hood that we might be able to also do in WP Rig, but do it in a WordPress way. Because Vite is a SaaS tool. If you’re building a SaaS, like React with a… we’re not a SaaS. I guess a spa is a better term to use here. If you’re building a single page application with React or view or belt or whatever, right, then knowing what Vite is and just using Vite right out of the box is perfect. But it doesn’t translate perfectly to WordPress land because WordPress has its own opinions. And so I did have to do some dissecting there and figure out what to keep and what to not keep to what to kind of set aside so that WordPress can keep doing what WordPress does the way WordPress likes to do it, but also improve on how we’re doing some of the compiling and transpiling and the manipulation of the code during these various. Topher: All right. I want to pivot a little bit to some personal-ish questions. Rob: Okay. Topher: This is a big project. I’m sure it takes up plenty of your time. How scalable is that in your life? Do you want to do this for the rest of your life? Rob: That’s a fantastic question. I don’t know about the rest of my life. I mean, I definitely want to do web development for the rest of my life because the web has, let’s be honest, it’s transformed everyone’s way of life, whether you’re a web developer or not. You know, the fact that we have the internet in our pocket now, you know, it has changed everything. Apps, everything. It’s all built on the web. So I certainly want to be involved in the web the rest of my life. Do I want to keep doing WordPress the rest of my life? I don’t know. Do I want to keep doing WP Rig the rest of my life? I don’t know. But I will say that you bring up a very interesting point, which is it does take up a lot of time and also trust in open source over the past four or five years I would argue has diminished a little bit as a result of various events that have occurred over the past two or three years. I mean, we could cite the whole WP Engine Matt Mullerwig thing. We can also cite what’s going on with Oracle and JavaScript. Well, I mean, there’s many examples of this. I mean, we can cite the whole thing that happened… I mean, there’s various packages out there that are used and developed and open source to anybody, and some of them are going on maintained and it’s causing security vulnerabilities and degradation and all this stuff. So it’s a very important point. One thing I started thinking about after considering that in relation to WP Rig was I noticed that there’s usually a for-profit arm of any of these frameworks that seems to extend the lifespan of it. Let’s just talk about React, for example, React is an open source JavaScript framework, but it’s used by Facebook and Facebook is extremely for-profit. So companies that are making infrastructural or architectural decisions, they will base their choice on whether or not to use a framework largely on how long they think this framework is going to remain relevant or valid or maintained, right? A large part of that is, well, is there a company making money off of this thing? Because if there is, the chances- Topher: They’re going to keep doing that. Rob: They’re going to keep doing it. It’s going to stay around. That’s good. I think that’s healthy. A lot of people that like open source and want everything to be free, they might look at something like that and say like, well, I don’t want you to make a paid version of it or there shouldn’t be a pro version. I think that’s a very short-sighted way of looking at that software and these innovations. I think a more experienced way of looking at it is if you want something to remain relevant and maintained for a long period of time, having a for-profit way in which it’s leveraged is a very good thing. I mean, let’s be real. Would WordPress still be what it is today if there wasn’t a wordpress.com or if WooCommerce wasn’t owned by Automattic or whatever, right? They’ll be on top. I mean, it’s obviously impossible to say, but my argument would be, probably not. I mean, look at what’s happened to the other content management systems out there. You know, Joomla Drupal. They don’t really have a flourishing, you know, paid pro service that goes with their thing that’s very popular, at least definitely not as popular as WordPress.com or WordPress VIP or some of these other things that exist out there. And so having something that’s making and generating money that can then contribute back into it the way Automattic has been doing with WordPress over these years has, in my opinion, been instrumental. I mean, people can talk smack about Gutenberg all they want, but let’s be real, it’s 2025, would you still feel that WordPress is an elegant solution if we were still working from the WYSIWYG and using the classic editor? And I know a lot of people are still using the classic editor and there’s classic for us, the fork and all that stuff. But I mean, that only makes sense in a very specific implementation of WordPress, a very specific paradigm. If you want to explore any of these other paradigms out there, that way of thinking about WordPress kind of falls apart pretty quickly. I, for one, am happy that Gutenberg exists. I’m very happy that Automattic continues. And I’m grateful, actually, that Automattic continues to contribute back into WordPress. And not just them, obviously there’s other companies, XWP, 10Up, all these other companies are also contributing as well. But I’m very grateful that this ecosystem exists and that there’s contribution going back in and it’s happening from companies that are making money with this. And I think that’s vital. All that to say that WP Rig may and likely will have paid products in the future that leverage WP Rig. So that’s not to say that WP Rig will eventually cost money. That’s just to say that eventually people can expect other products to come out in the future that will be built on WP Rig and incentivize the continued contributions back into WP Rig. The open source version of WP Rig. Topher: That’s cool. I think that’s wise. If you want anything to stay alive, you have to feed it. Rob: That’s right. Topher: I had some more questions but I had forgotten them because I got caught up in your answer. Rob: Oh, thank you. I’ll take that as a compliment. I mean, my answer was eloquent. But I’m happy to expand on anything, know you, WordPress related, me related, you know, whether it comes to the ecosystem in WordPress, the whole WordCamp meetup thing is very interesting. I led the WP Omaha meetup for many years here in Omaha, Nebraska and I also led the WordCamp, the organizing of WordCamp here in Omaha for several years as well. That whole community, the whole ecosystem, at least in America seems to have largely fallen apart. I don’t know if you want to talk about that at all. But yeah, I’m ready to dive into any topics. Topher: I’m going to have one more question and then we’re going to wrap up. And it was that you were talking about all the things you had to learn. I’m sure there were nights where you were looking at your computer thinking, “Oh man, I had it working, now I gotta go learn a new thing.” I would love for you to go back in time and blog all of that if you would. But given that you can’t, I would be interested in a blog moving forward, documenting what you’re learning, how you’re learning it and starting maybe with a post that’s summarizes all of that. Obviously, that’s up to you and how you want to spend your time, but I think it’d be really valuable to other people starting a project, picking up somebody else’s project to see what the roadmap might look like. You know what I mean? Rob: For sure. Well, I can briefly summarize what I’ve learned over the years and where I’m at today with how I do this kind of stuff. I will say that a lot of the improvements to WP Rig that have happened over the last year or two would not be possible without the advent of AI. Topher: Interesting. Rob: That’s a fancy way of saying that I have been by coding a lot of WP Rig lately. If you know how to use AI, it is extremely powerful and it can help you do many things very quickly that previously would have taken much longer or more manpower. So, yeah, perhaps if there was like five, six, seven people actively, excuse me, actively contributing to WP Rig, then this type of stuff would have been possible previously, but that’s not the case. There is one person, well, one main contributor to WP Rig today and you’re talking to them. There are a handful of other people that have been likely contributing to WP Rig over the versions and you can find their contributions in the change log file in WP Rig. But those contributions have been extremely light compared to what I’ve been doing. I wouldn’t be able to do any of it without AI. I have learned my ability to learn things extremely rapidly has ramped up tenfold since I started learning how to properly leverage LLMs and AI. So that’s not to say that like, you know, WP Rig, all the code is just being completely written by AI and I’m just like. make it better, enter, and then like WP Rig is better. I wish it was that easy. It’s certainly not that. But when I needed to start asking some of these vital questions that I really didn’t have anyone to turn to to help answer them, I was able to turn to AI. For instance, let’s go back to the Webpack versus Gulp situation. Although Gulp is no longer used in WP Rig, you know, it was used in WP Rig until very recently. So I had to understand like, what is this system, how does it work, how do I extend it and how do I update it and all these things, right? And why aren’t we using WebPack and you know, is there validity to this criticism behind you should use webpack instead of Gulp or whatever, right? I was able to use AI to ask these questions and be able to get extremely good answers out of it and give me the direction I needed to make some of these kind of higher level decisions on like architecturally where should WP Rig go? It was through these virtual conversations with LLMs that I was able to refine the direction of WP Rig in a direction that is both modern and forward-thinking and architecturally sound. I learned a tremendous amount from AI about the architecture, about the code, about all of it. My advice to anybody that wants to extend their skill set a little bit in the development side of things is to leverage this new thing that we have in a way that is as productive as possible for you. So that’s going to vary from person to person. But for me, if I’m on a flight or if I’m stuck somewhere for a while, like, let’s say I got to take my kid to practice or something and I’m stuck there for an hour and I got to find some way to kill my time 9 times out of 10, I’m on my laptop or on my phone having conversations with Grok or ChatGPT or Gemini or whatever. I am literally refining… I’m just sitting there asking it questions that are on my mind that I wish I could ask somebody who’s like 10 times more capable than me. It has been instrumental. WP Rig wouldn’t be where it is today if it wasn’t for that. I would just say to anybody, especially now that it’s all on apps and you don’t have to be on a browser anymore, adopt that way of thinking. You know, if you’re on your lunch break or whatever and you have an hour lunch break and you only take 15 minutes to eat, what could you be doing with those other 45 minutes? You could just jump on this magical thing that we have now and start probing it for questions. Like, Hey, here’s what I know. Here’s what I don’t know. Fill these knowledge gaps for me.” And it is extremely good at doing that. Topher: So my question was, can you blog this and your answer told me that there’s more there that I want to hear. That’s the stuff that should be in your book when you write your book. Rob: I’m flattered that you would be interested in reading anything that I write. So thank you. I’ve written stuff in the past and it hasn’t gotten a lot of attention. But I also don’t have any platforms to market it either. But yeah, no, I made some… I’m sorry. Topher: I think your experience is valuable far beyond Rig or WordPress. If you abstract it out of a particular project to say, you know, I did this with a project, I learned this this way, I think that would be super valuable. Rob: Well, I will say that recently at my current job, I was challenged to create an end to end testing framework with Playwright that would speed up how long it takes to test things and also prevent, you know, to make things fail earlier, essentially, to prevent broken things from ending up in the wild, right, and having to catch them the hard way. I didn’t know a lot about Playwright, but I do know how toolkits work now because of WP Rig. And I was able to successfully in a matter of, I don’t know, three days, put together a starter kit for a test framework that we’re already using at work to test any website that we create for any client. It can be extended and it can be hooked into any CI CD pipeline and it generates reports for you and it does a whole bunch of stuff. I was able to do this relatively quickly. This knowledge, yes, does come in handy in other situations. Will I end up developing other toolkits like WP Rig in the future for other things? I guess if I can give any advice to anybody listening out there, another piece of advice I would give people is, you know, especially if you’re a junior developer and you’re still learning or whatever, or you’re just a marketing person and just want to have more control over the functionality side of what you’re creating or more insight into that so you could better, you know, manage projects or whatever. My advice would be to take on a small little project that is scoped relatively small that’s not too much for you to chew and go build something and do it with… Just doing that will be good. But if you can do it with the intent to then present it in some fashion, whether it be a blog article or creating a YouTube video or going to a meetup and giving a talk on it or even a lunch and learn at work or whatever, right, that will, in my experience, it will dramatically amplify how much you learn from that little pet project that’s kind of like a mini learning experience. And I highly encourage anybody out there to do that on the regular. Actually, no matter what your experience level is in development, I think you should do these things on a regular basis. Topher: All right. I’m going to wrap this up. I got to get back to work. You probably have to get back to work. Rob: Yeah. Topher: Thanks for talking. Rob: Thanks for having me, Topher. Really appreciate it. Topher: Where could people find you? WPrig.io?  Rob: Yeah, WPrig.io. WP rig has accounts on all of the major platforms and, even on Bluesky and Mastodon. You can look me up, Rob Ruiz. You can find me on LinkedIn. You can find me on all of those same platforms as well. You can add me on Facebook if you want, whatever. And I’m also in the WordPress Slack as well as Rob Ruiz. You can find me in the WordPress Slack. And then I’m on the WordPress Reddit and all that stuff. So yeah, reach out. If anybody wants to have any questions about Rig or anything else, I’m happy to engage.  Topher: Sounds good. All right, I’ll see you. Rob: All right, thanks, Topher. Have a good day. Topher: This has been an episode of the Hallway Chats podcast. I’m your host Topher DeRosia. Many thanks to our sponsor Nexcess. If you’d like to hear more Hallway Chats, please let us know on hallwaychats.com.

This is a special episode, highlighting a session from ELC Annual 2025! OpenAI evolved from a pure research lab into the fastest-growing product in history, scaling from 100 million to 700 million weekly users in record time. In this episode, we deconstruct the organizational design choices and cultural bets that enabled this unprecedented velocity. We explore what it means to hire "extreme generalists," how AI-native interns are redefining productivity, and the real-time trade-offs made during the world's largest product launches. Featuring Sulman Choudhry (Head of ChatGPT Engineering) and Samir Ahmed (Technical Lead), moderated by Lawrence Bruhmeller (Eng Management @ Sigma). ABOUT SULMAN CHOUDHRYSulman leads ChatGPT Engineering at OpenAI, driving the development and scaling of one of the world's most impactful AI products. He pushes the boundaries of innovation by turning cutting‑edge research into practical, accessible tools that transform how people interact with technology. Previously at Meta, Sulman founded and scaled Instagram Reels, IGTV, and Instagram Labs, and helped lead the early development of Instagram Stories.He also brought MetaAI to Instagram and Messenger, integrating generative AI into experiences used by billions. Earlier in his career, Sulman was on the founding team that built and launched UberEATS from the ground up, helping turn it into a global food delivery platform. With a track record of marrying technical vision, product strategy, and large‑scale execution, Sulman focuses on building products that meaningfully change how people live, work, and connect.ABOUT SAMIR AHMEDSamir is the Technical Lead for ChatGPT at OpenAI, where he currently leads the Personalization and Memory efforts to scale adaptive, useful, and human-centered product experiences to over 700 million users. He works broadly across the OpenAI stack—including mobile, web, services, systems, inference, and product research infrastructure.Previously, Samir spent nine years at Snap, working across Ads, AR, Content, and Growth. He led some of the company's most critical technical initiatives, including founding and scaling the machine learning platform that powered nearly all Ads, Content, and AR workloads, handling tens of billions of requests and trillions of inferences daily.ABOUT LAWRENCE BRUHMELLERLawrence Bruhmuller has over 20 years of experience in engineering management, much of it as an overall head of engineering. Previous roles include CTO/VPE roles at Great Expectations, Pave, Optimizely, and WeWork. He is currently leading the core query compiler and serving teams at Sigma Computing, the industry leading business analytics company.Lawrence is passionate about the intersection of engineering management and the growth stage of startups. He has written extensively on engineering leadership (https://lbruhmuller.medium.com/), including how to best evolve and mature engineering organizations before, during and after these growth phases. He enjoys advising and mentoring other engineering leaders in his spare time.Lawrence holds a Bachelors and Masters in Mathematics and Engineering from Harvey Mudd College. He lives in Oakland, California, with his wife and their three daughters. This episode is brought to you by Span!Span is the AI-native developer intelligence platform bringing clarity to engineering organizations with a holistic, human-centered approach to developer productivity.If you want a complete picture of your engineering impact and health, drive high performance, and make smarter business decisions…Go to Span.app to learn more! SHOW NOTES:From research lab to record-breaking product: Navigating the fastest growth in history (4:03)Unpredictable scaling: Handling growth spurts of one million users every hour (5:20)Cross-stack collaboration: How Android, systems, and GPU engineers solve crises together (7:06)The magic of trade-offs: Aligning the team on outcomes like service uptime vs. broad availability (7:57)Why throwing models "over the wall" failed and how OpenAI structures virtual teams (11:17)Lessons from OpenAI's first intern class: Why AI-native new grads are crushing expectations (13:41)Non-hierarchical culture: Using the "Member of Technical Staff" title to blur the lines of expertise (15:37)AI-native engineering: When massive code generation starts breaking traditional CI/CD systems (16:21)Asynchronous workflows: Using coding agents to reduce two-hour investigations to 15 minutes (17:35)The mindset shift: How rapid model improvements changed how leaders audit and trust code (19:00)Predicting success: "Vibes-based" decision making and iterative low-key research previews (20:43)Hiring for high variance: Why unconventional backgrounds lead to high-potential engineering hires (22:09) LINKS AND RESOURCESLink to the video for this sessionLink to all ELC Annual 2025 sessions This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/405Yevgeniy "Jim" Brikman - Author of "Fundamentals of DevOps and Software Delivery" & Co-Founder of GruntworkKief Morris - Author of "Infrastructure as Code" & Distinguished Engineer at ThoughtworksRESOURCESYevgeniy (Jim)https://bsky.app/profile/brikis98.bsky.socialhttps://twitter.com/brikis98https://github.com/brikis98/https://www.linkedin.com/in/jbrikmanhttps://www.ybrikman.comKiefhttps://bsky.app/profile/kief.comhttps://twitter.com/kiefhttps://github.com/kiefhttps://www.linkedin.com/in/kiefmorrishttps://infrastructure-as-code.comhttps://kief.comLinkhttps://terragrunt.gruntwork.ioDESCRIPTIONYevgeniy (Jim) Brikman, author of "Fundamentals of DevOps and Software Delivery", discusses his journey from app developer to DevOps advocate, triggered by LinkedIn's deployment crisis that required freezing all product development for months. The discussion with Kief Morris explores the practical definition of DevOps as efficient software delivery methodology, the relationship between infrastructure as code and application orchestration tools, the necessity of frameworks over custom wrapper scripts, and emerging paradigms including infrastructure from code, infrastructure as graph models, and interactive runbooks.Jim emphasizes that while new approaches are interesting, maturity and standardization in existing tools often provides more value than constantly chasing new technologies.RECOMMENDED BOOKSYevgeniy Brikman • Fundamentals of DevOps and Software Delivery • https://amzn.to/3WMPMFUYevgeniy Brikman • Terraform: Up and Running • https://amzn.to/4otpxQLYevgeniy Brikman • Hello, Startup • https://amzn.to/3JmV0VRKief Morris • Infrastructure as Code • https://amzn.to/4e6EBQcMauricio Salatino • Platform Engineering on Kubernetes • https://amzn.to/3X14qZKCharity Majors, Liz Fong-Jones & George Miranda • Observability Engineering • https://amzn.to/38scbmaBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Bentornati e bentornate su Azure Italia Podcast, il podcast in italiano su Microsoft Azure!Per non perderti nessun nuovo episodio clicca sul tasto FOLLOW del tuo player

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

In 2026, security is no longer a final checkpoint; it is the very foundation of the code you write. With global cybercrime costs crossing the $10.5 trillion mark, the industry has moved toward a "Secure-by-Design" mandate. This episode dives into the DevSecOps revolution: the art of bridging the gap between rapid innovation and stringent regulatory compliance (GDPR, HIPAA, SOC-2). We explore the specialized tools that transform compliance from a manual bottleneck into an automated, self-running process within your CI/CD pipeline.

An airhacks.fm conversation with Johan Haleby (@johanhaleby) about: first computer experience with Commodore C64 and typing Basic programs from instruction manuals, early gaming experiences and interest in understanding load commands, transition to Amiga 500 Plus for demo scene scripting and composition, moving to PC era with 486 SX25 and four megabytes of RAM, learning Turbo Pascal and creating 2D Super Mario-inspired games, experimenting with inline assembler in Pascal and reading "The Art of Assembly Programming", reverse engineering games using Win32 disassembler to bypass license checks, studying computer science at Blekinge and Lund University in Sweden, first job at JayWay consultancy firm working on IKEA project in 2005, early adoption of Spring framework and automated testing practices, comparison of old-style EJB with heavy XML configuration versus Spring's lightweight approach, the evolution from XML-based configuration to annotation-based Java EE 5 and 6, creating PowerMock with colleague Jan Kronqvist to mock static methods and final classes, using asm and JavaAssist for bytecode manipulation instead of AspectJ, implementing custom class loaders where each JUnit method executed in different class loader, deep clone module for cloning object graphs between class loaders, tight coupling challenges between PowerMock and Mockito/EasyMock/JUnit versions, transition from EasyMock's record-replay pattern to Mockito's when-then approach, modern preference for avoiding mocks and testing against real cloud environments, optimizing for fast CI/CD pipelines rather than local simulation, structuring code to separate infrastructure concerns from pure business logic, using Java Records as pure data carriers versus adding behavior to records, Clojure-inspired philosophy of decoupling state from behavior and identity, Rich Hickey's "Simple Made Easy" talk and definitions of simple versus easy, multi-methods in functional languages as alternative to polymorphism, domain modeling example with network devices and fiber channel connections, benefits of object-oriented polymorphism for transparent persistence and simple code, avoiding religious adherence to patterns in favor of pragmatic solutions, Maven's stability and opinionated approach versus Gradle's flexibility, reducing external dependencies and Maven plugins in favor of CI/CD automation, the NPM ecosystem's over-modularization compared to Java's more reasonable approach, decline of OSGi hype and return to simpler monolithic architectures, Johan's current work on Occurrent Event Sourcing library and cloud events Johan Haleby on twitter: @johanhaleby

Join host Jaeden Schafer as he jumps into the world of AI with Spriha Baruah Tucker, Field CTO at BuildKite and a two-time Y Combinator founder. Discover how BuildKite is revolutionizing CI-CD platforms, the journey that led Spriha to her current role, and her insights on the future of AI in engineering. This episode is packed with valuable advice for companies looking to leverage AI effectively.Learn more about Buildkite: See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Neste episódio, vestimos a armadura do Homem de Ferro para falar de DevSecOps do jeito certo: sem buzzword, sem romantização e sem ferramenta milagrosa. DevSecOps aqui é engenharia, estratégia e responsabilidade compartilhada não um badge bonito no pipeline. Exploramos como AppSec se conecta ao DevSecOps quando o time para de “jogar segurança no final” e começa a projetar sistemas pensando em falha, ataque e resiliência desde o início. É o Jarvis rodando no CI/CD: dando contexto, alertando riscos e ajudando a tomar decisões melhores, não só gritando erro. Se você acha que DevSecOps é só SAST, DAST e um monte de check verde, esse episódio é um choque de realidade. Se você quer construir software como o Tony Stark constrói armaduras evoluindo a cada versão você está no lugar certo.Become a supporter of this podcast: https://www.spreaker.com/podcast/devsecops-podcast--4179006/support.Apoio: Nova8, Snyk, Conviso, Gold Security, Digitalwolk e PurpleBird Security.

Aytekin is the founder and CEO of JotForm, one of the most widely used no-code automation platforms in the world, serving more than 35 million users across education, healthcare, nonprofits, and small businesses. He's also the author of the Wall Street Journal and Publisher's Weekly bestselling book Automate Your Busy Work,00:00 – IntroductionFounder mindset, automation philosophy, and the future of work00:01 – Why Automate Your Busy Work Was Ahead of Its TimeNo-code, automation thinking before the AI boom01:09 – Building JotForm Before the AI Hype Cycle20 years of bootstrapping, slow growth, and real product-market fit02:29 – Forms as the Gateway to AutomationHow education, nonprofits, healthcare, and SMBs really work03:49 – From Forms to Workflows, Approvals, PDFs, and E-SignaturesDesigning automation for people without developers04:21 – Solo Founder Reality: Doing HR, Legal, Support, and Product AloneThe hidden cognitive cost of running everything yourself04:51 – Competing with Google Forms as a Bootstrapped FounderWhy automation and delegation became survival tools05:58 – Email Automation as Cognitive ReliefHow prioritization systems reduce stress and decision fatigue07:41 – Applying Automation Internally: Teams, CI/CD, and TestingWhy automation makes teams safer, not riskier08:10 – Designing Products Around How People Actually WorkFrom tools to systems thinking09:17 – Writing, Teaching, and Sharing Automation PrinciplesFrom Medium and Forbes to a bestselling book10:48 – Discovering the AI Revolution After Publishing the BookAutomation philosophy vs AI productivity tools11:16 – “People Aren't Overworked — They're Over-Busy”The psychology of modern work and burnout12:28 – Embodying Automation Principles Inside the CompanyScaling without chaos12:48 – Email Prioritization Systems That Actually WorkHow to design inboxes for executives and founders14:20 – Gmail Filters, Labels, and Decision AutomationSimple systems over complex tools16:59 – Automation as Stress Reduction, Not SpeedWhy missing important work causes burnout19:21 – Continuous Deployment and First-Day Code CommitsHow automation builds trust and confidence at scale21:12 – Why Automation Shouldn't Be FearedRisk reduction through systems22:08 – Internal Automation Lessons from JotForm's Engineering Culture23:01 – Future of Work: Policy, Strategy, and AIWEF, global work, and structural change24:32 – Does AI Kill Jobs or Create Better Ones?A real company case study25:02 – Deploying AI Support Without Laying Off EmployeesHow JotForm handled AI responsibly27:09 – Human-in-the-Loop AI SystemsWhy oversight matters more than hype28:19 – Training AI Through Documentation and FeedbackHow resolution rates improved from 25% to 75%31:01 – Improving AI Through Better Knowledge SystemsDocumentation as infrastructure32:36 – New Roles Created by AI AdoptionFrom support agents to AI evaluators33:29 – Multilingual AI Support at Global ScaleWhy AI enables inclusion, not just efficiency35:09 – Why JotForm Didn't Get AcquiredIndependence, focus, and long-term thinking39:29 – Focused Work, Fewer Hours, Higher LeverageRedefining productivity at scale41:06 – Evolution of JotForm Into a Full Automation PlatformFrom forms to AI agents and integrations42:09 – AI Agents Demo Discussion and Key TakeawaysReal use cases, real ROI46:18 – User Research at Massive ScaleLearning from 35 million users48:03 – Omnichannel AI Agents: Web, Instagram, Gmail, SalesforceTraining once, deploying everywhere49:35 – The Future of AI Agents as Digital EmployeesOne system, many touchpoints50:14 – Advice for Young Developers and FoundersHow to compete in the AI era50:49 – Growth Mindset Through Every Tech RevolutionFrom PCs to the internet to AI52:10 – Why This Is the Best Time to Be YoungOpportunities created by AI and no-code tools53:38 – Closing Reflections on Building, Learning, and PurposeA long-term view of work and life

It's that time of year—each host reaches into Santa's sack of topics to see who's been naughty and who's been nice. Ben returns from visiting his employer's manufacturing headquarters in Georgia with some philosophical musings. Carol is on a mission to slash CI/CD build times. Adam has cautiously optimistic news about passkeys finally working (sometimes). And Tim reflects on a TLDR article suggesting that the management skills you've built—knowing what to build and what not to build—might be exactly what AI-era coding demands.Plus: December blues, mushroom tea for focus, and jQuery as peak imperative JavaScript.Links mentioned:Owning A Lucid Has Been Super DisappointingDriving Xiaomi's Electric Car: Are we Cooked?Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @workingcode.dev on Bluesky. New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.With audio editing and engineering by ZCross Media.Full show notes and transcript here.

Send us a textCheck us out at:  https://www.cisspcybertraining.com/Get access to 360 FREE CISSP Questions:  https://www.cisspcybertraining.com/offers/dzHKVcDB/checkoutGet access to my FREE CISSP Self-Study Essentials Videos:  https://www.cisspcybertraining.com/offers/KzBKKouvHeadlines about eight Chrome zero days aren't just noise—they're a prompt to act with precision. We open with the fastest, most reliable steps to reduce exposure: force updates with MDM, restart browsers to trigger patches, narrow to a hardened enterprise browser, and brief your SOC to tune EDR for active exploit patterns. You'll get a focused checklist that's quick to run and easy to defend to leadership.From there, we turn the lens to CISSP Domain 8 with five questions that teach more than they test. We explain why strict schema validation for JSON beats blanket escaping, and how misuse and abuse case analysis during requirements gives you the strongest assurance that security is built into design, not bolted on. We also break down supply chain risk in CI/CD with a practical recipe: software composition analysis, cryptographic signature checks, internal artifact repositories, and policy gates that block malicious or license-violating packages before they ship.Design flaws are the silent killers. We highlight a common mistake—putting sensitive business logic in the browser—and show how to move decisions server-side, validate every request, and protect against client tampering. Finally, we get tactical about containerized microservices: image signing plus runtime verification, read-only filesystems, minimal base images, and network policies that enforce least privilege. These are the controls that turn incident response into a manageable drill, not a firestorm.If you're preparing for the CISSP or leading an engineering team, you'll leave with strategies you can apply today: browser patching that sticks, threat modeling that finds real risks, SCA that calms your pipeline, and container security that proves runtime trust. Enjoyed this conversation? Subscribe, share with a teammate, and leave a quick review to help more people find it.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Susanne Heipcke is Director of Software Engineering at FICO, where she has led the Modelling Team of FICO Xpress development for more than 12 years. Her team is responsible for the development and design of the modelling tools (Xpress Mosel) and the APIs of the Xpress Optimization software suite, with past tasks including the design of application development toolkits, solution templates, and productized optimization solutions such as FICO Decision Optimizer. More recently, her team's responsibilities have expanded to include CI/CD, performance testing, and delivery infrastructure for the entire Xpress suite. Before joining Dash Optimization (acquired by FICO in 2008) in 1998, she worked for BASF-AG in Germany. Her Ph.D. research at the University of Buckingham—conducted partly at the MIT OR Center (USA) and the University Aix-Marseille II (France)—focused on solving large-scale industrial problems using a combination of constraint programming and mixed integer programming. Her work centers on all aspects of modelling, particularly through her contributions to the development of the algebraic modelling and programming language Xpress Mosel. She is the author of the book Applications of Optimization with Xpress-MP and numerous papers on different aspects of mathematical modelling. Susanne enjoys teaching mathematical optimization, having participated in teaching the mathematical modelling course in the OR master's program at the University Aix-Marseille II (2001–2004) and the Computational Mixed-Integer Programming course at the Technical University of Munich in 2020. She regularly organizes specialist training events and conference sessions, such as the “Software for Optimization Modeling and Deployment” sessions at recent INFORMS Annual Meetings (jointly with Bob Fourer), and she is actively engaged in mentoring younger colleagues. Since 2019 she has been a member of the EURO Practitioners' Forum committee (formerly the EURO Working Group Practice of OR), leading the organization of the Forum's annual meetings in 2020, 2023, and 2026. With more than 30 years of experience in applied OR, she has also contributed to numerous consulting projects worldwide, involving scheduling and planning in manufacturing, personnel staffing, aircraft routing with maintenance planning, portfolio optimization, trading, energy production planning and unit commitment, and retail logistics.Contents of this video:0:00 - Intro1:27 - Family background and early years4:15 - Attending a girls' high school4:58 - Polyglot9:11 - Learning to program during high school11:13 - Moving to Bavaria to study mathematics13:19 - Practical data processing projects14:52 - Learning about OR16:31 - Master's thesis on constraint programming (CP) applied to a problem arising at BASF20:31 - Getting inspiration from a female leader at BASF22:14 - Spending half a year at the MIT OR Center + moving to the University of Buckingham for a PhD25:02 - Adapting to the UK26:06 - Combining MIP and CP to solve production planning and scheduling problems29:19 - Joining Dash Optimization in 199830:32 - Moving to France in 199931:20 - Working form home in an era before Zoom, Git, and similar tools existed32:28 - Maternity and work33:55 - The modelling language Xpress Mosel36:38 - Launching Mosel in 200139:45 - Evolution of Mosel over the years45:16 - Mosel's long-standing team47:35 - High compatibility across different versions of Mosel 48:16 - Xpress Mosel is a free software since 201849:21 - Favorite contributions to Mosel53:21 - Software engineering and optimization58:20 - AI and optimization software1:01:12 - Organizing conferences, workshops and special sessions regarding optimization software1:03:25 - EURO Practitioners' Forum1:04:52 - Regrets?1:05:18 - Plans for the future1:06:15 - Inspiring takeaway message1:07:22 - Concluding remarks

What does it take to make more environmentally sustainable software? Carl and Richard talk to Tom Herkhove about Microsoft's efforts to make carbon footprint and emissions visible for applications. Tom talks about the Azure API Management interface as a great starting point, and the ability to shift workloads to low-emission data centers as needed. The conversation also digs into wasted cycles, like automatically fired CI/CD pipelines whose results are never reviewed. It all begins with measuring - what action you take from there is up to you!

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

What does it take to make more environmentally sustainable software? Carl and Richard talk to Tom Herkhove about Microsoft's efforts to make carbon footprint and emissions visible for applications. Tom talks about the Azure API Management interface as a great starting point, and the ability to shift workloads to low-emission data centers as needed. The conversation also digs into wasted cycles, like automatically fired CI/CD pipelines whose results are never reviewed. It all begins with measuring - what action you take from there is up to you!

An airhacks.fm conversation with Stanislav Bashkyrtsev (@sbashkirtsev) about: Early programming journey starting with Pascal in school and C# self-study in 2005, transition from C# to Java through local programming courses in 2007, first experiences with Java 6 and EJB2/EJB3, working with Delphi for lawyers' desktop software before finding Java opportunities, first Java project for Madison Square Garden and New York Knicks website, career progression through entertainment and banking sectors including work with Barclays Capital and UBS, transition to CI/CD engineering in 2012 with heavy Jenkins usage and source code patching, challenges of implementing trunk-based development practices, automated QA engineering experiences with selenium testing, problems with separate QA and development teams affecting code testability, self-study of biology and chemistry leading to scientific software development, founding elsci company focused on high-performance enterprise software for chemists and biotech companies, disconnect between software developers and scientists' needs in scientific software, advantages of quarkus framework for serverless deployments on AWS, Quarkus build-time deployment optimization versus traditional application servers, comparison with Spring Boot auto-configuration complexity, migration experiences from Java EE to Quarkus maintaining standards compliance, virtual threads support in modern Quarkus, preference for Java 7 simplicity over modern Java streams, importance of end-to-end testing over unit testing pyramid, challenges of running a software company versus being an independent consultant, Helsinki Java User Group presentation on operating system thread mechanics Stanislav Bashkyrtsev on twitter: @sbashkirtsev

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Dave Thomas, author of The Pragmatic Programmer, The Manifesto for Agile Software Development, Programming Ruby, Agile Web Development with Rails, Programming Elixir, Simplicity, and co-founder of the Pragmatic Bookshelf, speaks with SE Radio host Gavin Henry about building infrastructure for eBooks. They discuss what an eBook is, the various formats, what infrastructure is needed to build them, how an author writes an book, the history of the Pragmatic Bookshelf, how they have evolved, how to handle links within eBooks, why humans are so important in the writing process, and why AI can help with your writing -- once you've written your content. Thomas discusses PDFs, eBooks, Mobi files, ePub files, CI/CD pipelines, WYSWYG, Markdown files, Pragmatic Markup Language, embedding code, AI agents, images, printing PDFs, JVMs, Java, jRuby, and how Markdown won the plain text writing format wars. Brought to you by IEEE Computer Society and IEEE Software magazine.

"La performance, c'est pas juste un benchmark dans un coin, c'est un vrai sujet d'équipe qui doit se traiter tout au long du cycle de développement." Le D.E.V. de la semaine est Adrien Cacciaguerra, cofondateur de CodSpeed. Ensemble, on plonge dans la performance logicielle, un sujet souvent relégué au second plan par les devs mais qui devient vite central quand le code rame en prod. Adrien partage les raisons qui l'ont poussé à créer CodSpeed pour aider les équipes à éviter les régressions et fiabiliser leurs déploiements. On explore l'intégration des tests de performance dans la CI/CD, les galères des environnements partagés et l'évolution des pratiques avec l'arrivée de l'IA et des LLM. Un échange nourri d'anecdotes, de conseils terrain et d'une vision lucide sur l'avenir de la perf et des outils.Chapitrages00:00:53 : Introduction à la performance00:01:13 : La genèse de CodSpeed00:05:34 : Optimisation des performances en CI00:07:52 : Environnement de test et métriques00:11:17 : Défis et solutions pour les bases de données00:14:36 : Mesurer la performance : enjeux et méthodes00:18:26 : L'impact des LLM sur la performance00:20:00 : Micro-optimisation vs. performance globale00:22:16 : Évaluer les tendances de performance00:25:04 : Outils de profiling et apprentissage pour les devs00:30:29 : Intégration de CodSpeed dans les langages00:32:27 : Variabilité des tests en environnement CI00:39:07 : Défis des systèmes distribués00:41:26 : L'avenir des performances avec les LLM00:48:41 : Conclusion et recommandations Liens évoqués pendant l'émission Chaine YT: Code Aesthetic **Restez compliant !** Cet épisode est soutenu par Vanta, la plateforme de Trust Management qui aide les entreprises à automatiser leur sécurité et leur conformité. Avec Vanta, se mettre en conformité avec des standards comme SOC 2, ISO 27001 ou HIPAA devient plus rapide, plus simple, et surtout durable. Plus de 10 000 entreprises dans le monde utilisent déjà Vanta pour transformer leurs obligations de sécurité en véritable moteur de croissance.

¿Estás seguro de que tu servidor Linux y tus contenedores Docker están a salvo de intrusos?

Rani Radhakrishnan is a Principal at PwC US, leading work on AI-managed services, autonomous agents, and data-driven transformation for enterprises.The Future of AI Operations: Insights from PwC AI Managed Services // MLOps Podcast #345 with Rani Radhakrishnan, Principal, Technology Managed Services - AI, Data Analytics and Insights at PwC US.Huge thanks to PwC for supporting this episode!Join the Community: https://go.mlops.community/YTJoinInGet the newsletter: https://go.mlops.community/YTNewsletter// AbstractIn today's data-driven IT landscape, managing ML lifecycles and operations is converging.On this podcast, we'll explore how end-to-end ML lifecycle practices extend to proactive, automation-driven IT operations.We'll discuss key MLOps concepts—CI/CD pipelines, feature stores, model monitoring—and how they power anomaly detection, event correlation, and automated remediation. // BioRani Radhakrishnan, a Principal at PwC, currently leads the AI Managed Services and Data & Insight teams in PwC US Technology Managed Services.Rani excels at transforming data into strategic insights, driving informed decision-making, and delivering innovative solutions. Her leadership is marked by a deep understanding of emerging technologies and a commitment to leveraging them for business growth.Rani's ability to align and deliver AI solutions with organizational outcomes has established her as a thought leader in the industry.Her passion for applying technology to solve tough business challenges and dedication to excellence continue to inspire her teams and help drive success for her clients in the rapidly evolving AI landscape. // Related LinksWebsite: pwc.com/us/aimanagedserviceshttps://www.pwc.com/us/en/tech-effect.html~~~~~~~~ ✌️Connect With Us ✌️ ~~~~~~~Catch all episodes, blogs, newsletters, and more: https://go.mlops.community/TYExploreJoin our Slack community [https://go.mlops.community/slack]Follow us on X/Twitter [@mlopscommunity](https://x.com/mlopscommunity) or [LinkedIn](https://go.mlops.community/linkedin)] Sign up for the next meetup: [https://go.mlops.community/register]MLOps Swag/Merch: [https://shop.mlops.community/]Connect with Demetrios on LinkedIn: /dpbrinkmConnect with Rani on LinkedIn: /rani-radhakrishnan-163615Timestamps:[00:00] Getting to Know Rani[01:54] Managed services[03:50] AI usage reflection[06:21] IT operations and MLOps[11:23] MLOps and agent deployment[14:35] Startup challenges in managed services[16:50] Lift vs practicality in ML[23:45] Scaling in production[27:13] Data labeling effectiveness[29:40] Sustainability considerations[37:00] Product engineer roles[40:21] Wrap up

Do you actually need a Release Engineer to manage Salesforce DevOps? Ana Moreno joins Jack to share her incredible (and truly accidental) journey from the world of art history to the heart of tech. Before they dive into release management, Jack derails the conversation to hear all about the fascinating world of art fraud, including tales of Man Ray's lost negatives and fake Victorian photographs.Once back on track, Ana pulls back the curtain on what it really takes to manage a complex, high-stakes Salesforce release process at a company that lives and breathes DevOps.Tune in to learn:- What the day-to-day life of a dedicated Release Engineer actually looks like.- How GitLab manages weekly Salesforce releases with a 30+ person team across five pods.- Strategies for handling merge conflicts as a "necessary evil."- Ana's top advice for teams looking to overhaul their process (Hint: It's not just about buying a tool).- The practical role AI is playing in their DevOps cycle today.About DevOps Diaries: Salesforce DevOps Advocate Jack McCurdy chats to members of the Salesforce community about their experience in the Salesforce ecosystem. Expect to hear and learn from inspirational stories of personal growth and business success, whilst discovering all the trials, tribulations, and joy that comes with delivering Salesforce for companies of all shapes and sizes. New episodes bi-weekly on YouTube as well as on your preferred podcast platform.Podcast produced and sponsored by Gearset. Learn more about Gearset: https://grst.co/4iCnas2Subscribe to Gearset's YouTube channel: https://grst.co/4cTAAxmLinkedIn: https://www.linkedin.com/company/gearsetX/Twitter: https://x.com/GearsetHQFacebook: https://www.facebook.com/gearsethqAbout Gearset: Gearset is the leading Salesforce DevOps platform, with powerful solutions for metadata and CPQ deployments, CI/CD, automated testing, sandbox seeding and backups. It helps Salesforce teams apply DevOps best practices to their development and release process, so they can rapidly and securely deliver higher-quality projects. Get full access to all of Gearset's features for free with a 30-day trial: https://grst.co/4iKysKWChapters:00:00 Welcome Ana Moreno, Salesforce Release Engineer at GitLab02:36 Ana's journey: The "Accidental Admin"03:30 From art history to tech09:33 Let's talk about art fraud!15:14 From Admin to Release Engineer22:35 What does a Release Engineer actually do all day?25:48 Inside GitLab's weekly Salesforce release cycle28:09 The challenge of managing 1,000+ Apex tests33:07 Taming the "necessary evil" of merge conflicts38:41 Key advice for teams overhauling their DevOps process46:12 The real-world future of AI in the DevOps pipeline50:57 Ana's Final Mantra

An airhacks.fm conversation with Gabriel Pop (@vwggolf3) about: transition from individual contributor to engineering management since 2011, managing developer tools and AWS code suite services, discussion of AWS CodeCommit entering maintenance mode but maintaining performance and security standards, benefits of AWS CodeBuild as a serverless build service, using CodeBuild for running JARs and automated testing, proper channels for submitting AWS feature requests through documentation and github repos, CodeArtifact as artifact repository for Java JARs and other packages, using S3 for serverless lambda deployment artifacts, multi-account architecture patterns for build systems, CodeDeploy flexibility for various deployment scenarios including ECS rolling updates, lifecycle hooks in CodeDeploy for Lambda deployments, Code Connections for secure third-party repository integration without storing secrets, CodePipeline as orchestrator for CI/CD workflows, CodePipeline V2 features with tag-based triggers for release automation, event-driven architecture using Amazon EventBridge with CodeBuild and CodePipeline events, comparison with GitHub Actions and Jenkins integrations, philosophy of using AWS-native services for consistency and security, Step Functions as alternative orchestration tool, importance of automation and infrastructure as code with CDK, challenges of prioritization and trade-offs in AWS service development, AWS region expansion and service availability, end-to-end testing strategies with Java interfaces and MicroProfile, security best practices with least privilege and dedicated build accounts, developer experience improvements and console UI updates, community engagement through AWS Hero program and user groups Gabriel Pop on twitter: @vwggolf3

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Driving Enterprise Innovation with AI and Strong CI/CD FoundationsAs enterprises push to deliver software faster and more efficiently, continuous integration and continuous delivery (CI/CD) pipelines have become central to modern engineering. With increasing complexity in builds, tools, and environments, the challenge is no longer just speed, but it's also about maintaining flow, consistency, and confidence in every release.In this episode of Tech Transformed, host Dana Gardner joins Arpad Kun, VP of Engineering and Infrastructure at Bitrise, to explore how solid CI/CD foundations can drive innovation and enable enterprises to harness AI in more practical, impactful ways. Drawing on findings from the Bitrise Mobile DevOps Insights Report, Kuhn shares how teams are optimising mobile delivery pipelines to accelerate development and support intelligent automation at scale.Complexity of Continuous Integration“Continuous integration pipelines are becoming more complex,” says Kuhn. “Build times are decreasing despite increasing complexity.” Faster compute and caching solutions are helping offset these pressures, but only when integrated into a cohesive CI/CD platform that can handle the rising demands of modern software delivery.A mature CI/CD environment creates stability and predictability. When developers trust their pipelines, they iterate faster and with less friction. As Kuhn notes, “A robust CI/CD platform reduces anxiety around releases.” Frequent, smaller iterations deliver faster feedback, shorten release cycles, and often improve app ratings—especially in the fast-paced world of mobile and cross-platform development.AI Ambitions with Engineering RealityIt's easy to become swept up in the potential of AI without considering whether existing foundations can support it. Many development environments are not yet equipped to handle the iterative, data-intensive nature of AI-powered software engineering. Without scalable CI/CD pipelines, teams risk encountering bottlenecks that can cancel out the potential benefits of AI.To truly drive innovation, enterprises must align their AI ambitions with robust automation, strong observability, and disciplined engineering practices. A well-designed CI/CD platform allows teams to integrate AI responsibly, accelerating testing, improving deployment accuracy, and maintaining agility even as complexity grows.TakeawaysContinuous integration pipelines are becoming more complex.Build times are decreasing despite increasing complexity.Faster computing and caching are key to improving delivery speed.Flaky tests have increased significantly, causing inefficiencies.Monitoring and isolating flaky tests can improve build success rates.Maintaining flow for engineers is crucial for productivity.A robust CI/CD platform reduces anxiety around releases.Frequent iterations lead to faster feedback and improved app ratings.Cross-platform development is on the rise, especially with React Native.The future of software development will be influenced by AI.For more insights, follow Bitrise:X: @bitriseInstagram: @bitrise.ioFacebook:

In part one of this Building Better Foundations interview, hosts Rob Broadhead and Michael Meloche talk with Greg Lind, founder of Buildly and OpenBuild, about bridging the gap in software development through AI, automation, and collaboration. Greg shares how modern teams can overcome silos, strengthen communication, and build transparency into their workflows — creating stronger, more adaptive foundations for success in today's fast-paced, AI-driven world. "We wanted to bring developers and product managers into one tool—so they could build together rather than as two separate teams." — Greg Lind About the Guest — Greg Lind Gregory Lind is an American software developer, author, and entrepreneur with over 20 years of experience in open-source innovation, software efficiency, and team transparency. He's the founder of Buildly in Brooklyn and co-founder of Humanitec in Berlin, helping organizations modernize systems through collaboration and automation. A frequent speaker at Open Gov and Open Source conferences, Greg advocates for open, scalable solutions and smarter software processes. His upcoming book, "Radical Therapy for Software Teams" (Apress, 2024), explores how transparency and AI can transform how teams build software. Bridging the Gap Between Teams and Tools Greg's journey toward bridging the gap started years ago while working with Humanitech in Berlin, where he saw firsthand how poorly connected processes caused frustration and inefficiency. Traditional Agile frameworks, while once revolutionary, began to buckle under the pressure of multi-repo, multi-cloud, and AI-driven development. "Agile started to break under the pressure—especially when we introduced AI-driven tools and CI/CD pipelines. The cycles just weren't fast enough." — Greg Lind To solve this, Buildly introduced a Rapid AI Development (RAD) process — a modern evolution of Agile that supports faster, release-based cycles rather than rigid sprints. It's an approach designed to keep pace with today's distributed teams and complex workflows. Bridging the Gap Through Automated Communication At the heart of Buildly's philosophy is a belief that communication shouldn't slow developers down — it should empower them. By integrating tools like Trello and GitHub, Buildly connects product and sprint backlogs into one transparent view. Developers' commits, issues, and updates automatically feed into team dashboards, reducing the need for endless meetings and manual updates. "You shouldn't have to explain what you did yesterday. Your commits already tell that story." — Greg Lind This approach allows teams to focus on outcomes rather than overhead — building trust, visibility, and true alignment across departments. It's automation as a bridge, not a barrier. Using AI to Bridge the Gap Between People and Process While Greg embraces AI's potential, he warns against depending on it too heavily. AI is great at identifying tasks and patterns, but humans still bring creativity, empathy, and strategic thinking to the table. "AI can tell you what's urgent, but it can't understand what's important." — Greg Lind In Greg's view, AI should be a co-pilot — helping teams filter information, automate repetitive work, and focus on higher-value decisions. By balancing automation with human insight, teams can bridge the gap between efficiency and innovation. Empowering Developers to Bridge the Gap Themselves Greg encourages developers not to wait for leadership to fix broken processes — but to take initiative. Automate your own workflows, visualize your backlog, and demonstrate how better systems can look in practice. "Even if you have to automate your own backlog—do it. Show your team what better looks like." — Greg Lind This proactive mindset transforms teams from reactive to adaptive, ensuring that everyone contributes to bridging the gap between communication, accountability, and delivery. Bridging the Gap Toward the Future of Development Greg Lind's insights remind us that bridging the gap in software development isn't about adopting the latest framework — it's about reconnecting people, process, and purpose. When teams share context, communicate openly, and use AI responsibly, they build stronger foundations for innovation. As this episode shows, the future of software isn't about faster code — it's about better collaboration. And bridging the gap is where that future begins. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Useful WordPress SEO Plugins Product Catalog: A Deeper Dive Into Customizing WordPress Plugins Manage WordPress Plugins Building Better Foundations Podcast Videos – With Bonus Content

Don't get stuck using AI to build faster horses. Instead, find the opportunities and rethink your software delivery processes! That, and only that, will help you increase Developer Experience and Efficiency!This episode is all about how to measure and improve DevEx in the age of Artificial Intelligence. And with Laura Tacho, CTO at DX, we think we found a perfect guest!Laura has been working in the dev tooling space for the past 15 years. In her current role at DX she is working on the evolution of DORA and SPACE into DX Core 4 and the DXI Measurement Framework.In our episode we learn about those frameworks but also how tech leaders need to rethink where and how to apply AI to improve overall efficiency, quality and effectiveness! The key takeaways from this conversation areDevEx is all about the identifying and reducing friction in the end-2-end development processTech Leaders need to become better in articulating technical change requirements to businessAs of today only 22% of code in git is really AI generated. Don't get fooled into believing AI is already betterBack to Basics makes companies successful with AI. That is: proper CI/CD, testing, documentation, observability!Here the links we discussedLaura's LinkedIn: https://www.linkedin.com/in/lauratacho/DX: https://getdx.com/Cloud Native Days Austria Talk: https://www.youtube.com/watch?v=kZ1F0-XS1l4Engineering Leadership Community: https://www.engineeringleaders.io/

In this comprehensive episode, Luka Mustafa, founder and CEO of Irnas Product Development, provides an in-depth exploration of Zephyr RTOS and its transformative impact on embedded development. We dive deep into how Zephyr's Linux Foundation-backed ecosystem enables hardware-agnostic development, dramatically reducing the time spent on foundational code versus business-value features. Luka shares practical insights from five years of specializing in Zephyr development, demonstrating how projects can achieve remarkable portability - including running the same Bluetooth code on different chip architectures in just an hour, and even executing embedded applications natively on Linux for development purposes.The discussion covers Zephyr's comprehensive testing framework (Twister), CI/CD integration capabilities, and the cultural shift required when moving from traditional bare-metal development to this modern RTOS approach. We explore real-world applications from low-power IoT devices consuming just 5 microamps to complex multi-core systems, while addressing the learning curve challenges and when Zephyr might not be the right choice. This episode is essential listening for embedded teams considering modernizing their development practices and leveraging community-driven software ecosystems.Key Topics[03:15] Zephyr RTOS fundamentals and Linux Foundation ecosystem benefits[08:30] Hardware abstraction and device tree implementation for portable embedded code[12:45] Nordic Semiconductor strategic partnership and silicon vendor support landscape[18:20] Native POSIX development capabilities and cross-platform debugging strategies[25:10] Learning curve challenges: EE vs CS background adaptation to Zephyr development[32:40] Resource requirements and low-power implementation on constrained microcontrollers[38:15] Multi-vendor chip support: STMicroelectronics, NXP, and industry adoption trends[42:30] Safety-critical applications and ongoing certification processes[45:50] Organizational transformation strategies and cultural adaptation challenges[52:20] Zbus inter-process communication and modular development architecture[58:45] Twister testing framework and comprehensive CI/CD pipeline integration[65:30] Sample-driven development methodology and long-lived characterization tests[72:15] Production testing automation and shell interface utilization[78:40] Model-based development integration and requirements traceability[82:10] When not to use Zephyr: Arduino simplicity vs RTOS complexity trade-offsNotable Quotes"With Zephyr, porting a Bluetooth project from one chip architecture to another took an hour for an intern, compared to what would traditionally be months of effort." — Luka Mustafa"How many times have you written a logging subsystem? If the answer is more than zero, then it shouldn't be the case. Someone needs to write it once, and every three years someone needs to rewrite it with a better idea." — Luka Mustafa"The real benefit comes from doing things the Zephyr way in Zephyr, because then you are adopting all of the best practices of developing the code, using all of the subsystems to the maximum extent." — Luka Mustafa"You want to make sure your team is spending time on things that make money for you, not on writing logging, for example." — Luka MustafaZephyr Project - Linux Foundation-backed RTOS project providing comprehensive embedded development ecosystemTwister Testing Framework - Zephyr's built-in testing framework for unit tests, hardware-in-the-loop, and CI/CD integrationZbus Inter-Process Communication - Advanced event bus system for modular embedded development and component decouplingiirnas - Open-source examples of Zephyr best practices and CI/CD pipeline implementationsCarles Cufi's Talk - Detailed presentation on Nordic's strategic decision to support Zephyr RTOS You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click hereAre you looking for embedded-focused trainings? Head to https://agileembedded.academy/Ryan Torvik and Luca have started the Embedded AI podcast, check it out at https://embeddedaipodcast.com/

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

This week's guests are Ani and Henry, co-founders of Smithery. Smithery is building the marketplace and runtime for MCP, making it easier for developers to distribute, discover, and monetize tools in the emerging agent ecosystem.  Smithery provides a platform to connect your repo, integrate with CI/CD, and handle hosting for servers seamlessly. MCP shines when agents become more general, but it only scales if demand grows for more connections between tools and systems. Drawing from their experiences at Browserbase, Whatnot, and prior AI startups, Ani and Henry saw the need for standardization across the agent stack and set out to build the distribution and trust layer for MCP. We cover what early traction they're seeing from developers, how they're approaching payments and identity to reduce configuration friction, and what the broader shift toward open, composable AI infrastructure means for the future of agents. Episode chapters: 1:51 — Getting into AI 5:30 — The Origin of Smithery 7:40 — Building the Supply Side 9:10 — Why Smithery Is the Easiest Way to Discover MCPs 13:30 — Agent Authentication and Identity 17:08 — The Most Popular MCPs 19:50 — MCP and the Principle of Separation of Concerns 22:50 — How AI Is Being Used Today 25:57 — Defining Success as Founders 31:45 — Quire Fire RoundThis episode is brought to you by Grata, the world's leading deal sourcing platform. Our AI-powered search, investment-grade data, and intuitive workflows give you the edge needed to find and win deals in your industry. Visit grata.com to schedule a demo today.Fresh out of Y Combinator's Summer batch, Overlap is an AI-driven app that uses LLMs to curate the best moments from podcast episodes. Imagine having a smart assistant who reads through every podcast transcript, finds the best parts or parts most relevant to your search, and strings them together to form a new curated stream of content - that is what Overlap does. Podcasts are an exponentially growing source of unique information. Make use of it! Check out Overlap 2.0 on the App Store today.

"Data loss" is a phrase that strikes fear into the heart of every Salesforce professional. But what if you could face a data incident with calm and confidence?Jack speaks with Aga Peryie, Senior Product Manager at Gearset, about building a solid data management strategy. They discuss the vital role of understanding customer needs, the challenges of data backup, and why so many teams are vulnerable to simple user errors.This conversation is a masterclass in shifting from anxiety to control.Tune in to learn:- Why most teams are unprepared for the most common cause of data loss: user error.- The key to reducing anxiety: regularly testing your recovery process before you need it.- Practical strategies for archiving data to manage Salesforce storage limits effectively.- How to build a backup solution truly tailored to the complexities of Salesforce.- Why a "set it and forget it" backup plan is a recipe for disaster.About DevOps Diaries: Salesforce DevOps Advocate Jack McCurdy chats to members of the Salesforce community about their experience in the Salesforce ecosystem. Expect to hear and learn from inspirational stories of personal growth and business success, whilst discovering all the trials, tribulations, and joy that comes with delivering Salesforce for companies of all shapes and sizes. New episodes bi-weekly on YouTube as well as on your preferred podcast platform.Podcast produced and sponsored by Gearset. Learn more about Gearset: https://grst.co/4iCnas2Subscribe to Gearset's YouTube channel: https://grst.co/4cTAAxmLinkedIn: https://www.linkedin.com/company/gearsetX/Twitter: https://x.com/GearsetHQFacebook: https://www.facebook.com/gearsethqAbout Gearset: Gearset is the leading Salesforce DevOps platform, with powerful solutions for metadata and CPQ deployments, CI/CD, automated testing, sandbox seeding and backups. It helps Salesforce teams apply DevOps best practices to their development and release process, so they can rapidly and securely deliver higher-quality projects. Get full access to all of Gearset's features for free with a 30-day trial: https://grst.co/4iKysKWChapters:00:00 Introduction to Product Management at Gearset02:52 The Importance of Customer-Centric Product Management05:15 Understanding Customer Needs and Asking 'Why'08:00 Data Backup Solutions: Common Practices and Misconceptions10:54 Assessing the Importance of Data and Trust13:35 Identifying Data Loss and Recovery Strategies16:16 Best Practices for Data Restoration19:09 Archiving Strategies for Salesforce Data21:47 The Role of Data in AI and Customer Experience24:39 The Benefits of Backup and Archiving Solutions27:28 Creating a Culture of Data Awareness29:58 Final Thoughts on Data Backup and Recovery

Send us a textQuantum threats aren't waiting politely on the horizon, and neither should we. We kick off with Signal's bold move to deploy post-quantum encryption, unpacking the “belt and suspenders” approach that blends classical cryptography with quantum-resistant algorithms. No jargon traps—just clear takeaways on why this matters for privacy, resilience, and the pressure it puts on other messaging platforms to evolve. We point you to smart reads from Ars Technica and Bruce Schneier that make the technical guts approachable and actionable.From there, we switch gears into a focused CISSP Domain 8 walkthrough: how to weave security into every phase of the software development lifecycle. We talk practical integration across waterfall, agile, and DevOps; show why change management, continuous monitoring, and application-aware incident response are non-negotiable; and explain how maturity models like CMMI and BSIMM help teams move from reactive to repeatable. We also break down the developer's toolbox—secure language choices, vetted libraries with SCA, hardened runtimes, and IDE plugins that surface issues in real time—so teams can ship faster without trading away safety.Speed meets rigor in the CI/CD pipeline, where shift-left security comes alive with SAST, DAST, and SOAR-driven checks. We cover repository hygiene, secret scanning, and how to measure effectiveness with audit trails and risk analysis that map code issues to business impact. You'll get a clear view of third-party risk across COTS and open source, the shared responsibility model for SaaS, PaaS, and IaaS, and the daily practices that keep APIs from leaking data: least privilege, strict authorization, input validation, and rate limiting. We close with software-defined security—policies as code—bringing consistency, versioning, and automation to your defenses. Subscribe, share with a teammate who owns your pipeline, and leave a review to tell us the next Domain 8 topic you want us to deep-dive.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Organizations pour millions into protecting running applications—yet attackers are targeting the delivery path itself.This episode of AppSec Contradictions reveals why CI/CD and cloud pipelines are becoming the new frontline in cybersecurity.

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Microsoft MVP Hailey Phillips joins The PowerShell Podcast to share her journey from systems engineer to automation innovator. She talks about IntuneStack, her new PowerShell-driven CI/CD project for Intune environments, and how it bridges the gap between systems engineering and DevOps. Hailey also reflects on her path to becoming an MVP, her experiences at MMS, and the importance of mentorship, collaboration, and authenticity in the tech community.   Key Takeaways: Bridging systems and DevOps – Hailey's IntuneStack helps IT pros apply DevOps principles like CI/CD and Infrastructure as Code to Intune environments. Automate and empower – True success in automation means enabling your team, not bottlenecking them. Collaboration beats perfectionism. Community and authenticity – Sharing knowledge, mentoring others, and showing up as your true self create lasting impact in the PowerShell ecosystem. Guest Bio: Hailey Phillips is a Systems Engineer, Microsoft MVP, and Professional Pokémon Trainer. She specializes in automation, endpoint management, and modern workplace strategy, bridging the gap between traditional IT and DevOps. Hailey's work focuses on building pragmatic, scalable solutions using tools like PowerShell, Microsoft Graph, Intune, and Azure Arc. When she's not deep in tech, you'll probably find her skiing in the Cascades, lifting heavy things, or at a metalcore show with a strong cup of coffee in hand.   Resource Links: Intune Stack Project – https://github.com/AllwaysHyPe/IntuneStack Hailey's Website – https://www.allwayshype.com/ Hailey on BlueSky – https://bsky.app/profile/allwayshype.com Hailey on GitHub – https://github.com/AllwaysHyPe Hailey's "Rage Coding" Spotify Playlist: https://open.spotify.com/playlist/692CBjUNRBnSzSsRncQJkn?si=9d8bf7e625104ce8 PowerShell Wednesdays – https://www.youtube.com/watch?v=2-d16gi3VEc&list=PL1mL90yFExsix-L0havb8SbZXoYRPol0B&pp=gAQB PDQ Discord – https://discord.gg/PDQ The PowerShell Podcast on YouTube: https://youtu.be/1YefrFekEJ

Kieron Allen speaks with Chris Pope, Chief Product Officer at AutomatePro, in an in-depth discussion that is part of a broader series of podcasts, articles, and reports on ServiceNow's evolving ecosystem. They explore how intelligent automation and agentic AI are reshaping DevOps and quality assurance. The conversation also highlights how AutomatePro's built-on approach enhances developer productivity, reduces risk, and ensures security, all within the ServiceNow environment.AutomatePro's AI EdgeThe Big ThemesAutomatePro's Core Mission: AutomatePro focuses on solving one of the most time-consuming parts of software delivery: testing and documentation. Pope explains that their goal isn't to replace humans but to augment their efforts through intelligent automation. By embedding deeply within the ServiceNow platform, AutomatePro allows developers and platform owners to automate repetitive tasks early in the development cycle, ensuring higher-quality releases and faster deployment.Human-AI Collaboration Wins: The myth of AI replacing people is outdated. Pope reframes the conversation: it's not about replacement, it's about enablement. The real winners will be those who know how to use AI effectively. Today's Copilots are context-aware, learning from human behavior and adapting to different personas — whether it's a developer, analyst, or HR owner. Prompt engineering is emerging as a vital skill, and the better the prompt, the better the AI-driven output.DevOps Innovation Without Compromise: AutomatePro and ServiceNow are reshaping DevOps by making speed and quality compatible. Historically, faster releases meant riskier ones. With AutomatePro's intelligent testing automation, that tradeoff no longer exists. Frequent, smaller releases — the “fixed forward” model — are now safer thanks to early automation, embedded security, and contextual AI. Pope argues that platform owners and developers are the new heroes in enterprise IT, and equipping them with Copilots, intelligent workflows, and instant feedback loops unlocks untapped value.The Big Quote: "You're not going to be replaced by AI per se, you're going to be replaced by someone that knows how to use AI effectively."More from ServiceNow and AutomatePro:Follow AutomatePro on LinkedIn or learn more about ServiceNow and intelligent automation. Visit Cloud Wars for more.

Animesh Koratana - CEO and Founder of PlayerZero discusses how agentic AI is transforming software quality assurance through predictive code simulation, and how teams can shift from reactive debugging to proactive problem prevention in the era of AI-generated code.SHOW: 967SHOW TRANSCRIPT: The Cloudcast #967 TranscriptSHOW VIDEO: https://youtube.com/@TheCloudcastNET CLOUD NEWS OF THE WEEK: http://bit.ly/cloudcast-cnotwNEW TO CLOUD? CHECK OUT OUR OTHER PODCAST: "CLOUDCAST BASICS"SPONSORS:[Interconnected] Interconnected is a new series from Equinix diving into the infrastructure that keeps our digital world running. With expert guests and real-world insights, we explore the systems driving AI, automation, quantum, and more. Just search “Interconnected by Equinix”.[TestKube] TestKube is Kubernetes-native testing platform, orchestrating all your test tools, environments, and pipelines into scalable workflows empowering Continuous Testing. Check it out at TestKube.io/cloudcastSHOW NOTES:PlayerZero websiteTopic 1 - Welcome to the show Animesh. Tell us about your background and your involvement in.Topic 2 - Let's start with the core problem you're solving. What is "predictive software quality" and why is this becoming critical now, especially in the era of AI-generated code?Topic 3 - How does agentic code simulation work, and what makes it different from traditional testing approaches?Topic 4 - This feels like it democratizes software quality beyond just engineering teams. How does PlayerZero work across different roles - developers, QA, product managers, and support teams?Topic 5 - Integration and workflow - how does PlayerZero fit into existing CI/CD pipelines and development workflows? What does the implementation look likeTopic 6 - Let's talk about scale and complexity. How does PlayerZero handle large, distributed systems with microservices, databases, and complex architecturesTopic 7 - If someone out there is interested and wants to get started, what is the best place to started?FEEDBACK?Email: show at the cloudcast dot netBluesky: @cloudcastpod.bsky.socialTwitter/X: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

What's the most overlooked element in a successful DevOps strategy? According to Salesforce Architect and community leader Raksha Sanganee, it's culture.In this powerful episode of DevOps Diaries, Jack McCurdy sits down with Raksha to uncover her remarkable journey from a school finance officer to a respected DevOps consultant. She shares the invaluable lessons learned while training over 300 people in Salesforce for free and unpacks her core principles for transforming a team's software delivery lifecycle.Tune in to learn why "seeing is believing" is the key to overcoming client skepticism, how to build unbreakable trust, and why you should never, ever forget your backups!About DevOps Diaries: Salesforce DevOps Advocate Jack McCurdy chats to members of the Salesforce community about their experience in the Salesforce ecosystem. Expect to hear and learn from inspirational stories of personal growth and business success, whilst discovering all the trials, tribulations, and joy that comes with delivering Salesforce for companies of all shapes and sizes. New episodes bi-weekly on YouTube as well as on your preferred podcast platform.Podcast produced and sponsored by Gearset. Learn more about Gearset: https://grst.co/4iCnas2Subscribe to Gearset's YouTube channel: https://grst.co/4cTAAxmLinkedIn: https://www.linkedin.com/company/gearsetX/Twitter: https://x.com/GearsetHQFacebook: https://www.facebook.com/gearsethqAbout Gearset: Gearset is the leading Salesforce DevOps platform, with powerful solutions for metadata and CPQ deployments, CI/CD, automated testing, sandbox seeding and backups. It helps Salesforce teams apply DevOps best practices to their development and release process, so they can rapidly and securely deliver higher-quality projects. Get full access to all of Gearset's features for free with a 30-day trial: https://grst.co/4iKysKWChapters:00:00 Introduction to Raksha Her Journey04:23 Transitioning to Salesforce and Community Impact09:13 Understanding DevOps: Culture and Trust13:41 Common Mistakes in DevOps and Importance of Automation18:24 Building Trust with Clients and Overcoming Skepticism23:02 The Role of Training and Demos in DevOps27:29 Data Strategy and Best Practices in Salesforce32:00 The Importance of Community and Continuous Learning36:31 Parting Wisdom and Final Thoughts

Rick Doten, cybersecurity startup advisor and AI researcher, joins the show to unpack how AI-assisted development is reshaping software—and what it means for security. From startups rushing to ship faster code to the unseen risks of “vibe coding,” Rick explains how engineering teams can balance innovation with secure, resilient design.If your dev team is using AI tools to boost velocity, this conversation might change how you think about your SDLC, code review, and even your threat model.Key Takeaways• AI-assisted coding speeds up output but can multiply security risks if context isn't baked in.• Startups often trade speed for security early on—and that can be expensive to unwind later.• Traditional fundamentals like OWASP and BSIMM still apply, even as architectures evolve with agents and MCP.• AI creates a widening gap between companies that can secure their models and those that can't.• “Vibe coding”—non-devs using AI to build—introduces a new wave of shadow code leaders must prepare for.Timestamped Highlights[02:09] The real range of how startups are using AI-assisted tools—and why security is often an afterthought.[05:12] Why AI-generated code is not just another form of third-party code.[09:40] The hidden risk: code volume grows faster than your ability to secure it.[15:51] How AI is widening the gap between resource-rich enterprises and everyone else.[18:25] The new fragility of systems—where architecture and resilience start to break.[22:07] Rethinking SDLC: integrating AI tools without losing security fundamentals.[25:29] “Vibe coding” and what happens when non-engineers start shipping code.Memorable Insight“AI isn't lazy like humans—it doesn't just fix one thing. It rewrites everything. That's why every line has to be re-scrutinized.”Pro TipsIf your startup doesn't have a dedicated security function yet, start with the basics: integrate OWASP checks into your CI/CD, use non-human accounts correctly, and automate code review gates early. Don't wait until production to harden your systems.Call to ActionIf this episode sparked ideas for your dev or security team, share it with someone who's experimenting with AI-assisted tools. Follow The Tech Trek for more conversations at the intersection of engineering, AI, and leadership.

Bret is joined by Philip Andrews and Dan Muret of Cast AI to discuss pod live migration between nodes in a Kubernetes cluster.

Neste episódio do Cabeça de Lab, mergulhamos no universo da Qualidade de Software (QA) com um foco especial nos Testes Regressivos, a "rede de segurança" que garante que nenhuma nova funcionalidade quebre aquilo que já estava funcionando perfeitamente. Discutimos a importância fundamental desses testes, diferenciando-os dos testes unitários e de integração, e exploramos os principais desafios de sua implementação e manutenção.Além disso, abordamos o equilíbrio ideal entre testes manuais e automação, como essa prática se alinha à agilidade e à velocidade de entrega de produtos, e a necessidade de uma cultura de qualidade compartilhada por desenvolvedores, QAs e times de produto. Por fim, trouxemos dicas de ferramentas, boas práticas como "começar pequeno" e a tendência da integração de CI/CD, Feature Flags e Inteligência Artificial no futuro dos testes.Edição completa por Rádiofobia Podcast e Multimídia: ⁠⁠https://radiofobia.com.br/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠---Nos siga no Twitter e no Instagram: @luizalabs @cabecadelabDúvidas, cabeçadas e sugestões, mande e-mail para o cabecadelab@luizalabs.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ou uma DM no InstagramParticipantes: ICARO BELMIRO | https://www.linkedin.com/in/icarobelmiro/MARCIANO CADORE | https://www.linkedin.com/in/marciano-cadore-a615b125/VICTORIA GABRIELLA | https://www.linkedin.com/in/victoria-gabriella-91392a1b2/ANA CAROLINA FONSECA BARRETO | https://www.linkedin.com/in/anacarolinafonsecabarreto/

Peter Ritchie is a veteran software architect and consultant with over 35 years of experience in the tech industry. Peter is renowned for his deep expertise in .NET development, distributed systems, and agile methodologies. He's an accomplished author of several technical books, a former Microsoft MVP, and a sought-after international speaker. Peter is also actively involved in the .NET community and was a candidate for the .NET Foundation Board of Directors, reflecting his commitment to open-source and developer advocacy. Through his consulting work, he helps teams elevate their architecture, code quality, and development practices — especially in areas like ASP.NET, Clean Architecture, and CI/CD pipelines.   Topics of Discussion: [3:45] Overview of .NET Foundation. [5:33] Support for User Groups and .NET 10. [5:48] The upcoming release of .NET 10 and Visual Studio 2026. [6:39] Stability and backward compatibility. [9:10] Challenges and approaches to business logic. [11:24] Repository structure and team organization. [15:27] Testing and continuous integration. [17:12] The role of experienced developers in mentoring and reviewing the work of junior developers. [20:02] Jeffrey mentions a recent blog post of Peter's and how we can define clear user stories, including roles, actions, criteria, and benefits, to ensure developers understand the requirements. [24:15] The importance of context in AI-driven development and how it applies to working with people. [25:06] How the AI revolution can lead to better understanding and communication within development teams.   Mentioned in this Episode: Clear Measure Way Architect Forum Software Engineer Forum Peter Ritchie LinkedIn     Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.  

Scaling CI/CD for mobile apps is hard. Faster test runs often lead to more tests, more infrastructure, and more complexity. So how do you keep your pipelines healthy and reliable while still shipping at speed? In this episode, we sit down with Anton Malinski of Marathon Labs to explore the real-world lessons he's learned building and optimizing mobile CI/CD pipelines. You'll discover: How to scale mobile test automation without introducing friction What “healthy CI growth” looks like in practice Why real devices still matter, even with a massive emulator fleet How backend mocking and dedicated mobile API gateways transform shift-left testing Practical advice for teams evolving from weekly releases to on-every-commit confidence Whether you're a QA leader, automation engineer, or DevOps practitioner, this conversation gives you the insights and metrics you need to take your mobile testing pipelines to the next level.

In this episode of the IoT For All Podcast, Gaurav Johri, co-founder and CEO of Doppelio, joins Ryan Chacon to discuss software validation and testing in IoT. The conversation covers the vital role of virtualization, the increasing complexity and distributed nature of connected products, the benefits of combining physical and virtual testing labs, the pitfalls of simulator-based approaches, intelligent automation in DevOps, the ROI of early validation, and future trends in AI, edge computing, and 5G.Gaurav Johri brings a wealth of expertise with over 25 years in steering multinational enterprises through the digital age. He has held global leadership positions at Mindtree, Onmobile, and Infosys. Johri's vision and passion for a future built on connected products shaped Doppelio as a pioneer in IoT testing. He is also a regular speaker at connected world events, such as AutomotiveIQ and IoT Tech Expo.Doppelio is a leading IoT test automation platform that enables enterprises to rapidly test connected products through advanced device virtualization at scale. Their solution creates "Doppels" (data twins) across diverse protocols, eliminating physical device dependency while enabling seamless co-existence of physical and virtual testing labs. They support comprehensive testing from simple sensors to complex industrial equipment, delivering 10x faster testing speeds, 80-90% coverage, and millions in operational savings. Trusted by Fortune 500 companies across connected elevators, medical devices, automotive, and security industries, Doppelio accelerates time-to-market while reducing field failure risks through intelligent automation.Discover more about IoT at https://www.iotforall.comFind IoT solutions: https://marketplace.iotforall.comMore about Doppelio: https://doppelio.comConnect with Gaurav: https://www.linkedin.com/in/gaurav-johri/(00:00) Intro(00:21) Gaurav Johri and Doppelio(00:56) IoT testing and its importance(03:56) Virtualization in IoT testing(06:10) Real-world examples of IoT testing(08:32) Physical vs. virtual testing labs(10:22) Limitations of simulator-based approaches(12:25) How do you enable rapid, scalable validation?(14:12) Role of intelligent automation in DevOps and CI/CD(15:43) The ROI of performing early software validation(17:35) Advice for modernizing IoT testing(19:26) Future of IoT testing with AI, edge, 5G(20:52) Learn more and follow upSubscribe to the Channel: https://bit.ly/2NlcEwmJoin Our Newsletter: https://newsletter.iotforall.comFollow Us on Social: https://linktr.ee/iot4all