Podcasts about low code

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

The following article of the AI Cloud & Data industry is: “AI and Low Code: The Future of Automation in Mexico” by Miguel Gonzalez Serrano, Area Vice President EMEA South, LATAM and Middle Eas, Appian.

Buy & Build gehört seit Jahren zum Standardrepertoire europäischer Finanzinvestoren, aber zwischen dem Zusammenkaufen von Unternehmen und dem echten Aufbau von Marktführern liegen Welten. Die meisten Investoren sprechen von Integration, tatsächlich gelebt wird sie aber selten konsequent genug, um dauerhaften Wettbewerbsvorteil zu schaffen. Und in einer Zeit, in der KI schon im Gartenbau Ausschreibungsprozesse verändert, stellt sich die Frage: Wer hat das Rüstzeug für Buy & Build 3.0?Mein Gast ist Eric Blumenthal, Managing Partner und Vorstand bei AURELIUS Growth. Mit ihm spreche ich über zehn Jahre Aufbauarbeit mit fast 100 Transaktionen, warum AURELIUS Growth bewusst gewerblich statt vermögensverwaltend agiert, wie echte Integration im Mittelstand funktioniert und was Low-Code und KI für Portfoliounternehmen in klassischen Branchen bedeuten.Wir beleuchten in dieser Episode:warum Eric kein Ingenieur blieb,wie AURELIUS Growth aufgestellt ist,welche Rolle echte Integration im Buy & Build spielt,was Low-Code und KI für traditionelle Branchen bedeutet,warum Unternehmerfamilien statt Fonds das Kapital stellen,und vieles mehr...Viel Spaß beim Hören!***Timestamps(00:00:00) Intro(00:01:45) Begrüßung & Werdegang(00:05:23) Stationen vor Aurelius(00:08:52) Timing des MBA(00:11:52) Buy & Build: Konzern vs. Investor(00:13:14) Fehler & Rückschläge(00:16:00) AURELIUS Anfangsjahre & Carve-out-DNA(00:20:14) Gründung AURELIUS Growth(00:23:48) Investitionsstrategie & Kriterien(00:26:22) Outbound-Strategie & Vertikalhypothesen(00:28:39) Wettbewerbsumfeld & Sektorfokus(00:32:47) Operativer Ansatz & Hands-on(00:37:38) Rückbeteiligung & Unternehmerbindung(00:39:57) Investorenbasis & Evergreen-Struktur(00:45:48) Wachstum & Skalierung des Teams(00:49:09) Internationalisierung(00:54:28) Integration konkret: Gartenbau & KI(00:57:26) Software-LBOs & Low-Code(01:00:43) KI-Demokratisierung & Mittelstand(01:11:12) Zukunft von Buy & Build***Alle Links zur Folge:Kai Hesselmann auf LinkedIn: https://www.linkedin.com/in/kai-hesselmann-dealcircle/CLOSE THE DEAL auf LinkedIn: https://www.linkedin.com/company/closethedeal-podcastEric Blumenthal auf LinkedIn: https://www.linkedin.com/in/eric-blumenthal-126670/AURELIUS Growth auf LinkedIn: https://www.linkedin.com/company/aureliusgrowth/Folge 68 mit Dirk Markus: https://dealcircle.com/ClosetheDeal/episoden/68-aurelius-dirk-markus/Website CLOSE THE DEAL: https://dealcircle.com/ClosetheDeal/***DUB.de und AMBER sind die Plattformen für sichere Unternehmensnachfolgen. Schaut vorbei, wenn ihr euer Unternehmen schnell, sicher und kostenfrei zum Verkauf inserieren wollt oder als Käufer auf der Suche nach passenden Deals seid:www.dub.dewww.amber.deals***Du bist M&A-Berater im Small- oder Midcap-Segment und suchst einen Überblick über alle relevanten Deals? Jetzt schnell den

„Mit wem verbringe ich meine Lebenszeit?“ – diese Frage zieht sich wie ein roter Faden durch diese Episode mit Hamarz Mehmanesh, Gründer und CEO von mgm technology partners. Franz Kubbillum spricht mit ihm über 30 Jahre Enterprise-Softwareentwicklung – von langlebigen Geschäftsanwendungen über das ELSTER Online-Portal bis zum Warenflussmanagement bei Lidl. Im Mittelpunkt stehen die Low-Code-Plattform A12, die Kunst, Software für 20–30 Jahre wartbar zu bauen, und die Frage, wie KI künftig tief in Fachanwendungen integriert wird – warum das für den deutschen Mittelstand eine enorme Chance bedeutet. Mehmanesh erzählt, wie er vom Philosophie- und Psychologiestudenten und Freiberufler zum Unternehmer wurde, der heute mit über 1.000 Mitarbeitenden an 19 Standorten komplexe Systeme entwickelt. Er beschreibt, was für ihn unternehmerisches Denken ausmacht: eine schonungslose Lagebeurteilung, Beharrlichkeit statt Ausreden –warum er seinen Alltag bewusst um Routinen, Sport und gute Gespräche mit Kolleg:innen strukturiert. Weitere Fragen, die Mehmanesh in dieser Episode beantwortet, sind: - Wie entwickelt und betreibt man Enterprise-Anwendungen, die Jahrzehnte überdauern – technisch, organisatorisch und kulturell? - Was unterscheidet die A12-Plattform von klassischen Low-Code-Ansätzen, und wie entkoppelt sie Fachlichkeit von Technik? - Wie verändert KI („AI eats Software“) die Art, wie Software entsteht und welche Rolle spielen dabei AI-Agents in Fachanwendungen? - Wodurch unterscheidet sich ein unternehmerisches Mindset von „Konzernmentalität“, und welche Rolle spielt dabei die Frage, mit wem man seine Zeit verbringt? Themen: - C-level - Softwareentwicklung - Low Code Anwendungen - KI ----- Über Atreus – A Heidrick & Struggles Company Atreus garantiert die perfekte Interim-Ressource (m/w/d) für Missionen, die nur eine einzige Option erlauben: nachhaltigen Erfolg! Unser globales Netzwerk aus erfahrenen Managern auf Zeit zählt weltweit zu den besten. In engem Schulterschluss mit den Atreus Direktoren setzen unsere Interim Manager vor Ort Kräfte frei, die Ihr Unternehmen zukunftssicher auf das nächste Level katapultieren. ▶️ Besuchen Sie unsere Website: https://www.atreus.de/ ▶️ Interim Management: https://www.atreus.de/kompetenzen/service/interim-management/ ▶️ Für Interim Manager: https://www.atreus.de/interim-manager/ ▶️ LinkedIn-Profil von Hamarz Mehmanesh: https://www.linkedin.com/in/hamarz-mehmanesh-34490ba/ ▶️ Profil von Franz Kubbillum: https://www.atreus.de/team/franz-kubbillum/

Até onde o low-code realmente pode chegar em sistemas reais?Neste episódio, falamos sobre como o Bubble e ferramentas similares vão além de MVPs, atuando como complemento a sistemas existentes, integrando com APIs — inclusive fiscais — e acelerando entregas com uma arquitetura bem definida.Uma conversa prática sobre aplicação responsável de low-code, combinando automação com n8n e backends modernos como Supabase e Xano.Ouça agora e transforme sua forma de programar com ACBr!Convidados: Marcus Ribeiro é empreendedor tech e cofundador da Ison. Atua há mais de 10 anos com desenvolvimento de soluções empresariais, hoje focado na construção de Módulos sob demanda, automações e integrações — principalmente conectando sistemas com APIs e estruturas fiscais, usando uma abordagem híbrida entre low-code e desenvolvimento tradicional.

Наш постоянный зритель Николай Моряков покажет работу с параллельными агентами.Спасибо всем, кто нас слушает. Ждем Ваши комментарии.Музыка из выпуска: - https://artists.landr.com/056870627229- https://t.me/angry_programmer_screamsВесь плейлист курса "Kubernetes для DotNet разработчиков": https://www.youtube.com/playlist?list=PLbxr_aGL4q3SrrmOzzdBBsdeQ0YVR3Fc7Бесплатный открытый курс "Rust для DotNet разработчиков": https://www.youtube.com/playlist?list=PLbxr_aGL4q3S2iE00WFPNTzKAARURZW1ZShownotes: 00:00:00 Вступление00:10:20 Работа с параллельными агентами00:20:00 Что делать с подагентами?00:32:00 А нужен ли человек?00:47:00 Low Code vs Claude01:01:00 Подстраиваемся под агентов01:13:00 Смотреть в код или не смотреть?Ссылки:- https://github.com/SourceSurfer/BookLibrary : Созданный проект Видео: https://youtube.com/live/WrOlHt5SDT8 Слушайте все выпуски: https://dotnetmore.mave.digitalYouTube: https://www.youtube.com/playlist?list=PLbxr_aGL4q3R6kfpa7Q8biS11T56cNMf5Twitch: https://www.twitch.tv/dotnetmoreОбсуждайте:- Telegram: https://t.me/dotnetmore_chatСледите за новостями:– Twitter: https://twitter.com/dotnetmore– Telegram channel: https://t.me/dotnetmoreCopyright: https://creativecommons.org/licenses/by-sa/4.0/

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM This episode explores how AI, agents, and prompting are reshaping how software and business solutions are built. Mark Smith and Keith Atherton discuss the shift beyond traditional low-code towards natural language, agent-driven development, where context, outcomes, and governance matter more than interfaces. They examine why developer fundamentals still matter, how generative AI accelerates delivery, and what new makers should focus on as Microsoft investment, tooling, and certifications pivot towards agentic and AI-first approaches. 

In dieser Episode spreche ich mit Ayelt Komus, Professor, Hochschule Koblenz (Koblenz University of Applied Sciences).Wir sprechen über folgende Themen:Warum tun sich Unternehmen noch immer schwer mit der Zusammenarbeit von IT und Fachbereichen?Was bedeutet Business-IT-Fusion konkret für Unternehmen?Warum gewinnt das Thema Business-IT-Fusion gerade jetzt so stark an Bedeutung?Wie verändern GenAI, Low-Code und No-Code die Zusammenarbeit zwischen Business und IT?Woran erkennt man, dass IT und Business in einem Unternehmen nicht wirklich gut zusammenarbeiten?Welche Fähigkeiten müssen Fachbereiche aufbauen, um stärker an digitalen Lösungen mitzuarbeiten?Wie verändert sich die Rolle der IT-Abteilung in einer Welt mit GenAI und Vibe Coding?Welche Aufgaben sollten Fachbereiche selbst übernehmen – und wo muss die IT zwingend eingebunden sein?Wie sieht eine ideale Zusammenarbeit zwischen IT und Business in der Praxis aus?Was machen erfolgreiche CIOs anders, wenn sie Business und IT besser zusammenbringen wollen?Erhalte jede Woche aktuelle Strategien in dein E-Mail Postfach: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.stateofprocessautomation.com/⁠⁠Podcast-Moderator: Christoph Pacher⁠LinkedIn⁠Interviewgast: Ayelt Komus, Professor, Hochschule Koblenz (Koblenz University of Applied Sciences)⁠LinkedIn

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVMThis episode explores how AI coding agents are reshaping how software is built, through the practical experience of Vardhaman Deshpande. The core insight is that pro-code developers using natural language with modern AI models can now build features and agents faster than many low-code tools. The conversation examines velocity gains, trade-offs between pro-code and low-code, and what this shift means for professionals building AI-powered solutions.  

Sundararajan S., Co-Founder and Chief Executive Officer of i-exceed technology solutionsi-exceed explores the future of digital banking through three key pillars: AI-powered personal financial management, real-time risk mitigation, and unified customer profiles. By leveraging predictive AI and low-code platforms like Appzillon, banks can modernize quickly while maintaining transparency, enhancing customer trust, and improving financial wellness. As banks shift from reactive to anticipatory engagement, i-exceed is driving innovation with solutions that balance legacy integration challenges and accelerate digital transformation. With a roadmap focused on next-generation explainable AI and expanded Banking-as-a-Service (BaaS), i-exceed is poised to lead the future of intelligent, customer-first financial services.

Cosa succede quando l'idea è giusta, il mercato risponde… ma la tecnologia non regge?In questa puntata di Pionieri del Tech, parlo con Stefano Tazio, CEO e co-founder di Builtdifferent, di una storia che molte startup conoscono fin troppo bene:- MVP costruito in outsourcing- Backend “Frankenstein”- Database che non scala- Migrazione disastrosa- Refactoring totale da zeroParliamo di debito tecnico, internalizzazione del team, errori di comunicazione nel lancio di una 2.0, hype creato troppo presto, migrazione di milioni di record e della scelta di passare a Flutter per ricostruire tutto.E poi affrontiamo il tema che oggi nessuna tech company può ignorare: come integrare l'AI senza farsi sostituire dall'AI.Una conversazione concreta, cruda, reale.Niente storytelling patinato. Solo cosa succede davvero quando fai prodotto.Capitoli:00:00 Intro e il background medico di Stefano Tazio01:22 Validare l'idea con Excel: lo "0 a 1" senza codice02:45 Il bivio dell'Outsourcing e il primo MVP03:50 Frankenstein tecnologico: quando il Low-Code diventa un limite05:15 Rifare tutto: il passaggio a Flutter e database relazionali06:40 Internalizzare il team: perché il codice deve essere tuo08:15 Errori di migrazione e gestione dell'Hype10:30 Consigli per founder: l'importanza del co-founder tecnico12:10 L'AI nel wellness: Human-in-the-loop e nuove feature14:50 Conclusioni e visione futura

In a podcast recorded at ITEXPO / MSP EXPO, Doug Green, Publisher of Technology Reseller News, spoke with Mike Ryan, CEO of SpiceX, about how low-code and no-code platforms are reshaping automation, integration, and revenue opportunities for MSPs and channel partners. The conversation focused on how SpiceX enables organizations to connect data, systems, and AI tools through visual workflow design rather than traditional software development. Ryan described SpiceX as a platform designed to remove complexity from integration and orchestration. “We make it stupid simple for an organization to connect and structure all of their data and then use drag-and-drop workflows to automate it,” he said. Built to be business-user friendly, the platform allows MSPs to design and deploy solutions without requiring deep coding expertise, accelerating time to value for both service providers and their customers. For MSPs, Ryan emphasized that the real opportunity lies in applying domain expertise rather than writing code. MSPs bring industry-specific knowledge—such as healthcare, background screening, or public sector workflows—and use SpiceX to build repeatable, branded solutions that can scale across multiple customers. According to Ryan, some partners have leveraged this approach to expand rapidly, even acquiring competitors by productizing their automation offerings. The discussion also touched on AI and the growing challenge of “shadow AI” inside organizations. Ryan noted that SpiceX enables MSPs and enterprises to safely connect approved AI tools into structured workflows, helping future-proof operations while maintaining control. As adoption accelerates, he positioned low-code automation as a practical way for MSPs, channel partners, and enterprises to turn complexity into scalable services and new revenue streams. Visit https://www.spicex.com/

www.iotusecase.com#IIoT #Shopfloor #LowCode In dieser Episode des IoT Use Case Podcasts spricht Gastgeber Dr. Peter Schopf mit Thilo Brosinsky, Entwicklungsleiter bei der Peakboard GmbH, und Björn Mutschler, Produktionsleiter bei der Johannes Giesser Messerfabrik GmbH. Thema: Wie eine dezentrale IoT-Low-Code-Plattform Shopfloor-Apps von der Maschinenintegration bis zum Energie- und Produktionsmanagement schrittweise skaliert. Folge 205 auf einen Blick (und Klick):(05:59) Herausforderungen, Potenziale und Status quo – So sieht der Use Case in der Praxis ausPodcast ZusammenfassungGIESSER Messer startete mit einer einfachen Shopfloor-Visualisierung, um Produktionskennzahlen erstmals tagesaktuell und direkt an der Maschine sichtbar zu machen. Die zentrale Herausforderung: geringe Akzeptanz, heterogene Datenquellen (ERP, Maschinen, Energie), fehlende Standards bei Maschinenschnittstellen und die Notwendigkeit, produktionskritische Anzeigen ausfallsicher zu betreiben – ohne Großprojekt oder Cloud-Zwang. Umgesetzt wurde dies mit einer dezentralen IoT-/Low-Code-Architektur: Anwendungen werden im Peakboard Designer per Drag-and-drop (bei Bedarf mit Scripting) erstellt, Daten über OPC UA, Modbus, SQL/ERP angebunden und auf lokale Peakboard Boxen verteilt; der Peakboard Hub dient optional zur zentralen Verwaltung, ohne dass bei Ausfall der Zentrale die Shopfloor-Logik stoppt. Eingesetzt werden u. a. MDE/BDE, Downtime-Tracking, papierarme Auftragssteuerung (ziehende Fertigung) sowie Energiemonitoring bis hin zu Lastmanagement. Für IT/OT-Entscheider zeigt der Use Case: iteratives Skalieren mit geringem Startaufwand, schnelle Integration bestehender OT/IT-Systeme, höhere Transparenz und robuste Betriebsfähigkeit im Werk.-----Relevante Folgenlinks:Peter (https://www.linkedin.com/in/peter-schopf/)Thilo (https://www.linkedin.com/in/thilo-brosinsky-39870766/)Jetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhaltenJetzt IoT Use Case auf LinkedIn folgen1x monatlich IoT Use Case Update erhalten

In dieser Folge schauen wir auf fünf IT‑Trends, die wir eigentlich längst beerdigt hatten – und die jetzt, dank künstlicher Intelligenz, stärker zurück sind als je zuvor. Warum erleben RPA, SharePoint‑Liebe, Custom Apps, Best‑of‑Breed‑Konzepte und sogar Fat Clients ein Comeback? Genau das bespreche ich heute. Kurzübersicht Wie KI die Rückkehr alter Konzepte notwendig und sinnvoll macht Warum RPA mit Computer Use Agents völlig neu gedacht wird Weshalb SharePoint wieder zum strategisch wichtigen Fundament wird Wieso Custom Apps ein Revival erleben – und welche Risiken das birgt Was Best of Breed heute wirklich bedeutet Warum lokale Rechenpower und Fat Clients wieder relevanter werden Kapitelübersicht 00:00 Einstieg und Konferenz‑Inspiration 00:20 Trend 1: RPA wird zum Computer Use Agent 07:47 Trend 2: SharePoint wird wieder strategisch 13:45 Trend 3: Custom Apps und die neue Schatten‑IT 18:45 Trend 4: Best of Breed statt reiner Suites 24:16 Trend 5: Das Comeback des Fat Clients 29:54 Fazit und Ausblick Inhaltlicher Überblick In dieser Episode spreche ich über fünf IT‑Trends, die unerwartet wieder in Mode kommen. Dabei geht es nicht um Nostalgie, sondern um eine fundamentale Veränderung: KI zwingt uns, alte Ideen neu zu betrachten. Ich beleuchte, wie RPA durch moderne Computer Use Agents plötzlich wieder ein ernstzunehmendes Werkzeug wird. Warum SharePoint – verstärkt durch Copilot, Agents und KI‑gestützte Intranets – wichtiger denn je ist. Weshalb Custom Apps dank Low‑Code, GitHub‑Agents und Power Platform einen zweiten Frühling erleben, gleichzeitig aber neue Risiken für Governance und Schatten‑IT mitbringen. Außerdem zeige ich, wie Unternehmen sich zunehmend von reinen Suite‑Ansätzen lösen und wieder stärker auf Best of Breed setzen. Und schließlich klären wir, warum lokale Rechenleistung und echte Fat Clients angesichts KI‑Workloads wieder unverzichtbar werden – zumindest für eine Übergangszeit. Wenn dir diese Folge gefallen hat, abonniere den Podcast und gib gern eine Bewertung ab. Schreib mir deine Fragen oder Themenwünsche auf LinkedIn – ich freue mich über dein Feedback. LinkedIn Daniel Rohregger: https://www.linkedin.com/in/drohregger/

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

Pour ce vingt-quatrième épisode, on retrouve Alexandre Talon qui partage son parcours entre No-Code, Low-Code et engagement social. Cofondateur de https://www.labastide.io/ et de l'association No-Code for Good, il accompagne des structures à impact positif grâce à des outils accessibles et solidaires.Alexandre raconte son quotidien dans l'économie sociale et solidaire, son intérêt grandissant pour le développement assisté par IA et son expérience récente avec Lovable, Windsurf, Bolt, Cursor et KiloCode. On découvre aussi la manière dont il combine Supabase, N8n et le vibe coding pour créer des solutions rapides et efficaces.Il revient également sur sa participation à la Grande Journée No-Code, sa table ronde sur l'avenir des agences à l'ère de l'IA et le plaisir de retrouver une communauté en constante évolution.Un épisode riche, clair et inspirant qui met en lumière une vision engagée du No-Code.https://www.linkedin.com/in/alexandre-talon-nocode/

In this episode of Software People Stories, Shiv is in conversation with Yaron Schneider, co-founder of Diagrid and a seasoned developer and entrepreneur deeply involved in the open source movement.Yaron shares his origin story, starting from programming at age 11 to his current role as co-founder of Diagrid. He discusses his early foray into university education, experience in the military, and his progression within the software industry, including a notable tenure at Microsoft.Yaron delves into the joys and pains of working in open source, detailing the challenges and rewards of maintaining a project with thousands of contributors and balancing corporate and community needs. The discussion also touches on the complexities of scaling in hybrid environments, the risks associated with supply chain attacks, and the evolving role of developers in the age of AI and low-code solutions.Yaron concludes by offering advice for those aspiring to contribute to open source and sharing personal strategies for managing the stresses of startup life. 00:00 Introduction and Welcome00:25 Yaron's Origin Story02:39 Joys and Pains of Open Source05:21 Challenges of Open Source Coordination06:14 Role Differences: Architect vs. CTO08:21 Corporate Influence on Open Source10:00 On-Prem vs. Cloud-Based Models11:34 Scalability in Hybrid Environments13:22 Introduction to Dapper and D Grid18:05 Security and Supply Chain Challenges23:27 Low-Code and No-Code Development25:29 Transition from Corporate to Startup27:04 Balancing Work and Personal Life28:31 Music and Software Development Parallels31:14 Getting Involved in Open Source32:21 Future of AI and Software Jobs33:50 Conclusion and Final ThoughtsThe timestamps are approximate, and after the intro that is about 90 seconds.For more closer timestamps, add 90 seconds to the labels aboveYaron Schneider is a visionary technologist and open source pioneer who has fundamentally shaped how developers build distributed applications. As co-creator of Dapr and KEDA—both graduated CNCF projects—he has enabled tens of thousands of enterprises to build more resilient, scalable cloud-native systems. Dapr is currently used by an estimated 30,000 to 40,000 enterprise users worldwide, while KEDA adoption may be even broader, though it is more difficult to estimate precisely.Now co-founder of Diagrid, Yaron is building the next generation of platforms that make it easier to develop and operate distributed applications and AI agents. His deep expertise in distributed systems, combined with years of leadership at Microsoft on scalable cloud architecture, positions him at the forefront of the agentic AI revolution.Recognized as an industry innovator in open source and platform engineering, Yaron bridges the gap between cutting-edge research and practical developer tools. His work continues to define how modern applications are built, deployed, and scaled in the cloud-native era.

If you think your value as a software engineer comes just from writing code, you're already at risk.In this episode, Outsystems CEO Woodson Martin reveals why AI isn't the real threat to your career. Irrelevance is. He explains that writing code is now only 20% of the job, and the engineers who thrive are the ones who master the other "80% that matters."We cover:The billions of lines of ungoverned code AI is creatingWhy the "Forward Deployed Engineer" model is changing team structuresThe 80% of engineering work that AI cannot replaceHow to shift from coder to problem solver who drives business revenueA CEO's advice for building a lasting engineering careerThis is a reality check for developers, tech leads, and architects who want to stay relevant as agentic AI reshapes the industry.Connect with Woodson:https://www.linkedin.com/in/woodsonmartinTimestamps:00:00:00 - Intro00:00:56 - How Agentic AI keeps the human in the loop00:01:55 - Real-world example: Automating the grunt work00:04:17 - How engineers are using agents internally00:05:52 - Blending Low-Code and High-Code for complex systems00:08:28 - Is a Low-Code career a trap for engineers?00:10:50 - Will AI make software engineering obsolete?00:12:09 - The 80/20 Rule: Why code is only 20% of your job00:13:14 - Layoffs vs. the rise of the solo entrepreneur00:15:18 - Career advice for a volatile tech market00:17:02 - How to retain top talent and keep them happy00:20:10 - Why we radically changed our engineering team structure00:24:33 - The "Forward Deployed Engineer" model explained00:27:08 - Outsystems vs. OpenAI: The future of platform building00:31:45 - The tech debt problem no one's talking about00:34:23 - The one thing that keeps you from becoming irrelevant#SoftwareEngineering #CareerAdvice #AIAgents

Acesse a ContrataPJ agora!https://4soci.al/contratapj-papo-ceoNo 180º episódio do Papo de CEO, recebemos Rodrigo Bernardinelli, CEO e Cofundador da Digibee, a única plataforma de integração low-code que escala a integração de workflows de aplicativos, reduz custos e aumenta a produtividade das equipes de tecnologia.Formado em Ciência da Computação e com MBA em Negócios, Rodrigo construiu uma trajetória sólida em empresas como CA Technologies e Zup Innovation antes de fundar a Digibee, hoje referência global em soluções de integração.Neste episódio, ele compartilha como o low-code está transformando o mercado de tecnologia, otimizando processos corporativos e permitindo que empresas de todos os portes acelerem sua transformação digital de forma simples, escalável e eficiente.Se você quer entender o futuro da integração de sistemas e como a Digibee vem impulsionando o crescimento de grandes corporações, esse episódio é pra você!

Power Platform ConferencePower Platform Community ConferenceMeet App Builder By Ryan CunninghamNewsHow to unfuck your LinkedIn feed and How to fix your LinkedIn feed part 2 by Luise FreesePower Platform CLI MCP by Daniel LaskewitzHow Do You AI? at Microsoft WorklabEntra External ID for Power Pages by Tino Rabe Power Pages server logic overview (preview)Strengthen Your Power Pages Security with CodeQL code scanClippy is BACK!Retrieves data from Dataverse using FetchXml as a knowledge source in Copilot Studio by Andreas AdnerEvaluate your agent's performance (preview) (Test Labs as presented by Lydia Williams)Jukka's CornerBe sure to subscribe so you don't miss a single episode of Power Platform BOOST!Thank you for buying us a coffee: buymeacoffee.comPodcast home page: https://powerplatformboost.comEmail: hello@powerplatformboost.comFollow us!Twitter: https://twitter.com/powerplatboost Instagram: https://www.instagram.com/powerplatformboost/ LinkedIn: https://www.linkedin.com/company/powerplatboost/ Facebook: https://www.facebook.com/profile.php?id=100090444536122 Mastodon: https://mastodon.social/@powerplatboost

 AI opportunities: Despite the excitement around AI, Kaupp emphasizes the importance of understanding the technology before fully integrating it into workflows. He advocates for “literacy before agency" to understand the true impacts of what AI "can unlock."Transformation with AI: Kaupp describes the process of transforming a contract approval process using AI tools, highlighting the importance of identifying inefficiencies and becoming “client zero” for automation. He poses a question relating to assisting customers with AI adoption: “If I can't identify 'stupid' things that we're living with and transforming them, how am I going to get clients to do that?”Internal impacts: Microsoft's release of all Microsoft Learn content as an MCP server has led to an important internal transformation for ArcherPoint by Cherry Bekaert, enabling consultants and developers to use AI-powered search instead of traditional engines to quickly find relevant functionality and updates. This approach has also been applied to the organization's own codebase, allowing access to previous customer implementations.Big trends for Business Central: Across all Microsoft products, and in the case of Business Central, Kaupp shares that clients are excited about the potential of AI agents, but many are still experimenting without clear use cases. As a result, he notes, consultants often find themselves reversing client-built solutions to make them production-ready.ArcherPoint by Cherry Bekaert at Summit NA: Kaupp and the team from ArcherPoint by Cherry Bekaert will be at Community Summit NA 2025, and you can connect with the team at their Booth #1007. Kaupp will also co-lead a session on Wednesday, October 22, "Leading Through Change: Harnessing Communication and Resilience." He encourages attendees to stop by the booth and chat with him on all things AI. "I'm there to learn or to guide... to me, that is the benefit of the community. It's the benefit of why we're all there," he notes.Contributors: John Siefert, Greg KauppSearch keywords:  No transcript Can be scheduled for 9:00 AM ET on 10/17.  Visit Cloud Wars for more.

Season 26 of the Building Better Developers podcast is all about Building Better Foundations. In Episode 2, hosts Rob Broadhead and Michael Meloche explore today's most flexible coding options—no-code, low-code, and a rising trend called vibe coding. Understanding Modern Coding Options Software creation no longer requires writing every line by hand. Today's coding options range from drag-and-drop builders to AI-generated code, giving teams new ways to move quickly from idea to launch. No-Code Coding Options for Rapid Builds No-code platforms enable you to assemble applications visually using pre-built components and workflows—ideal for creating landing pages, prototypes, or internal dashboards. The trade-offs for this coding option are scalability, security, and platform lock-in. Low-Code Coding Options for Integrated Workflows Low-code combines visual design with the ability to add custom logic where needed. Need email integration or payment processing? This coding option strikes a balance between speed and targeted customization. Even Excel with VBA macros fits here. Vibe Coding: The AI-Driven Coding Option Vibe coding utilizes large-language-model assistants, such as GitHub Copilot and ChatGPT, to generate code from natural language prompts. Treated like a junior developer, this coding option is powerful for prototypes and boilerplate but still requires human review and testing. Choosing the Right Coding Option Match project goals to the best coding option: Fast MVP or marketing site: No-code. Workflows that need integrations: Low-code. Quick prototypes or repetitive tasks: Vibe coding with code reviews. Scaling and Securing Your Coding Options Regardless of which coding option you start with, protect the future: Document architecture and dependencies early. Pin framework and library versions to avoid drift. Run security and performance tests with real data. Budget time for manual reviews—even when AI writes the code. Final Thoughts on Coding Options The expanding menu of coding options gives developers unprecedented flexibility. No-code speeds experiments, low-code balances speed with control, and vibe coding adds AI power. By understanding each approach's strengths and limits, you can launch quickly while building a foundation that lasts. 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 Developer Career Growth: Breaking Through Stagnation Dealing with Legacy Code: When to Let Go and Start Anew Code Refactoring: Maintaining Clean, Efficient Code The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

AI & Low-Code Transformation in Biotech IT #biotechit #AIrevolution #lowcodetechnologyIn this episode, Kevin Dushney, a seasoned CIO with over eight biotech companies under his belt, shares invaluable insights into the rapidly changing landscape of biotech IT. Please visit our website to get more information: https://swangroup.net/ With the rising impact of AI and low-code tools, small biotech teams can now deliver more than ever before. Kevin discusses how these tools are reshaping workflows and how fractional CIOs are transforming leadership models.From the challenges of compliance to the hype around AI, Kevin cuts through the noise and breaks down what's real, what's useful, and what's not. Tune in to hear practical strategies and discover what's truly happening behind the scenes in biotech IT.Links from this episode:✅ Get to know more about Kevin Dushney: https://www.linkedin.com/in/kevindushney 

Wir schauen uns das große Paradoxon der aktuellen Software-Entwicklung an: Noch nie war es so einfach, Software zu entwickeln - und noch nie war es so schwer, damit erfolgreich zu werden. Durch konkrete Daten und Beispiele erfährst du , warum KI, Low-Code und Cloud-Services die Entwicklung revolutionieren, aber gleichzeitig die Distribution zur größten Herausforderung machen.  Was du lernst: Die Beschleunigung der Entwicklung: Wie KI-Assistenten die Entwicklung um 55% beschleunigen Warum Low-Code die Zukunft ist Die Rolle von Cloud & APIs Die Herausforderungen: 9 Millionen Apps weltweit Steigende Marketingkosten Übersättigte Kanäle Die deutsche Perspektive: Stärken im Engineering Schwächen in der Distribution Das "Made in Germany" Potenzial Konkrete Strategien: Die doppelte Secret Sauce Community Building Fokus auf echte Painpoints Next Steps: Vertrieb ins Gründerteam Global denken, lokal starten Branding & Vertrauen aufbauen Die in der Folge genannten Episoden findest du unter Sales Bakery auf https://www.unicornbakery.de/episodes/  ALLES ZU UNICORN BAKERY: https://zez.am/unicornbakery  Join our Founder Tactics Newsletter: 2x die Woche bekommst du die Taktiken der besten Gründer der Welt direkt ins Postfach: https://www.tactics.unicornbakery.de/  Kapitel: (00:00) Die einfache Seite: KI & Tools (02:55) Die harte Realität: Übersättigung (04:18) Das globale Paradoxon (05:31) Konkrete Strategien & Empfehlungen (08:16) Weiterführende Ressourcen

In this episode, David and Dwight continue their “AI-Off,” a deep dive into using AI development tools to automate everyday tasks and create custom applications for HR. They explore the concept of "vibe coding" with platforms like Replit and Base44, discussing how HR professionals can leverage natural language to build powerful tools without extensive coding knowledge. They cover the iterative development process, the importance of subject matter expertise, and the practical realities of cost and security when deploying AI solutions. [0:00] Introduction Welcome, David and Dwight! Today's Topic: The AI-Off Part Two - Building AI Applications with Natural Language [8:19] The Pros and Cons of AI Development Tools How platforms like Replit and Base 44 handle the entire application stack, from the user experience to the backend data.  The power of these tools to quickly build dashboards, scorecards, and data aggregation tools that once took significant time and effort.  [17:38] How to build AI Applications with Natural Language Why subject matter expertise is crucial for guiding the AI to build a useful and accurate application.  The importance of providing context to the AI, much like a product manager creates user stories for a development team.  [24:09] The Reality of Building with AI: Costs, Security, and Deployment Understanding the costs associated with using these platforms and weighing them against the time and effort saved.  The need for human oversight and professional review, especially for security and compliance, before deploying an application externally.  [30:24] Closing Thanks for listening! Quick Quote “If you want [AI] to help you use your job better, [using tools like Replit or Base44] is potentially a really great way of being able to utilize your skills and your knowledge in this area.”

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM 

Struggling with data capture in remote or low-connectivity areas? Discover how an offline-capable app could transform your field team's productivity and efficiency.More information is available at https://www.alphasoftware.com/professional-services Alpha Software City: Burlington Address: 70 Blanchard Road Website: https://www.alphasoftware.com/ Phone: +1 781 229 4500 Email: support@alphasoftware.com

Release Plans Visualized by Jukka NiiranenPowerDocu for Copilot Studio in the works by Rene Modery Copilot Studio: How I Built A Generative Orchestration Agent by Matthew DevanyMichael Keimeyer shared

Low-code systems democratize artificial intelligence tools, allowing nontechnical staff members to produce data-driven apps independently. This movement creates questions about governance, security, and quality control even while it gives innovators agility and speed. How can companies enable low-code tool-equipped business units to provide strong security and governance? Are there best practices for juggling autonomy with control in democratized AI systems? What unanticipated difficulties might result from this move toward general AI availability? Guest: Udit Pahwa, Chief Information Officer at Blue Star Limited Guest Bio: Udit Pahwa More on this Episode: https://www.ciotalknetwork.com/low-code-ai-apps-enabling-innovation-ensuring-control/ More on AI & ML: https://www.ciotalknetwork.com/topics/artificial-intelligence-machine-learning/ Visit CIO Talk Network Website: https://www.ciotalknetwork.com/  

Catie King is the Co-founder of Stradia Partners, a consultancy that empowers companies to optimize operations through low-code, no-code, and AI-powered technology solutions. Stradia Partners specializes in building scalable internal tools using platforms like Airtable and Retool to streamline workflows, consolidate data, and boost team efficiency across industries. With over a decade of experience in product management, Catie previously served as Head of Product at flyExclusive, one of the largest private jet operators in the US. Outside of her work in tech, she is also a musician and a strong advocate for data-informed decision-making. In this episode… Many growing companies struggle with inefficiencies, fragmented data, and time-consuming manual processes, especially when teams rely on outdated spreadsheets or lack the budget for full-scale development. How can these businesses leverage today's tools to simplify operations and scale smarter? Catie King, an experienced product manager turned tech founder, believes the solution lies in low-code, no-code, and AI-powered platforms. Drawing from her experience leading product at a major private jet company and now co-founding Stradia Partners, Catie shares how tools like Airtable and Retool empower non-developers to create sophisticated solutions that streamline workflows and reduce costs. She also unpacks how generative AI is accelerating this shift, making once complex tech accessible to lean teams. Tune in to this episode of the Smart Business Revolution Podcast as John Corcoran interviews Catie King, Co-founder of Stradia Partners, about building custom solutions using low-code and AI. Catie shares how her background in music and journalism led her to tech, why she believes in empowering operations teams, and how tools like Airtable, Retool, and generative AI are redefining modern software development.

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM

Katherine is the founder of K.tab Creative, a branding and web design studio that helps small businesses and startups build strategic online presences. Her winding path to entrepreneurship includes a first career as a furniture buyer, several years in influencer and digital marketing (with a six-year side hustle as a fashion blogger), and nearly five years as a full-stack software engineer. Today, she blends her creative and technical background to craft thoughtful brand identities and custom websites that are as intuitive as they are impactful. When she's not at her laptop, Katherine enjoys working on her photography skills, trying out new restaurants and planning her next international travel destination. website: https://www.ktabcreative.com/ linkedin: https://www.linkedin.com/in/katherinetabinowski/  Ramblings of a Designer podcast is a monthly design news and discussion podcast hosted by Laszlo Lazuer and Terri Rodriguez-Hong (@flaxenink, insta: flaxenink.design) (insta: @happiscribble. LinkedIn Page: https://www.linkedin.com/company/ramblings-of-a-designer/ Facebook: https://www.facebook.com/Ramblings-of-a-Designer-Podcast-2347296798835079/ Send us feedback! ramblingsofadesignerpod@gmail.com Support us on Patreon! patreon.com/ramblingsofadesigner

The Future Of Biotech IT: AI, Cybersecurity & Low-Code Platforms | Steve Eichorn #biotech #aiinbiotech #cybersecurityHow is AI transforming the future of biotech today, not just in labs but in IT departments too? Please visit our website to get more information: https://swangroup.net/In this episode, I sit down with Steve Eichorn, CIO of Cytiva, to explore how artificial intelligence, cybersecurity, and low-code platforms are reshaping biotech from the inside out. Specifically, this episode highlights the following themes:✅ How AI is improving biotech operations and clinical processes✅ The growing importance of cybersecurity in an AI-driven world✅ Why low-code development is shaping the future of IT and business collaborationSteve shares his unique journey from finance to leading global IT and explains how AI is accelerating drug development, why low-code tools are changing how teams build solutions, and how security is now a core part of innovation. We also talk about how tech leaders are breaking down data silos, building more collaborative cultures, and preparing for the digital future of healthcare.If you're in biotech, tech, or healthcare, this conversation is full of insights you won't want to miss.Links from this episode:✅ Get to know more about Steven Swan: https://www.linkedin.com/in/swangroup ✅ Get to know more about Steve Eichorn: https://www.linkedin.com/in/steve-eichorn-he-his-him-68b8105

✨ Heads up! This episode features a demonstration of the SnapLogic UI and its AI Agent Creator towards the end. For the full visual experience, check out the video version on the Spotify app! ✨(Episode Summary)Tired of tangled data spread across multiple clouds, on-premise systems, and the edge? In this episode, MongoDB's Shane McAllister sits down with Peter Ngai, Principal Architect at SnapLogic, to explore the future of data integration and management in today's complex tech landscape.Dive into the challenges and solutions surrounding modern data architecture, including:Navigating the complexities of multi-cloud and hybrid cloud environments.The secrets to building flexible, resilient data ecosystems that avoid vendor lock-in.Strategies for seamless data integration and connecting disparate applications using low-code/no-code platforms like SnapLogic.Meeting critical data compliance, security, and sovereignty demands (think GDPR, HIPAA, etc.).How AI is revolutionizing data automation and providing faster access to insights (featuring SnapLogic's Agent Creator).The powerful synergy between SnapLogic and MongoDB, leveraging MongoDB both internally and for customer integrations.Real-world applications, from IoT data processing to simplifying enterprise workflows.Whether you're an IT leader, data engineer, business analyst, or simply curious about cloud strategy, iPaaS solutions, AI in business, or simplifying your data stack, Peter offers invaluable insights into making data connectivity a driver, not a barrier, for innovation.-Keywords: Data Integration, Multi-Cloud, Hybrid Cloud, Edge Computing, SnapLogic, MongoDB, AI, Artificial Intelligence, Data Automation, iPaaS, Low-Code, No-Code, Data Architecture, Data Management, Cloud Data, Enterprise Data, API Integration, Data Compliance, Data Sovereignty, Data Security, Business Automation, ETL, ELT, Tech Stack Simplification, Peter Ngai, Shane McAllister.

No episódio de hoje do Podcast Canaltech, exploramos uma das maiores tendências do momento: a combinação de low-code e Inteligência Artificial, que está transformando a criação de software nas empresas ao redor do mundo. Para discutir como essas tecnologias estão mudando a forma como as organizações criam e escalam suas soluções, conversamos com Lucas Felisberto, Vice-Presidente de Vendas e Sucesso do Cliente para a América Latina da Jitterbit, líder global em plataformas de integração e automação. Ele compartilha insights sobre como o low-code, que permite criar aplicações com pouco ou nenhum código, está se unindo à IA para acelerar o desenvolvimento, reduzir custos e tornar as empresas mais ágeis e competitivas no mercado. Você vai descobrir: O que é o desenvolvimento low-code e como ele está revolucionando a criação de software. O impacto da combinação de low-code e IA nas empresas e como isso altera a forma de desenvolver soluções. Como pequenas e médias empresas podem aproveitar essas tecnologias para competir com grandes corporações. O futuro das carreiras em TI com a popularização dessas tecnologias e o papel das equipes de TI no novo cenário. Desafios de governança e segurança em um mundo cada vez mais automatizado e conectado. Você também vai conferir: Apagão atinge Europa e levanta suspeitas de ciberataque; WhatsApp vai liberar reações com figurinhas e novo atalho para áudios; Apple prepara óculos inteligentes com foco em IA e design mais leve; Vivo lança celular barato com visual de iPhone e bateria de longa duração; Starlink lança antena compacta no Brasil, com internet de 100 Mbps e mais leve. Este Podcast foi roteirizado e apresentado por Fernanda Santos e contou com reportagens de André Lourenti, Emanuele Almeida, Renato Moura e Vinicius Moschen. A trilha sonora é de Guilherme Zomer, a edição de Jully Cruz e a arte da capa é de Erick Teixeira. Você escuta o Podcast do Canaltech de segunda a sexta-feira.See omnystudio.com/listener for privacy information.

Crystal Camarao is Executive Director at No-code Philippines.No-code Philippines is empowering the no-code and low-code community in the Philippines. No-code Philippines holds regular meetups, events, conferences, and hackathons to educate Filipinos in the concept of no-code, empower and upskill users, and provide a venue for networking and mentorship. No-code Philippines advocates no-code for smart innovation, agile startup validation, as well as having citizen developers who can create amazing apps at our own fingertips.IN THIS EPISODE | 01:08 Ano ang No-code Philippines? | 06:00 What are the advantages of using no-code tools? | 12:39 Why did you start No-code Philippines? | 19:10 How is No-code Philippines empowering the community? | 31:30 What programs and events does No-code Philippines hold? | 41:56 How is the experience building the community? | 57:00 What is the vision? | 01:04:00 How can listeners find more information?NO-CODE PHILIPPINES | Website: ⁠https://nocode.ph⁠ | Facebook: ⁠https://facebook.com/nocodeph⁠THIS EPISODE IS CO-PRODUCED BY:SPROUT SOLUTIONS | Website: ⁠⁠⁠⁠⁠https://sprout.ph⁠⁠⁠⁠⁠ | Sprout Payroll Starter: ⁠⁠⁠⁠⁠https://bit.ly/SproutPayrollStarter⁠⁠⁠⁠⁠APEIRON | Website: ⁠⁠⁠⁠⁠https://apeirongrp.com⁠⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠⁠https://facebook.com/apeirongrp⁠⁠⁠⁠⁠TWALA | Website: ⁠⁠⁠⁠⁠https://twala.io⁠⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠⁠https://facebook.com/twalaio⁠⁠⁠⁠⁠SYMPH | Website: ⁠⁠⁠⁠⁠https://symph.co⁠⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠⁠https://facebook.com/SymphCo⁠⁠⁠⁠⁠AIMHI | Website: ⁠⁠⁠⁠⁠https://aimhi.ai⁠⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠⁠https://facebook.com/aimhiconstruction⁠⁠⁠⁠⁠CHECK OUT OUR PARTNERS | Ask Lex PH Academy: ⁠⁠⁠⁠⁠https://asklexph.com⁠⁠⁠⁠⁠ (Get 5% discount on e-learning courses! Code: ALPHAXSUP) | Hyperstacks: ⁠⁠⁠⁠⁠https://hyperstacksinc.com⁠⁠⁠⁠⁠ | OneCFO: ⁠⁠⁠⁠⁠https://onecfoph.co⁠⁠⁠⁠⁠ (Get 10% discount on CFO services! Code: ONECFOXSUP) | UNAWA: ⁠⁠⁠⁠⁠https://unawa.asia⁠⁠⁠⁠⁠ | SkoolTek: ⁠⁠⁠⁠⁠https://skooltek.co⁠⁠⁠⁠⁠ | Better Support: ⁠⁠⁠⁠⁠https://bettersupport.io⁠⁠⁠⁠⁠ (They are offering a referral program for anyone who can bring in new BPO clients! Send us a message to know more) | Britana: ⁠⁠⁠⁠⁠https://britanaerp.com⁠⁠⁠⁠⁠ | Wunderbrand: ⁠⁠⁠⁠⁠https://wunderbrand.com⁠⁠⁠⁠⁠ | Fail Coach: ⁠⁠⁠⁠⁠https://fail.coach⁠⁠⁠⁠⁠ | Drive Manila: ⁠⁠⁠⁠⁠https://facebook.com/drivemanilaph⁠⁠⁠⁠⁠ | EastPoint Business Outsourcing Services: ⁠⁠⁠⁠⁠https://facebook.com/eastpointoutsourcing⁠⁠⁠⁠⁠ | Doon: ⁠⁠⁠⁠⁠https://doon.ph⁠⁠⁠⁠⁠ | Hier Business Solutions: ⁠⁠⁠⁠⁠https://hierpayroll.com⁠⁠⁠⁠⁠ | DVCode Technologies: ⁠⁠⁠⁠⁠https://dvcode.tech⁠⁠⁠⁠⁠ | Mata Technologies: ⁠⁠⁠⁠⁠https://mata.ph⁠⁠⁠⁠⁠ | Smile: ⁠⁠⁠⁠⁠https://getsmileapi.com⁠⁠⁠⁠⁠ | Mommyki Super Pet App: ⁠⁠⁠⁠⁠https://mommyki.com⁠⁠⁠⁠⁠ | Ignite Careers: ⁠⁠⁠⁠⁠https://ignitecareers.ph⁠⁠⁠⁠⁠ LookingFour Buy & Sell Online: ⁠⁠⁠⁠⁠https://lookingfour.com⁠⁠⁠⁠⁠ | NutriCoach: ⁠⁠⁠⁠⁠https://nutricoach.com⁠⁠⁠⁠⁠ | Digest PH: ⁠⁠⁠⁠⁠https://digest.ph⁠⁠⁠⁠⁠ (Get 10% discount on legal services! Code: DIGESTXSUP) | Contakt RFID Business Cards: ⁠⁠⁠⁠⁠https://contakt-ph.com⁠⁠⁠⁠⁠ (Get 10% discount on RFID Business Cards! Code: CONTAKTXSUP) | Uplift Code Camp: ⁠⁠⁠⁠⁠https://upliftcodecamp.com⁠⁠⁠⁠⁠ (Get 5% discount on bootcamps and courses! Code: UPLIFTSTARTUPPH) | Wasteless PH | Tech Tribe | YEY | Board Prep | DOHE Philippines | EdFolio | HiveRooms | Kazam | CodeChum | Jur.ph | Big Giant Games | Agile Data Solutions - Hustle PH | Pahatid PH | Founders Launchpad | Pareto Consulting | SeriousMDSTART UP PODCAST PH | YouTube: ⁠⁠⁠⁠⁠https://youtube.com/startuppodcastph⁠⁠⁠⁠⁠ | Spotify: ⁠⁠⁠⁠⁠https://open.spotify.com/show/6BObuPvMfoZzdlJeb1XXVa⁠⁠⁠⁠⁠ | Apple Podcasts: ⁠⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/start-up-podcast/id1576462394⁠⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠⁠https://facebook.com/startuppodcastph⁠⁠⁠⁠⁠ | Patreon: ⁠⁠⁠⁠⁠https://patreon.com/StartUpPodcastPH⁠⁠⁠⁠⁠ | Website: ⁠⁠⁠⁠⁠https://phstartup.online⁠⁠⁠⁠⁠This episode is edited by the team at: ⁠⁠⁠⁠⁠https://tasharivera.com⁠⁠

Crystal Camarao is Executive Director at No-code Philippines.No-code Philippines is empowering the no-code and low-code community in the Philippines. No-code Philippines holds regular meetups, events, conferences, and hackathons to educate Filipinos in the concept of no-code, empower and upskill users, and provide a venue for networking and mentorship. No-code Philippines advocates no-code for smart innovation, agile startup validation, as well as having citizen developers who can create amazing apps at our own fingertips.IN THIS EPISODE | 01:08 Ano ang No-code Philippines? | 06:00 What are the advantages of using no-code tools? | 12:39 Why did you start No-code Philippines? | 19:10 How is No-code Philippines empowering the community? | 31:30 What programs and events does No-code Philippines hold? | 41:56 How is the experience building the community? | 57:00 What is the vision? | 01:04:00 How can listeners find more information?NO-CODE PHILIPPINES | Website: https://nocode.ph | Facebook: https://facebook.com/nocodephTHIS EPISODE IS CO-PRODUCED BY:SPROUT SOLUTIONS | Website: ⁠⁠⁠⁠https://sprout.ph⁠⁠⁠⁠ | Sprout Payroll Starter: ⁠⁠⁠⁠https://bit.ly/SproutPayrollStarter⁠⁠⁠⁠APEIRON | Website: ⁠⁠⁠⁠https://apeirongrp.com⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠https://facebook.com/apeirongrp⁠⁠⁠⁠TWALA | Website: ⁠⁠⁠⁠https://twala.io⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠https://facebook.com/twalaio⁠⁠⁠⁠SYMPH | Website: ⁠⁠⁠⁠https://symph.co⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠https://facebook.com/SymphCo⁠⁠⁠⁠AIMHI | Website: ⁠⁠⁠⁠https://aimhi.ai⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠https://facebook.com/aimhiconstruction⁠⁠⁠⁠CHECK OUT OUR PARTNERS | Ask Lex PH Academy: ⁠⁠⁠⁠https://asklexph.com⁠⁠⁠⁠ (Get 5% discount on e-learning courses! Code: ALPHAXSUP) | Hyperstacks: ⁠⁠⁠⁠https://hyperstacksinc.com⁠⁠⁠⁠ | OneCFO: ⁠⁠⁠⁠https://onecfoph.co⁠⁠⁠⁠ (Get 10% discount on CFO services! Code: ONECFOXSUP) | UNAWA: ⁠⁠⁠⁠https://unawa.asia⁠⁠⁠⁠ | SkoolTek: ⁠⁠⁠⁠https://skooltek.co⁠⁠⁠⁠ | Better Support: ⁠⁠⁠⁠https://bettersupport.io⁠⁠⁠⁠ (They are offering a referral program for anyone who can bring in new BPO clients! Send us a message to know more) | Britana: ⁠⁠⁠⁠https://britanaerp.com⁠⁠⁠⁠ | Wunderbrand: ⁠⁠⁠⁠https://wunderbrand.com⁠⁠⁠⁠ | Fail Coach: ⁠⁠⁠⁠https://fail.coach⁠⁠⁠⁠ | Drive Manila: ⁠⁠⁠⁠https://facebook.com/drivemanilaph⁠⁠⁠⁠ | EastPoint Business Outsourcing Services: ⁠⁠⁠⁠https://facebook.com/eastpointoutsourcing⁠⁠⁠⁠ | Doon: ⁠⁠⁠⁠https://doon.ph⁠⁠⁠⁠ | Hier Business Solutions: ⁠⁠⁠⁠https://hierpayroll.com⁠⁠⁠⁠ | DVCode Technologies: ⁠⁠⁠⁠https://dvcode.tech⁠⁠⁠⁠ | Mata Technologies: ⁠⁠⁠⁠https://mata.ph⁠⁠⁠⁠ | Smile: ⁠⁠⁠⁠https://getsmileapi.com⁠⁠⁠⁠ | Mommyki Super Pet App: ⁠⁠⁠⁠https://mommyki.com⁠⁠⁠⁠ | Ignite Careers: ⁠⁠⁠⁠https://ignitecareers.ph⁠⁠⁠⁠ LookingFour Buy & Sell Online: ⁠⁠⁠⁠https://lookingfour.com⁠⁠⁠⁠ | NutriCoach: ⁠⁠⁠⁠https://nutricoach.com⁠⁠⁠⁠ | Digest PH: ⁠⁠⁠⁠https://digest.ph⁠⁠⁠⁠ (Get 10% discount on legal services! Code: DIGESTXSUP) | Contakt RFID Business Cards: ⁠⁠⁠⁠https://contakt-ph.com⁠⁠⁠⁠ (Get 10% discount on RFID Business Cards! Code: CONTAKTXSUP) | Uplift Code Camp: ⁠⁠⁠⁠https://upliftcodecamp.com⁠⁠⁠⁠ (Get 5% discount on bootcamps and courses! Code: UPLIFTSTARTUPPH) | Wasteless PH | Tech Tribe | YEY | Board Prep | DOHE Philippines | EdFolio | HiveRooms | Kazam | CodeChum | Jur.ph | Big Giant Games | Agile Data Solutions - Hustle PH | Pahatid PH | Founders Launchpad | Pareto Consulting | SeriousMDSTART UP PODCAST PH | YouTube: ⁠⁠⁠⁠https://youtube.com/startuppodcastph⁠⁠⁠⁠ | Spotify: ⁠⁠⁠⁠https://open.spotify.com/show/6BObuPvMfoZzdlJeb1XXVa⁠⁠⁠⁠ | Apple Podcasts: ⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/start-up-podcast/id1576462394⁠⁠⁠⁠ | Facebook: ⁠⁠⁠⁠https://facebook.com/startuppodcastph⁠⁠⁠⁠ | Patreon: ⁠⁠⁠⁠https://patreon.com/StartUpPodcastPH⁠⁠⁠⁠ | Website: ⁠⁠⁠⁠https://phstartup.online⁠⁠⁠⁠This episode is edited by the team at: ⁠⁠⁠⁠https://tasharivera.com⁠

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVMFULL SHOW NOTES https://www.microsoftinnovationpodcast.com/660  Zeeshan Saeed's journey from a website designer to a dynamic MVP leader emphasizes the transformative power of community and the importance of adapting to technological evolution. He discusses his career transitions, the current job market in Sydney, and the necessity of best practices in tech implementations. Our conversation also uncovers the shifting trend of tech professionals gravitating towards freelancing, driven by technological advancements outpacing corporate adoption. Gain valuable perspectives on the challenges of AI integration in businesses and how nimble startups are seizing these tech opportunities. TAKEAWAYS• Emphasizes the impact of community on professional growth • Discusses the transition from traditional coding to low-code platforms • Zeeshan shares his insights on the job market for Power Platform professionals • Highlights the importance of best practices in tech implementations • Reflects on his major projects, including government data initiatives • Explores the rise of freelancing in the tech industryOTHER RESOURCES: Microsoft MVP YouTube Series - How to Become a Microsoft MVP This year we're adding a new show to our line up - The AI Advantage. We'll discuss the skills you need to thrive in an AI-enabled world. Accelerate your Microsoft career with the 90 Day Mentoring Challenge We've helped 1,300+ people across 70+ countries establish successful careers in the Microsoft Power Platform and Dynamics 365 ecosystem.Benefit from expert guidance, a supportive community, and a clear career roadmap. A lot can change in 90 days, get started today!Support the showIf you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

FULL SHOW NOTES https://www.microsoftinnovationpodcast.com/654George Grammatikos' journey as a cloud integrator and Microsoft MVP showcases the blend of technology and personal experiences. With a passion for the Power Platform and a leadership role in various Microsoft communities, George has not only influenced the tech world but also left a mark on those he mentors. His story is one of ambition, dedication, and a deep commitment to pushing the boundaries of technology, making him a beacon of inspiration for aspiring tech professionals. Join us for an enriching conversation that blends professional insights with a heartfelt celebration of life's simple pleasures.  TAKEAWAYS  • George's personal connection to family and Greek cuisine • The transition from hardware to cloud technology • Insights into remote work and its benefits • Exploration of business applications and low-code tools • Future aspirations in AI and technology trends OTHER RESOURCES:Microsoft MVP YouTube Series - How to Become a Microsoft MVPThis year we're adding a new show to our line up - The AI Advantage. We'll discuss the skills you need to thrive in an AI-enabled world. Accelerate your Microsoft career with the 90 Day Mentoring Challenge We've helped 1,300+ people across 70+ countries establish successful careers in the Microsoft Power Platform and Dynamics 365 ecosystem.Benefit from expert guidance, a supportive community, and a clear career roadmap. A lot can change in 90 days, get started today!Support the showIf you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

This week's guest is ZJ van de Weg (https://www.linkedin.com/in/zegerjan/), CEO of FlowFuse. ZJ shares his journey from an intern at GitLab to now leading FlowFuse, how open-source technology is transforming industrial operations, and why Node-RED has become the go-to platform for low-code manufacturing connectivity. He also takes a deep dive into the challenges of scaling open source solutions in enterprise environments, the value of an ‘open-core' business model, and the future of IT/OT collaboration. Augmented Ops is a podcast for industrial leaders, citizen developers, shop floor operators, and anyone else that cares about what the future of frontline operations will look like across industries. This show is presented by Tulip (https://tulip.co/), the Frontline Operations Platform. You can find more from us at Tulip.co/podcast (https://tulip.co/podcast) or by following the show on LinkedIn (https://www.linkedin.com/company/augmentedpod/). Special Guest: ZJ van de Weg.

Co-founders Sean Blagsvedt and Archana Prasad of Gooey.AI discuss how their platform is making AI more accessible across communities. The platform enables teams to leverage multiple AI tools, enhancing productivity in sectors like agriculture, healthcare, and frontline services. Key applications include multilingual chatbots that support African farmers through WhatsApp and AI assistants that help HVAC technicians access technical documentation.

Ben and Andrew open the show by discussing the emergence of the DeepSeek AI model, Google's shakeup of the SEO landscape, and speculate on whether or not we're seeing the death of free APIs.Then, Ben sits down with Bernd Ruecker, Co-Founder and Chief Technologist at Camunda, to explore how low code solutions are changing the game for developers. They discuss how these tools allow developers to focus on more complex challenges, and delve into the importance of understanding when to leverage low code versus custom solutions, and the evolving role of developers in a world increasingly driven by automation.Finally, do us a favor and fill out the Dev Interrupted listener survey! You'll be our best friend forever :-)Show Notes:Dev Interrupted SurveyBeyond the DORA Frameworks Workshop (Jan. 29, 30)Follow BenFollow AndrewFollow BerndLearn more at: camunda.comCamundacon 2025Support the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

Brad and Amy dive into their year-end tech reflections, discussing goal-setting strategies and Amy's ambitious Build 12 project for 2025. The hosts explore various database hosting solutions, share their favorite hardware purchases including cameras and peripherals, and examine how AI tools are reshaping development workflows. The episode concludes with insights into emerging tech trends and anticipated developments for 2025.Chapter Marks00:00 Episode introduction and host intros00:41 Year-end goals discussion and 12-week planning02:02 Amy's Build 12 project announcement03:01 Goal setting strategies and focus04:25 Brad's 2024 goals review05:35 Travel plans and New York City trips06:58 More 2024 goals: fitness, career, and finances08:21 Technical stack discussion13:22 AI tools and development workflows17:19 Database hosting options comparison25:45 Tech gear and hardware updates33:47 Notable tech purchases review43:29 AI tools and future tech discussionLinksBuild Twelve, by Brian P. Moran - Amy's upcoming projectThe 12 Week Year (book)Atomic Habits, by James Clear (book)The Power of Habit, by Charles Duhigg (book)SupabaseNeon databaseDigital OceanTursoCursor IDERemarkable Tablet (v2)Oura RingRazer Basilisk V3 Pro mouseSwish app for MacNuphy Air 75 keyboardDrop keyboardInsta360 One cameraInsta360 Go 3 cameraNikon ZFC cameraRay Deck - Episode 182: Low-Code as a Medium For High-Speed DevelopersMarc LouPieter LevelsWorkOSThe Best Way to Add Authentication to Your Astro Website (Amy's YouTube Video)Comparing Frameworks - Amy's projectGitHub CopilotClaudeconvertkit.comloops.soPrisma

Is low-code development the future of digital transformation? In this episode of Tech Talks Daily, I sit down with Hans de Visser, Chief Product Officer at Mendix, to explore how low-code is reshaping the enterprise software space. With 73% of C-suite executives now viewing low-code as the only viable coding option, Hans shares insights into why this technology is no longer a departmental fix but a strategic enabler driving innovation at scale. Hans delves into Mendix's integration of generative AI, which is revolutionizing the software development lifecycle. From AI-assisted data modeling to AI-powered applications, he explains how the fusion of AI and low-code creates a productivity leap that enables enterprises to innovate faster and more efficiently. But innovation doesn't come without challenges. Governance, security, and upskilling remain critical to unlocking the potential of low-code while mitigating risks. The conversation also touches on the increasing collaboration between IT and business teams, as organizations adopt fusion team models to harness the full spectrum of talent. Hans offers practical advice on addressing knowledge gaps, building cross-functional teams, and creating sustainable digital transformation strategies. We'll also discuss Mendix's latest research findings, which highlight the growing influence of non-technical C-suite executives in low-code adoption and the importance of regulatory compliance frameworks in reducing risks. With AI and low-code seen as key drivers of future enterprise growth, this discussion provides a compelling look at how technology can transform business processes from the ground up. What are your thoughts on low-code and its role in shaping the future of digital transformation? Could this be the game-changer your business needs? Tune in and let us know what you think!

Send me a Text Message hereFULL SHOW NOTES https://podcast.nz365guy.com/620  Emma-Claire Shaw, a dynamic low-code product manager and consultant at Defra in the UK, brings her vibrant personality to our latest discussion. With a bustling family life, including two young daughters and a dog, Emma balances her work with a passion for social activities such as music festivals and fitness through early morning gym sessions and trail running. Her intriguing relationship with food reveals a chocoholic side matched with a deep interest in nutrition and a primarily plant-based diet. We unravel her insights into the latest gut health trends, where she shares her experiences with nutrition and I reveal my experiments with Celtic salt for weight management.Our conversation takes a fascinating twist into the world of Microsoft Power Platform, as Emma shares her journey of implementing transformative low-code solutions in government operations. Her experiences highlight the impact of Power Apps in streamlining processes such as fleet vehicle logs and port inspections at Defra, showcasing the potential for increased efficiency in the public sector. We also reflect on the significant role of Microsoft 365 and the evolution of tech adoption in government, sharing compelling stories from around the world, including innovative uses of similar technology in container inspections in Australia.As we round off our episode, we dive into the digital transformation efforts of environmental agencies in the UK, focusing on initiatives like the Environment Agency's efficient fishing rod license verification via Power App. Emma discusses the ongoing challenges with offline data access in remote areas and shares strategies that have been successfully deployed elsewhere, such as in Western Australia. We also delve into Natural England's modernization of its licensing schemes, marking a shift from paper-based forms to a centralized digital platform, reflecting a broader move towards operational efficiency and innovation in government processes. Join us for this captivating narrative that weaves together technology, lifestyle, and wellness.90 Day Mentoring Challenge 10% off code use MBAP at checkout https://ako.nz365guy.comSupport the showIf you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

Keri Olson (@ksolson20, VP AI for Code at @IBM) talks about coding assistants across the software development lifecycle, the future of agents, and domain-specific assistants.SHOW: 869SHOW TRANSCRIPT: The Cloudcast #869 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" SHOW SPONSOR:While data may be shaping our world, Data Citizens Dialogues is shaping the conversationFollow Data Citizens Dialogues on Apple, Spotify, YouTube, or wherever you get your podcastsSHOW NOTES:IBM Watsonx Code Assistant (homepage)IBM Watsonx Code Assistant for Ansible Lightspeed (homepage)IBM Watsonx Code Assistant for Z (homepage)Topic 1 - Welcome to the show. Tell us about your background, and then give us a little bit of background on where you focus your time at IBM these days?Topic 2 - Developer code assistants have become one of the most popular areas of GenAI usage. At a high level, how mature are the technologies that augment developers today? Topic 3 - Software development has an entire lifecycle (Generate, Complete, Explain, Test, Transform, Document). It's easy for developers to just plug in a service, but is that often the most effective way to start using GenAI in the software development lifecycle? Topic 4 - Software developers are notoriously picky about what tools they use and how they use them. GenAI doesn't “guarantee” outputs. Are there concerns that if different developers or groups use different coding assistants, that it could create more challenges than it helps? Topic 5 - What is a holistic way to think about code assistants? How much should be actively engaged with developers, how much should be behind the scenes, how much will be automated or agentic in the future? Topic 6 - In the past, we essentially had “real developers” (people who wrote code) and things like Low-Code for “citizen developers” on process tasks. Do you expect to see code assistants bringing more powerful skills to people that previously hadn't identified as a real developer? (e.g. the great idea on a napkin that turns into a mobile app)FEEDBACK?Email: show at the cloudcast dot netTwitter: @cloudcastpodInstagram: @cloudcastpodTikTok: @cloudcastpod

How can a low-code solution help you deliver a .NET app? Carl and Richard talk with Serge Sarafudinov about his Xomega project. Serge describes how Xomega uses models and templates to generate .NET code for applications for Blazor clients, WPF, and even ASP.NET Forms and TypeScript! The conversation also digs into rehabilitating existing .NET applications where new features can be added with Xomega, and then gradually convert the existing application into the model approach - and then you can change out the client if you like! There are free and paid versions of Xomega; take it out for a spin and see if you can't deliver solutions faster!

How can a low-code solution help you deliver a .NET app? Carl and Richard talk with Serge Sarafudinov about his Xomega project. Serge describes how Xomega uses models and templates to generate .NET code for applications for Blazor clients, WPF, and even ASP.NET Forms and TypeScript! The conversation also digs into rehabilitating existing .NET applications where new features can be added with Xomega, and then gradually convert the existing application into the model approach - and then you can change out the client if you like! There are free and paid versions of Xomega; take it out for a spin and see if you can't deliver solutions faster!