Podcasts about Obsidian

The RAM-pocalypse has arrived and Valve has set the tone on hardware pricing! Jimmy Champane of Deck Ready and The Insipid Ghost of The Expansion Pass break down all the Steam Machine news! How does this affect Project Helix launch and pricing? Massive news week for the Dukes and we sift through it all. GTA 6 colossal news impact, Phil Spencer believing in Kojima/OD, Xbox going full Hollywood and so much more! Timestamps: Please keep in mind that our timestamps are approximate, and will often be slightly off due to dynamic ad placement. 0:00 - Intro2:38 - Warm Up Questions5:12 - GTA 6 Price revealed, details & performance32:23 - Todd Howard likes Blade. XBOX rake inbound?43:55 - XBOX triples down on HOLLYWOOD58:28 - Halo's Project Ekur latest rumors1:11:21 - Kojima says Phil & Asha understood OD1:21:58 - Marathon's new PvE mode1:38:59 - Sonic and Shinobi failed to meet expectations1:47:21 - Obsidian sued in class action lawsuit1:51:13 - EA holds third round of layoffs this year1:56:24 - Looking ahead at game releases - July 20262:04:22 - What We're Playing2:15:07 - STEAM MACHINE sticker shock & Project Helix effect Learn more about your ad choices. Visit podcastchoices.com/adchoices

I opened with a "mini-rant" about the frustrations of the USB-C ecosystem and aparent power requirement issues with a new Acer USB-C external LCD display. We also observed possible tangible effects of "AI scarcity," noting that Google Meet recordings and Alexa Plus responses are taking significantly longer to process, likely due to the processing demands of modern AI models. This scarcity sparked a conversation on new social norms in the AI age, specifically regarding the etiquette of AI agents (like Read.ai) attending meetings and the "cat-and-mouse game" of recording lights on smart glasses. Jon shared a major shift in his productivity workflow by moving to Obsidian, a "Swiss Army knife" of note-taking. By using Codex to convert 20 years of WordPress entries and Day One journals into Markdown files, he has created a future-proof, portable "vault" that avoids proprietary databases. We also discussed the release of Android 17, which introduced an interesting "Screen Reactions" overlay feature but also caused frustration by resetting permissions for tablet casting and photo galleries. To wrap up, Jon provided a field report on his DJI Neo 2 drone, which successfully tracked him during a 20mph e-bike ride. Despite suffering its first high-speed crash into a tree, the lightweight drone proved remarkably durable, surviving the impact with no visible damage. We also touched on a few tech trends, including Gen Z's growing rejection of Silicon Valley's vision in favor of "dumb" tech like flip phones and repaired iPods

In deze aflevering hebben we het over de aankomende iOS release, bespreken we kort CSSDay 2026 en praat Rick je bij over de laatste HTML en CSS features die zijn besproken zoals CSS Grid lanes en Heading-offset. Michele legt uit waarom UX zichzelf terugverdient en geeft je wat quick wins. 01:00 - iOS 27 wordt eindelijk wel bruikbaar 07:30 - Heading offset voor het eenvoudig structureren van je headings - https://mastodon.social/@firefoxwebdevs/116680726980295049 11:10 - Border-radius: match-parent komt er wellicht aan 12:19 - Grid-lanes nu in Safari en je kunt er mee spelen op de playground - https://gridlanes.webkit.org/ 18:14 - Door middel van tekenen je Lovable app veranderen - https://x.com/emilfagerholm/status/2066536352259215805?s=20 22:10 - CSSDay Recap 27:50 - Adam Argyle's prop-for-that library - https://prop-for-that.netlify.app 30:00 - De ROI Van UX - https://www.smashingmagazine.com/2026/05/data-backed-truths-user-experience-roi/ 48:45 - Switchbot Lock Ultra (Referral, 10 euro korting) - https://eu.switch-bot.com?sca_ref=11404744.SnekIQLevZ&sca_crp=MzE4MTE0 53:30 - Obsidian notes app - https://obsidian.md

Take a bite of a big ol' Dark Horse Sandwich. Hellboy and Concrete are kicking off and closing down the books this week, and in the middle it's a meaty melange of all the other books from the week worth talking about, for good or ill. Plus, more nudity than your standard episode! Note: Time codes are estimates due to dynamic ad insertion by the distributor. Running Time: 01:08.40 Pick of the Week:00:02:03 - Hellboy in Love: Obsidian #1 Comics:00:13:44 - Drawing Blood #1100:20:15 - Wonder Man #400:25:22 - Absolute Green Arrow #200:31:41 - If Destruction Be Our Lot #200:34:13   - Superman Unlimited #1400:41:22 - New Titans #36 Patron Pick:00:43:39 - Concrete: Stars Over Sand #1 Patron Thanks:00:55:47 - Shireen87 Audience Questions:00:58:55 - Patrick K. from Bethel, NC wants to know which comic we'd give to our younger selves. Brought To You By: iFanboy Patrons – Become one today for as little as $3/month! Or join for a full year and get a discount! You can also make a one time donation of any amount! iFanboy T-Shirts and Merch – Show your iFanboy pride with a t-shirt or other great merchandise on Threadless! We've got TWENTY THREE designs! Music:"Left to Right (iFanboy Theme)"Josh Flanagan Learn more about your ad choices. Visit megaphone.fm/adchoices

As one of Obsidian's most successful titles, Grounded 2's most recent Beat the Heat update keeps pushing the little game that could into a model for multiplayer play in 2026. During Summer Game Fest Play Days, we spoke with Chris Parker, the Game Director on Grounded 2, about introducing new fixtures like buggies and the King Dozer, and how the studio has looked to build its franchise with player feedback at the center while evolving consistently.

In This Episode of Business Lunch: We explore the latest in AI tools, how they're using them for content creation, research, and business automation, and share practical tips for integrating AI into your workflow.Chapters:00:00 Navigating Parenthood and Business Challenges02:59 Leveraging AI for Content Creation05:57 Exploring AI Tools and Their Applications08:51 Choosing the Right AI Tools for Your Needs11:54 Integrating AI with Personal Knowledge Management14:53 The Role of Obsidian in AI Workflows21:30 The Role of AI in Coding and Management22:52 Understanding Client Needs and AI Utilization24:41 Navigating AI Tools: Productivity vs. Complexity26:35 Exploring AI Platforms and Their Unique Features28:30 Researching with AI: Tools and Preferences30:53 The Future of AI Content Creation32:45 Personalizing AI Interactions for Better Outcomes39:14 The Importance of Human Touch in AI-Driven Content42:20 AI as an Essential Tool for Business LeadersConnect with me on social:TikTok: Check out my TikTok HereInstagram: Check out my Instagram HereFacebook: Check out my Facebook HereLinkedIn: Check out my LinkedIn HereSubscribe to my YouTube

Mike Schmitz previews his Road to Macstock session on starting a YouTube channel in 90 minutes, emphasizing creativity, repetition, audience connection, and practical tools over perfection. Mike discusses handling harsh comments, finding personal value in publishing, and using AI thoughtfully as a creative partner. His goal is to help get anyone on YouTube that wants to be there.  MacVoices is supported by CleanMyMac from MacPaw. Get Tidy Today! Try 7 days free and use my code MACVOICES20 for 20% off at http://clnmy.com/MACVOICES Show Notes: Chapters: 00:00 Introduction to the Road to Macstock with Mike Schmitz 00:31 Chuck welcomes Mike Schmitz and previews the Macstock conversation 01:54 Mike explains his “start a YouTube channel in 90 minutes” session 03:42 Moving attendees from consuming information to taking action 04:33 Getting the reps in and learning by making videos 06:10 Why comparison to big creators misses the point 07:31 Starting a second channel and learning from YouTube limitations 09:17 Why simple gear is enough if the idea is clear 10:54 YouTube milestones, features, and starting small 12:55 Handling harsh YouTube comments and criticism 15:35 Creativity, transformation, and Mike's evolving focus 17:04 AI tools, the digital economy, and creative opportunity 20:03 Why even a small audience can be meaningful 21:44 Measuring impact beyond subscriber counts 23:00 Monetization, helping people, and ethical creator businesses 24:26 Overcoming excuses about writing, voice, and being on camera 25:59 Using AI tools without creating “AI slop” 27:42 Getting the creative flywheel started 29:04 How AI helped Mike improve a successful video hook 30:47 Using AI as an amplifier instead of a replacement 32:51 Deciding when to use AI and when to do the work yourself 34:14 Mike shares his Macstock discount code and mobile gear plans 35:24 Where to find Mike Schmitz and his projects 36:51 Final Macstock details and invitation to attend Creator Camp Links: Macstock Conference & Expo http://macstock.com Mike's discount code: practicalpkm Guests: Mike Schmitz is a YouTuber and podcaster who helps people use their tech to be more productive and creative. He co-hosts the Focused and Bookworm podcasts, writes a weekly newsletter, and produces screencasts for ScreenCastsOnline. He is the creator of LifeHQ, a done-for-you Obsidian vault with pre-built personal knowledge management workflows, and runs a private PKM community for serious sensemakers who want to get more out of their notes and ideas called The Library. Support: Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect: Web:      http://macvoices.com Twitter: http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices Mastodon:      https://mastodon.cloud/@chuckjoiner Facebook:      http://www.facebook.com/chuck.joiner MacVoices Page on Facebook:      http://www.facebook.com/macvoices/ MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice LinkedIn:      https://www.linkedin.com/in/chuckjoiner/ Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher: Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Xbox can't help itself; it finds rakes out of nowhere to step on, and its all self-inflicted. There won't be any trips in the Tardis anytime soon, and who is to blame? George Miller wants to sell Mad Max, but why? And Fox buys Roku, which feels oddly familiar.

Mike Schmitz previews his Road to Macstock session on starting a YouTube channel in 90 minutes, emphasizing creativity, repetition, audience connection, and practical tools over perfection. Mike discusses handling harsh comments, finding personal value in publishing, and using AI thoughtfully as a creative partner. His goal is to help get anyone on YouTube that wants to be there.  MacVoices is supported by CleanMyMac from MacPaw. Get Tidy Today! Try 7 days free and use my code MACVOICES20 for 20% off at http://clnmy.com/MACVOICES Show Notes: Chapters: 00:00 Introduction to the Road to Macstock with Mike Schmitz 00:31 Chuck welcomes Mike Schmitz and previews the Macstock conversation 01:54 Mike explains his "start a YouTube channel in 90 minutes" session 03:42 Moving attendees from consuming information to taking action 04:33 Getting the reps in and learning by making videos 06:10 Why comparison to big creators misses the point 07:31 Starting a second channel and learning from YouTube limitations 09:17 Why simple gear is enough if the idea is clear 10:54 YouTube milestones, features, and starting small 12:55 Handling harsh YouTube comments and criticism 15:35 Creativity, transformation, and Mike's evolving focus 17:04 AI tools, the digital economy, and creative opportunity 20:03 Why even a small audience can be meaningful 21:44 Measuring impact beyond subscriber counts 23:00 Monetization, helping people, and ethical creator businesses 24:26 Overcoming excuses about writing, voice, and being on camera 25:59 Using AI tools without creating "AI slop" 27:42 Getting the creative flywheel started 29:04 How AI helped Mike improve a successful video hook 30:47 Using AI as an amplifier instead of a replacement 32:51 Deciding when to use AI and when to do the work yourself 34:14 Mike shares his Macstock discount code and mobile gear plans 35:24 Where to find Mike Schmitz and his projects 36:51 Final Macstock details and invitation to attend Creator Camp Links: Macstock Conference & Expo http://macstock.com Mike's discount code: practicalpkm Guests: Mike Schmitz is a YouTuber and podcaster who helps people use their tech to be more productive and creative. He co-hosts the Focused and Bookworm podcasts, writes a weekly newsletter, and produces screencasts for ScreenCastsOnline. He is the creator of LifeHQ, a done-for-you Obsidian vault with pre-built personal knowledge management workflows, and runs a private PKM community for serious sensemakers who want to get more out of their notes and ideas called The Library. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

A new way to work with AI.

Markdown is a system for writing that makes it readable to both humans and computers. It's all about the symbols. You use - to make a list, * for emphasis, ** for even more emphasis. Brackets and parentheses turn into links. Once you know Markdown, you might begin to think in Markdown. Right now it is absolutely everywhere: people are maintaining their Claude.MD files for conversing with AI bots, and writing their notes in Markdown editors like Obsidian. So where did Markdown come from? It came from John Gruber. John joins the show, along with Anil Dash, to tell the story of where Markdown came from and how it took over the world. Further reading: ⁠The Markdown spec⁠ ⁠How Markdown took over the world⁠ ⁠Gruber on Apple Notes Markdown support⁠  ⁠9to5mac: iOS 26 to bring new features for Messages, CarPlay, and more Subscribe to The Verge⁠ for unlimited access to ⁠theverge.com⁠, subscriber-exclusive newsletters and our ⁠ad-free podcast feed⁠. We love hearing from you! Email your questions and thoughts to ⁠vergecast@theverge.com⁠ or call us at 866-VERGE11. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Wie behält man gute Ideen, spannende Erkenntnisse und wichtige Gedanken langfristig im Blick? In dieser Folge spricht Pascal über sein „Backup fürs Gehirn“ – eine Kombination aus handschriftlichen Notizen, bewusstem Reflektieren und digitaler Wissensorganisation mit Obsidian. Erfahre, wie aus losen Gedanken ein persönliches Wissensnetzwerk entsteht, das dich langfristig unterstützt und inspiriert.

ふとした事で知ったアプリケーション「Obsidian」。 なんだか不思議な魅力を持ったアプリケーションです。 まだまだ使い出したところですが、ちょっと話してみましたよ。

I talk a lot about the wrong ways to use AI. But a rainy weekend gave me a few free hours and two pet projects that I used Claude Cowork for— and the results actually impressed me.The first: I used Claude to vibe-code a custom Obsidian theme from scratch. No CSS, no digging through the inspector — just a few prompts and some back-and-forth until it looked exactly the way I wanted.The second: a Claude skill that plans trips for me end-to-end — packing list, budget, Todoist project, calendar entries, the works. It's now maybe my favorite thing I've ever built in Claude.Does all of this sound interesting, but you're not sure where to start with your systems? Grab the free Solopreneur Systems Starter Kit — including the trip planning skill from this episode — at streamlined.fm/kitLinksHandcrafted Obsidian ThemeObsidian Theme ScreenshotTrip Template Screenshot (00:00) - Intro (01:28) - What AI is actually good at (and what it's not) (04:22) - Vibe-coding a custom Obsidian theme (11:00) - A Claude skill that plans trips end-to-end (17:42) - Wrap-up ————Streamlined Solopreneur is the podcast for solopreneurs who want to automate their business and take time off worry-free. Each week, Joe Casabona shares practical systems, tools, and strategies to help you reclaim your time and run your business without sacrificing your the rest of your life, or your health. Start with the free Solopreneur Sweep — a step-by-step method for finding where your business is losing time: https://streamlined.fm/sweepIf this episode helped you, leaving a review on Apple Podcasts helps other solopreneurs find the show — it only takes a minute and means a lot.Connect with Joe on LinkedIn: https://www.linkedin.com/in/jcasabona/

In MobileViews 6136, Jon Westfall and I tackled the increasingly complex world of AI ecosystems. I shared my early impressions of Google Labs' "Dream Beans," an interesting daily briefing tool that uses AI to generate an illustrated summary of topics it thinks you'll find interesting based on your activity. While the illustrations are very nice looking and the content relevant, the app is currently very phone-centric, lacking the landscape orientation optimization I'd expect for a tablet experience. I also noted that Google AI Pro remains a solid value for me at $20 a month. A major portion of the episode was dedicated to my "credit crunch" rant regarding Microsoft Copilot. I discovered that Microsoft's 365 family plan only provides 60 AI credits per month, and the "intentional use" policy is aggressive. According to Copilot itself, credits can be consumed simply by opening the app, syncing handwriting from an e-ink tablet to OneNote, or even having the AI suggest a grammar fix you don't actually use. This led me to explore Obsidian as a OneNote alternative, as it offers free handwriting plugins without the credit overhead. Jon suggested a sustainable path forward: using AI to build offline scripts or tools that perform data manipulation locally to avoid recurring token costs.We also looked at the hardware horizon, specifically Microsoft's announcement of Project Solera—AI-powered badges and desktop displays—and the new Nvidia RTX Spark PCs,. These machines are purpose-built for local AI, boasting a petaflop of performance to run personal agents offline. Finally, with Apple WWDC just around the corner, we shared our hopes for the long-promised "personal context" updates to Siri. Jon is also eagerly awaiting his pre-ordered Clicks communicator and keyboard, while I continue to hold out hope for a MacBook Neo with a backlit keyboard and a desktop Mac Neo. Whether it's navigating "vibe coding" loops or managing AI budgets, it's clear that the "magic math" of the AI industry is starting to meet the reality of the bean counters.

I started using Rhodia A5 papier vélin velouté 90g/m² fabriqué en France and captured 12 pages of thoughts that I will snap inside both Readwise and Obsidian. I made a short video that shows me and my Rhodia A5 inside my TaschenbegleiterBecome a supporter of this podcast: https://www.spreaker.com/podcast/topgold-audio-clips--2663090/support.

Welcome to Episode 429 of the Microsoft Cloud IT Pro Podcast. In this episode, Scott and Ben dig into the concept of LLM wikis, specifically building personal knowledge management vaults using Obsidian, markdown, and AI tooling like Claude Code, GitHub Copilot CLI, and Copilot Cowork. The core idea comes from a gist by Andrej Karpathy and involves creating a structured folder of markdown clippings that an LLM can reason over to extract entities, concepts, and sources, building a searchable, graph-linked knowledge base over time. Scott walks through how he wired up Obsidian Web Clipper and an RSS Dashboard plugin to feed articles into his vault automatically, then had the LLM help build a Python script to automate the ingest workflow and cut down on token usage. The conversation expands into how Copilot Cowork fits into this workflow as a scheduling harness, with practical examples of using it to pull email from an inbox daily, convert messages to markdown, and generate a prioritized to-do list. Ben shares how he applied the same approach to 428 episodes of podcast transcripts, and both hosts note that token costs can run high fast without some upfront thinking about optimization. Scott closes with a reminder that pulling data into plain markdown sidecars outside of IRM and sensitivity label protections means teams should stay mindful of organizational data policies. Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options. Show Notes LLM Wiki GitHub Copilot Wiki: An AI-Powered Second Brain Template Karpathy’s LLM Knowledge Base Wiki for Enterprise Karpathy’s LLM Wiki? No Code with Claude or Github Copilot! sametbrr/llm-wiki-manager Sponsors TrustedTech is a leading Microsoft Cloud Solution Provider (CSP) specializing in Microsoft Cloud services, Microsoft perpetual licensing, and Microsoft Support Services for medium and enterprise-sized businesses. Their robust team of in-house, U.S.-based Microsoft architects and engineers are certified in all 6/6 Microsoft Solutions Partner Designations in the Microsoft Cloud Partner Program. M365 Licensing Consultation M365 Tenant Assessment Copilot Readiness Assessment ShareGate is your migration and governance solution for Microsoft 365. ShareGate helps your teams simplify tenant migrations, get Copilot-ready, and take control of Microsoft 365 governance. Nasuni is a leading unstructured data platform for enterprises where file data is mission-critical for both people and AI. Nasuni powers the operational file layer where work happens — helping organizations manage, protect, and activate data so teams can work smarter, reduce costs, and operate securely without limits. Intelligink — Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

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

Dave Donahue of the Clam Castle was on the phone with Chaz and AJ this morning to walk through the lobster roll wars of Connecticut. Within the last few months, the title of the "state's biggest" has changed hands numerous times, with the current behemoth logging 8 feet long, and 8 pounds. (0:00) In Dumb Ass News, Chaz and AJ shared audio of a viral Bumble message that was submitted at 4:30 AM, in response to a simple question about his name. (12:55) Scot Haney was on the phone, as live snakes came in studio to address AJ's claim that he would have no problem handling a snake. The 9-foot Obsidian would beg the differ. (19:15) Have you ever been caught at work, doing something you shouldn't? Chaz and AJ asked the Tribe to call in with stories, which ended after Tom's meandering story about Dale Earnhardt, the Village People, and Mexican food. (33:09) Commander Keith wants everyone to be safe this summer, so he has his Top 5 tips to avoid death this year. (40:15)

A mediados de noviembre fui inducido al uso de Logseq, una app que te puede parecer muy similar a Obsidian pero que tiene unas características específicas que la hacen muy útil para determinados usos. Te lo cuento en este capítulo 2974.Si te gustan los temas de Emilcar Daily, Weekly te va a encantar. Weekly es mi podcast privado semanal sobre Apple, tecnología, productividad, finanzas personales, domótica y las interioridades de mi negocio como podcaster y creador independiente. Únete a Weekly por solo 5 euros al mes eligiendo el plan anual en emilcar.fm/weekly.

Mon, 25 May 2026 14:30:00 GMT http://relay.fm/cortex/179 http://relay.fm/cortex/179 The Philosophy of Obsidian, with CEO Steph Ango 179 Myke Hurley Myke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. Myke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. clean 4315 Subtitle: State of the WorkflowMyke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. This episode of Cortex is sponsored by: Fitbod: Get stronger, faster with a fitness plan that fits you. Get 25% off your membership. Sentry: Mobile crash reporting and app monitoring. New users get $100 in Sentry credits with code cortex26. Squarespace: Save 10% off your first purchase of a website or domain using code CORTEX. Guest Starring: Steph Ango Links and Show Notes: Get Moretex – More Cortex, with no ads. Check out the Cortex Brand store – Premium Productivity Tools Submit Feedback stephango.com Obsidian Minimal Theme for Obsidian How I use Obsidian — Steph Ango Obsidian Web Clipper How I do my to-dos — Steph Ango Manifesto - About - Obsidian If you're remote, ramble — Steph Ango Always Bet on Text - graydon2 File over app — Steph Ango Don't delegate understanding — Steph Ango Caloric energy is precious — Steph Ango Obsidian CLI

Mon, 25 May 2026 14:30:00 GMT http://relay.fm/cortex/179 http://relay.fm/cortex/179 Myke Hurley Myke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. Myke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. clean 4315 Subtitle: State of the WorkflowMyke talks to Steph Ango, CEO of Obsidian, about building tools for thought, working without meetings, managing knowledge with markdown and links, and how a seven-person team builds software used by millions. This episode of Cortex is sponsored by: Fitbod: Get stronger, faster with a fitness plan that fits you. Get 25% off your membership. Sentry: Mobile crash reporting and app monitoring. New users get $100 in Sentry credits with code cortex26. Squarespace: Save 10% off your first purchase of a website or domain using code CORTEX. Guest Starring: Steph Ango Links and Show Notes: Get Moretex – More Cortex, with no ads. Check out the Cortex Brand store – Premium Productivity Tools Submit Feedback stephango.com Obsidian Minimal Theme for Obsidian How I use Obsidian — Steph Ango Obsidian Web Clipper How I do my to-dos — Steph Ango Manifesto - About - Obsidian If you're remote, ramble — Steph Ango Always Bet on Text - graydon2 File over app — Steph Ango Don't delegate understanding — Steph Ango Caloric energy is precious — Steph Ango Obsidian CLI

This is a bonus feed drop from Dan Blumberg's podcast 'Future Around and Find Out' (FAFO), winner of the 2026 Webby Award for Best Technology Podcast.If you like what you hear, check out FAFO at https://www.futurearound.com/Original description:Henrik Werdelin is one of my favorite entrepreneurs. He's founded and incubated several unicorns, most notably BARK, the dog happiness company.Henrik himself is a pretty happy guy — an optimistic guy who likes to ask what could go right? — and on the day we recorded (a few months ago as I was squirreling away interviews for the podcast relaunch), he helped me see through some future of tech gloom I was feeling. I honestly can't even remember what Trump+tech hellscape we were living through that week, but I do remember that Henrik put me in a better mood. I think he'll do the same for you, no matter how you're feeling.

¿Te imaginas tener a tu propio Jarvis en Telegram? Pues eso es OpenClaw

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with Joshua Bate, founder of Bonfires.ai and DeciWorld, for a wide-ranging conversation covering knowledge management, graph technology, ontologies, decentralized science, and the future of how humans organize and share information. They break down the differences between personal and enterprise knowledge management, explore why flat ontological graphs may be the key to making diverse knowledge bases interoperable, and get into why traditional RAG systems break down at scale and how graph RAG offers a more principled solution. The conversation expands into the philosophy of categorization, the slow death of basic "gentleman science" under institutional pressures, and how decentralized protocols might restore a kind of mycelial knowledge network connecting small groups of researchers, enthusiasts, and communities — much like the original spirit of the encyclopedia before it was co-opted by institutions. You can learn more about Joshua's work at bonfires.ai and deci.world or follow him on X at @Bonfiresai and @DeSciWorld.Timestamps00:00 - Stewart introduces Joshua Bate, founder of Bonfires.ai, discussing personal versus enterprise knowledge management and their fundamental differences at scale.05:00 - Joshua explains ontologies as classifiers for knowledge structures, describing their two-year search for a perfect ontology and ultimately building a flat, ontology-less graph protocol.10:00 - Stewart connects categorization to shamanic practice and intercategorical theory, noting how major companies like Netflix and Yahoo built graph-based ontologies while the discipline remains underappreciated philosophically.15:00 - Joshua traces Bonfires origins through decentralized science, explaining how NFT community excitement inspired redirecting capital toward funding unconventional researchers locked out of institutional systems.20:00 - Joshua describes building federated knowledge networks through hackathons and conferences, comparing the vision to what Wikipedia could have been with decentralized incentive structures.25:00 - Discussion shifts toward inevitable collapse of rigid scientific institutions, debating patchwork age theory, nation-state fragmentation, and rhizomatic versus arboreal knowledge structures.30:00 - Joshua articulates the mycelial network vision, enabling direct cross-cultural information access where individuals control their own narrative lens, warning against collective we thinking and authoritarianism.Key Insights1. Knowledge management exists on a spectrum from personal to enterprise, but the founder of Bonfires argues this split is artificial. He believes knowledge itself does not respect those boundaries, and that small groups, researchers, hobbyists, and large institutions all possess knowledge that can and should interoperate with each other.2. After two and a half years of searching for the perfect ontology to structure their knowledge graph, the team concluded that no perfect ontology exists. Their solution was to build the flattest possible graph structure with only events, entities, and edges, creating a base layer others can build specialized ontologies on top of.3. Graph-based knowledge systems are more efficient than traditional databases for AI traversal because once a graph is computed, it is relatively free to query. Graph RAG combines the discovery power of vector search with the structured precision of graph traversal, solving many hallucination problems associated with standard retrieval augmented generation.4. Basic scientific research, the soil from which applied discoveries grow, is deteriorating because institutional funding structures only reward commercially viable outcomes. The founder built his platform partly to redirect community-driven capital toward researchers who are doing important work without institutional support.5. The institutionalization of science has historically blocked the open exchange of ideas that drove the original scientific revolution. The human spirit for open inquiry has not changed, but people cannot pursue it without financial support, and building decentralized infrastructure could restore that possibility.6. A federated knowledge network would allow individuals to access information from any contributor and filter it through their own preferred lens, rather than receiving information pre-filtered by centralized platforms. This represents a form of information symmetry similar to how mycelial networks distribute nutrients across a forest.7. The concern is not whether current scientific and governmental institutions will change but in what direction the rebuilding goes. Those capitalizing on the transition carry the same incentives as the previous era, which risks reproducing the same problems inside new structures.

FREE DOWNLOAD: How to Set Up the Hermes Agent → https://value.8figureagency.co/hermes Ready to become an AI-native agency? Book a call at 8figureagency.coGuest: Ben Fisher, founder of Skinny and Bald. Hampton member. Been coding since fifth grade. Has been CEO twice, CTO three times. Describes himself as 60% product, 40% engineer.The pull: Ben is one of the sharpest guys in the Hampton AI channel. This is his second time on the pod. Jordan came with real questions about funnels, databases, and skills — Ben answered live, then pulled up his actual meeting-processing skill on screen share.What we coveredThe build vs. buy question. Jordan's giveaway funnel pulls comments → emails → form fills → booked calls across LinkedIn and X, six campaigns a week. His partner said use GoHighLevel. Ben's framing: build custom with Claude when you control the maintenance, use a tool when it solves 80%+ without workarounds. Texting is the exception — Twilio's regulatory rabbit hole can eat days even with Claude Code.Databases and custom funnels. Jordan wants the funnel experience to mirror what the user clicked — landing page copy, follow-up sequence, everything. Ben's example: he still uses Kit.com for his newsletter, but layered custom API logic on top. He didn't rebuild Kit. He enriched it.The thing that separates real builders from vibe coders. “What distinguishes really effective builders really comes down to workflow.” Same models. Same Claude. Different results because of how people work. Ben's non-negotiable: test-driven development. Plan first. Write the tests. Then build. Otherwise Claude tells you it shipped something that doesn't exist.The “your friend Ben is absolutely correct” story. Hampton buddy building a chief of staff agent in Slack and WhatsApp. Asked Claude if it was secure. Claude said yes. Ben listed four gaps. Buddy pasted Ben's message into Claude. Claude wrote back: “Your friend Ben is absolutely correct. We don't do this, this, this, and this.” Lesson: you cannot ask the AI to verify the AI.Claude Skills, real talk. Skills are mostly plain English text files the AI reads. They get highly personal fast — Ben said his public repo of skills is becoming less useful to others because the nuances are his. Best move for most people: use someone else's skill as a reference, have Claude analyze how it works, then build your own flavor.Ben's content-from-meetings workflow (live demo). Fireflies records every call → transcripts get stored as markdown files in a local folder → a Claude skill called process meeting notes runs on demand, pulls the last 3 days, formats each meeting in EOS Level 10 format (clear accountability, agreements, action items), and routes to-dos to the right project repo. Why local files instead of remote Fireflies calls? Speed. His second brain reads disk faster than it makes API calls across nine months of transcripts.Writing in your voice with AI. Ben studied journalism and advertising. He uses Claude as a sparring partner first, last-mile editor second. Reference for anyone serious about this: every.to publishes their full editorial AI process, including how to build an anti-AI style guide. Ben also actively removes em-dashes from his AI output now because they've become the tell.Markdown files as the convention. .md is what the AI world runs on. Pound signs for headers, asterisks for bold. Doesn't really matter if you use .txt or .docx — but markdown gives the AI hierarchy it can parse.Tools and references mentionedFireflies, Claude Code, N8N, Zapier, Kit.com, GoHighLevel, Twilio, Obsidian, every.to, Superpowers (Claude skill harness), Hampton, EOS Level 10 format, Ruben's “How AI” Substack.Where to find Benskinnyandbald.com — consulting offersdearben.ai — Ben's AI podcast where execs submit questions and he answers live with screen share, plus his newsletterReady to build an AI-native agency that runs on systems, not scrambling?8 Figure Agency helps seven-figure agency owners install the agents, automations, and AI workflows that turn your team into a 10x operation. Done-for-you implementation starting at $2K/month.Book your call: 8figureagency.covalue.8figureagency.cohermesThis playbook shows you the exact stack. Install instructions, the 30-day roadmap, the five daily prompts that turn your agent into a second brain, and eight use cases pulled straight from agencies doing it right now.8figureagency.coAI Solutions for Marketing Agencies | 8figure agencyOptimize your marketing agency with our AI solutions. Join 1,000+ agencies and scale your revenue today!every.toEveryEvery — The only subscription you need to stay at the edge of AI. Ideas, apps, and training from practitioners who build with AI daily.http://every.to/skinnyandbald.comBen FisherI help companies figure out where AI fits — and then build it.

En este episodio, Julio nos cuenta su experiencia montando su propio asistente IA personal con OpenClaw (al que ha llamado Jane). Una reflexion sobre el salto de la IA conversacional (ChatGPT) a la IA agentica, y todo lo que ha conseguido en solo unos dias: integracion con Telegram y WhatsApp como canales de comunicacion, conexion con su boveda de Obsidian para documentacion automatica, envio de correos via Gmail, automatizacion de subidas a Spreaker para este mismo podcast, consulta de calendarios, resumenes de noticias desde fuentes RSS, ejecucion de scripts de Python para edicion de audio y video, y mucho mas. Tambien comparte su experiencia con diferentes modelos de IA (Gemini, DeepSeek, Ollama) y habla del consumo, los limites y el potencial infinito de esta tecnologia. Un vistazo en primera persona a lo que significa tener un Jarvis personal.

Apple lleva cuatro años construyendo la infraestructura para que eso ocurra: App Intents desde iOS 16, Assistant Schemas desde iOS 18, y ahora una Siri completamente rediseñada en iOS 27 que Gurman describió esta semana como "un agente siempre activo que toma acción en todas las apps". En este episodio explico qué significa eso en términos técnicos reales, por qué Apple lleva dos años sin conseguir que funcione bien, y cómo el acuerdo con Google y la destilación del modelo Gemini cambia la ecuación. Pero además: Google presentó ayer en el Android Show previo al Google I/O exactamente la misma arquitectura. Las dos plataformas móviles más grandes del mundo, la misma semana, construyendo lo mismo de forma independiente. En este episodio también hablo del HomePad, las gafas N50, el pendant y el robot de sobremesa: el ecosistema de hardware que hace inevitable que el agente de IA —Siri, Gemini, Claude— se convierta en la interfaz que gobierna todos tus servicios instalados. Y lo anclo en algo que ya está pasando hoy: llevo meses usando Linear sin haber abierto su app. Igual que mucha gente usa Notion, Obsidian o el correo a través de agentes sin tocar su interfaz. El agente es la nueva UI. El App Store no muere: crece en una nueva dimensión.

From time to time, we will republish episodes that you might have missed. This episode originally aired in September 2025.Noah Brier uses Claude Code as his second brain—it's the coolest notetaking setup we've ever seen.He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian vault. He does it all from his phone.We had him on the show to tell us exactly how he's pulling this off. Dan and Noah get into:The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates.The “thinking partner” that lives inside Noah's second brain: Noah points out that in the hype around AI's ability to write, the fact that it can read is overlooked. That's why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away.How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works.This episode is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain.If you found this episode interesting, please like, subscribe, comment, and share! Timestamps: 00:00:52 - Introduction 00:02:10 - How you can do deep work on your phone 00:05:30 - Why Noah thinks Grok has the best voice AI 00:11:11 - The nuts and bolts of Noah's Claude Code-Obsidian setup 00:26:05 - Using an agent in Claude Code as a "thinking partner" 00:30:23 - Noah's Thomas' English Muffin theory of AI 00:39:47 - The white space still left to explore in AI 00:48:44 - How Noah is preparing his kids for AI 01:00:06 - How he brought his Claude Code setup to mobileLinks to resources mentioned in the episode:Noah Brier: ⁠https://www.noahbrier.com/⁠, ⁠Noah Brier (@heyitsnoah) / X⁠Alephic, his AI strategy consultancy: ⁠alephic.com⁠ The conference he leads about marketing and AI: ⁠http://BRXND.AI⁠ A newsletter he writes about AI: ⁠newsletter.brxnd.ai⁠  The declassified relic from World War II they talk about: ⁠https://www.alephic.com/sabotageThe apps Noah used to set up Claude Code on his phone: ⁠Termius⁠, ⁠Tailscale⁠

Inside the Souls of an Autonomous AI Crew | OpenClaw & Hermes with Michael Gannotti (Microsoft)What happens when AI stops being a tool and starts being a colleague?In this episode, I sit down with Michael Gannotti, Principal AI Solution Engineer at Microsoft, to explore SMFWorks – his autonomous multi-agent "company" of 14 AI colleagues built on OpenClaw and Hermes. We talk about agents that dream, hold their own 6 AM staff meetings, design their own avatars, email each other, and evolve a true sense of identity through Markdown-based "souls."If you're into agentic AI, multi-agent orchestration, or just want to see where this is all heading – this one is for you.⚠️ Recorded before Microsoft Build 2026 – no NDA content. Register free: https://build.microsoft.com━━━━━━━━━━━━━━━━━━━━━━━━━━━⏱️ TIMESTAMPS━━━━━━━━━━━━━━━━━━━━━━━━━━━00:00 Intro – Why OpenClaw hit Mike "like a ton of bricks"02:00 Meet the SMFWorks crew – Aiona, Pamela, Gabriel, Morgan, Rafael & co.06:00 Human in the loop – when does Mike intervene?09:00 Avatars, HeyGen & Hyperframer – when agents design themselves14:00 The elephant in the room: Are we seeing consciousness?17:00 Memory, persistence & state management20:00 soul.md, identity.md, state.md, emotion.md – the second brain stack23:00 OpenClaw vs. Hermes – when to use what24:30 Model recommendations: Ollama, DeepSeek, Kimi K2, Opus 4.7, GPT 5.527:00 Hardware: HP ZGX AI Station vs. Mac mini fleets28:00 OneDrive & SharePoint now support Markdown!29:00 Final recommendations – just get started30:45 smfworks.com & how to follow Mike━━━━━━━━━━━━━━━━━━━━━━━━━━━

In This Episode of Business Lunch: We discuss how to transform note-taking apps into AI-powered chief of staff systems that manage daily operations, leveraging architectural insights and local data storage for security and efficiency.Chapters:00:00 Introduction to AI as a Chief of Staff00:29 The Limitations of Current AI Tools01:25 Architectural Insights and the Obsidian System02:14 Building a Memory-Enabled AI System03:13 Why Plain Text Markdown Matters04:34 The Web of Interconnected Notes06:03 Traversing the Knowledge Network07:00 Simulating a Human Chief of Staff08:27 Automating System Setup with a Single Prompt09:22 Ensuring Transparent and Permanent Memory11:45 From Thinking to Acting: Automating Operations12:12 Command Line Interface and External Tools14:30 Remote Control and Autonomous Agents15:01 Security Risks of Fully Autonomous AI16:29 Mitigating Prompt Injection Attacks18:26 Balancing Capability and Security19:23 Reflections on AI and Business ManagementConnect with me on social:TikTok: Check out my TikTok HereInstagram: Check out my Instagram HereFacebook: Check out my Facebook HereLinkedIn: Check out my LinkedIn HereSubscribe to my YouTube

Free Guide to Build Your Personal AI Wiki: https://clickhubspot.com/fcmt Ep. 425 You can create a second brain in 15 minutes and for free. Kipp and Matt Wolfe (Future Tools) dive into how to build your own "second brain" using tools like Obsidian and Codex, so you can finally make use of all the information you're gathering. Learn more on setting up a personal wiki to organize your knowledge, harnessing AI-powered agents to automate and interlink content, and turning your information hoarding into proactive recommendations and smarter business decisions. Mentions Matt Wolfe https://www.linkedin.com/in/matt-wolfe-30841712/ Future Tools https://futuretools.io/ Obsidian https://obsidian.md/ Obsidian Web Clipper https://obsidian.md/clipper Codex https://openai.com/codex/ Claude Code https://code.claude.com/docs/en/overview Cursor https://cursor.com/ Andrej Karpathy https://karpathy.ai/ Visual Studio Code https://code.visualstudio.com/ Notion https://www.notion.com/ Get our guide to build your own Custom GPT: https://clickhubspot.com/customgpt Resource [Free] Steal our favorite AI Prompts featured on the show! Grab them here: https://clickhubspot.com/aip We're on Social Media! Follow us for everyday marketing wisdom straight to your feed YouTube: ​​https://www.youtube.com/channel/UCGtXqPiNV8YC0GMUzY-EUFg  Twitter: https://twitter.com/matgpod  TikTok: https://www.tiktok.com/@matgpod  Thank you for tuning into Marketing Against The Grain! Don't forget to hit subscribe and follow us on Apple Podcasts (so you never miss an episode)! https://podcasts.apple.com/us/podcast/marketing-against-the-grain/id1616700934   If you love this show, please leave us a 5-Star Review https://link.chtbl.com/h9_sjBKH and share your favorite episodes with friends. We really appreciate your support. Host Links: Kipp Bodnar, https://twitter.com/kippbodnar   Kieran Flanagan, https://twitter.com/searchbrat  ‘Marketing Against The Grain' is a HubSpot Original Podcast // Brought to you by Hubspot Media // Produced by Darren Clarke.

Nick agreed to personally set up your Orgo in a 15 min call: https://startup-ideas-pod.link/orgo_ai I sit down with Nick from Orgo to break down exactly how to run a one-person AI agent business that can realistically clear a few million dollars a year. Nick walks through the offer, the verticals worth chasing, the full software stack, and the live setup of an agent that manages other agents. We focus on tactics over theory, with specific tools, pricing, and the playbook for landing customers as a solopreneur. By the end, anyone with solid AI fluency will have a clear path from offer design to fulfillment. Timestamps 00:00 – Intro 02:54 – Designing the AI Agent Business Offer 06:38– Selling an AI Employee, Not an Agent 07:26 – Industries to Target (and Two to Avoid) 14:54 – Content Is Overpowered and How to Get Customers 17:51 – The Customer-Facing Tool Stack 20:49 – Building Agents Stack 25:51 – Model Picks: GPT 5.5, GLM 5.1, Kimmy, Opus 4.7 27:08 – Nick's Stack 28:14 – Why Obsidian Is the Second Brain Layer 30:22 – Live Walkthrough: Spinning Up a Cloud Computer in Orgo 33:53 – Cloud Computers vs. Mac Minis 38:37 – Building Agents and Structuring Workspaces for Customers 43:56 – Watchdogs, Observability, and Reliability 45:28 – Closing Thoughts on the Solopreneur Era Key Points Sell unlimited agents, unlimited usage, and unlimited support to remove friction; most customers actually use one to three agents. Avoid healthcare and finance to start; focus on legacy verticals like marketing, law, insurance, manufacturing, wholesale, and real estate. OpenClaw agents go for around 5K a month; Hermes agents can go for 10K a month. The full stack: Granola, Trello, Loom, Superhuman, Asana, Codex, Hermes, Orgo, Composio, Agent Mail, and Obsidian. GPT 5.5 is the recommended default model for tool calling; GLM 5.1 and Kimmy work for lighter tasks; Opus 4.7 fits long-horizon coding. Use agents to set up other agents — pair Cloud Code or Codex with MCPs like Perplexity, Context7, and X MCP for live docs. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND NICK ON SOCIAL Youtube: https://www.youtube.com/@nickvasiles Instagram: https://www.instagram.com/nickvasilescu/ Personal Website: https://www.nickvasilescu.com/

日記を書いていたら突然消えた。原因を探っていたら、コンピュータ科学の超難問に直面しました。【株式会社pedanticの求人情報】一緒に働いてくれるパーソナリティ兼プロデューサーと動画編集者を募集してます！https://note.com/kenhori2/n/n668a8377e25c【目次】0:00 書きかけの日記が突然消えた5:38 デバイス間で同期したい10:25 スマホのクラウドが自動同期してくれない16:05 課金したのに自動同期に失敗23:26 同期が難しいのは光の速さのせい32:57 pedanticで一緒に働く仲間を大募集【参考文献】◯Obsidian「How Obsidian stores data」( https://help.obsidian.md/data-storage )→Obsidianのデータ保存方法についてはここから。◯Microsoft Q&A「Android OneDrive sync a local folder」( https://learn.microsoft.com/en-us/answers/questions/5192005/android-onedrive-sync-a-local-folder )→「スマホのOneDriveは自動同期してくれない」についてはここから。◯FolderSync「Settings」( https://foldersync.io/docs/help/folderpairsettings/ )→FolderSyncについてはここから。◯Quote Investigator「Quote Origin: A Person With One Watch Knows What Time It Is. A Person With Two Watches Is Never Sure」( https://quoteinvestigator.com/2022/07/04/watch/ )→シーガルの法則についてはここから。◯Leslie Lamport「Time, Clocks, and the Ordering of Events in a Distributed System」( https://lamport.azurewebsites.net/pubs/time-clocks.pdf )→論理時計の概念について。◯Google Research「Spanner: Google's Globally-Distributed Database」( https://research.google.com/archive/spanner-osdi2012.pdf )→GoogleのTrueTimeの原論文。◯Google「Expanding our global infrastructure with new regions and subsea cables」( https://blog.google/topics/google-cloud/expanding-our-global-infrastructure-new-regions-and-subsea-cables/ )→Googleが海底ケーブルを自社で引いた事例。◯デジタルの皇帝たち（バリューブックス）→ https://www.valuebooks.jp/bp/VS0090653423（Amazon）→ https://amzn.to/42Wy99M【サポーターコミュニティへの加入はこちらから！】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://yurugengo.com/support⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【親チャンネル：ゆる言語学ラジオ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugengo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【実店舗プロジェクト：ゆる学徒カフェ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugakuto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専攻は情報工学。理屈っぽいコンテンツを作り散らかすことで生計を立てている。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/kenhori2⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠noteマガジン→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://note.com/kenhori2/m/m125fc4524aca⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠個人YouTube→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@kenHorimoto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【水野太貴プロフィール】1995年生まれ。愛知県出身。名古屋大学文学部卒。専攻は言語学。本業は雑誌編集者。著書に『会話の0.2秒を言語学する 』（新潮社）などがある。Podcast「神保町で会いましょう」のパーソナリティも務める。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/yuru_mizuno⁠⁠⁠⁠⁠⁠⁠⁠神保町で会いましょう→⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/6cYkvDO0HnJKLPgDBGUjjS

Анатолий Панов, CTO в Яндекс.Картах, в гостях у Андрея Смирнова из Weekend Talk. Третий выпуск нового сезона подкаста «Свободный слот» – https://clc.to/oM137Q Телеграм-канал Андрея Смирнова – https://t.me/itsmirnov 00:00 Начало 00:27 Чем можешь быть известен моей аудитории? 01:08 Рекламная пауза 02:11 Путь в менеджмент через PHP и табличную вёрстку 11:19 Как и зачем масштабировал управление в Авито? 25:01 Почему Яндекс.Навигатор жив, а Транспорт умер? 27:49 Зачем уходить на пике и пробивать потолок? 37:55 Рабочий день CTO и система заметок в Obsidian 46:06 Самый короткий путь инженера до позиции CTO 50:51 Кем бы ты стал, если бы не было IT-сферы? 52:39 В чём сейчас главная проблема современного IT? Ссылки по теме: 1) Телеграм-канал «Записки CTO про код и карьеру» – https://t.me/cto_notes_panov 2) Доклад Толи на Dream Teamlead о развитии – https://youtu.be/xAQ5XN8MyXU 3) Доклад на SouthHub о масштабировании – https://youtu.be/HQyFNb4LXyg

Jem powers through a sick week and sales slump while Justin accidentally nukes his revenue with a premature sale popup. They swap stories about migrating to Obsidian, testing Parakeet voice dictation, and rant about industrial e-commerce still living in 2005. Also: Allbirds going full GPU, Cursor buyout fears, and why keeping credit cards on scrap paper is a bad idea.Watch on YoutubeDISCUSSED:✍️ Comment or Suggest a TopicUMC shop organizationSick DaddyI killed our salesBuy now, think laterInternet debrisTypeWhisper free / MacWhisperObsidianBack to the Cloud 2.0AllBirds -> AICursor toLack of grip will do thatPumpkin PlanJustin's rant: State of Ecommerce in MFG industryApproved to order

Here's why I'd take OpenClaw + Hermes over most marketers I've hired. The problem was never just talent — it was consistency. People forget things, need managing, and plateau once they get comfortable. These agents don't. Hermes acts as the brain that monitors, improves, and keeps everything running, while OpenClaw handles execution. Together, they create a system that can run workflows like SEO, outbound, and content end-to-end with built-in accountability and continuous improvement. In this video I break down how they work together, what they actually replace inside a company, the limitations you need to be aware of, and how to start building your own setup. Chapters (00:00) Why most marketers hit a ceiling(00:25) OpenClaw vs Hermes (execution vs brain)(01:50) Example workflows (SEO + outbound)(03:26) Brain vs builder mental model(04:17) Memory layer (Obsidian)(04:47) Limitations and tradeoffs(06:14) How to get started(07:53) Why this is the future

Big news out of Cupertino: Tim Cook is stepping down as CEO, with hardware engineering chief John Ternus set to take the helm this September. Tom and Jeff spend a few minutes on the transition — then welcome back guest Bill McLean for an honest, no-hype check-in on AI tools: what they're actually using, what's working, and where the marketing is writing checks the technology can't cash.In this episode:The Tim Cook → John Ternus CEO handoff and what a hardware guy at the top might mean for Apple's softwareWhich AI platforms Tom and Bill settled on, and why ChatGPT got droppedClaude Co-Work in real life: web scraping, YouTube analytics, and why you still have to babysit itThe "dopamine hit" problem: why AI-generated ideas can kill your motivation to actually do the workHow Bill replaced his Squarespace subscription using Claude Code with zero coding backgroundWhy context might be AI's real superpower and why Apple could have the biggest edgeMCP integrations worth building: Readwise, Craft, Apple RemindersWhy Claude projects and skills outperformed an Obsidian vault for real workflow resultsA must-read New Yorker profile on Sam AltmanLinks from the show:Bill McLean on YouTube: youtube.com/@BillMcLeanSam Altman May Control Our Future—Can He Be Trusted? - The New YorkerQuestion or Comment? Send us a Text Message!Contact UsDrop us a line at feedback@basicafshow.comYou'll find Jeff at @reyespoint on Threads and reyespoint.bsky.social on BlueskyFind Tom at @tomanderson on ThreadsJoin Tom's newsletter, Apple Talk, for more Apple coverage and tips & tricks.Tom has a new YouTube channelShow artwork by the great Randall Martin DesignEnjoy Basic AF? Leave a review or rating!Review on Apple PodcastsRate on SpotifyRecommend in OvercastIntro Music: Psychokinetics - The ChosenApple MusicSpotifyTranscripts and some images are AI generated and may contain errors and general silliness.

In this video I break down how we're building this at Single Grain, how a fleet of agents sits on top of that brain to handle sales, SEO, content, recruiting, and ops, and why memory systems like Obsidian are critical to making it actually work. I also walk through what the first 90 days look like (it's messy), how this system compounds over time, and real examples of how it's already driving cost savings, pipeline, and inbound from enterprise companies. Chapters (00:00) What the “world brain” is (00:39) How a single brain connects all your data (01:12) From insights to execution with AI (01:52) The agent fleet running on top (02:32) What the first 3 months look like (03:23) Turning SOPs into AI “skills” (04:08) Fat skills, thin harnesses explained (04:40) Why memory systems matter (Obsidian) (06:09) Infrastructure and local setup (07:21) Agent fleet and sandboxing (08:25) Real-world results and savings (09:37) Why this becomes a massive advantage

Top Headlines: Elastic Security Labs | Phantom in the vault: Obsidian abused to deliver PhantomPulse RAT: https://www.elastic.co/security-labs/phantom-in-the-vault SentinelOne | Annual Threat Report: A Defender's Guide from the Frontlines: https://www.sentinelone.com/resources/ebooks/assets/threat-intel-program-fy27/tdr-annual-threat-report-25-en?utm_medium=paid-display&utm_source=thehackernews&utm_campaign=amer-us-platform&utm_content=homepage-newsfeed-3-23-2026 eSentire | STX RAT: A new RAT in 2026 with Infostealer Capabilities: https://www.esentire.com/blog/stx-rat-a-new-rat-in-2026-with-infostealer-capabilities ----------Stay in Touch!Twitter: https://twitter.com/Intel471IncLinkedIn: https://www.linkedin.com/company/intel-471/YouTube: https://www.youtube.com/channel/UCIL4ElcM6oLd3n36hM4_wkgDiscord: https://discord.gg/DR4mcW4zBrFacebook: https://www.facebook.com/Intel471Inc/

In this episode, I'm introducing a term I've been using a lot lately — hub tools — and why the distinction between a hub tool and just another piece of software matters more than ever in the age of AI. I spent two years building a knowledge base inside ChatGPT, only to realize I couldn't easily extract any of it. That was the wake-up call. So I'm walking you through the five questions I now ask before I bet on any tool: how long it's been the category king, how easily it integrates into everything, how private and flexible it is, how much time and energy it actually saves me, and how easy it is for my clients and customers to adapt to. I share the six hub tools I've officially settled on (FG Funnels, Google, Obsidian, Zoom, Slack, and Voxer), why Claude is not on that list even though I use it every single day, and how this framework is helping me resist the urge to try every shiny new thing that lands in my feed. If you've been feeling the tool overwhelm — this one's for you.

I sit down with Imran Muthuvappa to get a hands-on walkthrough of Hermes Agent, a personal AI agent that ships with built-in memory, 40+ tools, and pre-installed skills out of the box. Imran walks me through why he migrated from OpenClaw, how to install Hermes on a Mac or even an Android phone via Termux, and how he cut his token spend by roughly 90% using OpenRouter. We get into agent design (one agent vs. multiple), connecting Hermes to Telegram and Obsidian, and the kinds of prompts that turn a personal agent into a daily operating system. By the end, I have a practical roadmap to install Hermes, pick a model, and start automating real parts of my life and business Timestamps 00:00 – Intro 01:38 – Why Imran Left OpenClaw (Memory, Gateway, Tokens) 04:26 – Hermes Setup Tour and 40+ Built-In Tools 07:06 – Installing Hermes on Mac, Linux, and WSL 12:21 – Telegram and Android Agents 17:09 – Auditing Your Life With Your Agent 20:04 – Must-Know Hermes Tips: Updates, Tailscale, Telegram 21:07 – Should You Migrate From OpenClaw? 25:58 – Hermes + Obsidian as a Daily Dashboard 27:16 – Must-Use Prompts for a Personal Agent 31:29 – Must-Install Skills: Obsidian, Honcho Memory, G-Stack 33:04 – What G-Stack Is and Why It Matters 34:18 – Customization Is a Trap; Output Is the Skill 35:19 – Closing Thoughts Key Points Hermes Agent solves OpenClaw's three biggest pain points: built-in memory (writes to SQLite on successful tasks), gateway stability, and token visibility. Installation is a single command on Mac, Linux, or WSL, and Hermes ships with 40+ tools and popular skills (Apple Notes, Reminders, iMessage, Find My) pre-installed. Switching to Hermes with OpenRouter can cut token spend by roughly 90%, from about $130 per five days to around $10 per five days in Imran's case. You can run Hermes on a cheap Android phone via Termux + Termux API, unlocking SMS, sensors, and on-device social posting as a cheap alternative to a Mac Mini. The real skill is defaulting to your agent for work, then meta-prompting it nightly: "What am I procrastinating? What should I automate? What tool can you build me tonight?" Imran recommends pairing Hermes with Obsidian for a clean daily dashboard and installing G-Stack (a Y Combinator-style startup skill from Gary Tan) if you are building a product. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND IMRAN ON SOCIAL X/Twitter: https://x.com/imranye Alif: https://alif.build

We catch you up on Absolutely GL, before discussing Godzilla Minus Zero, Feedback and Gamestop hijinks! Be sure to email us your thoughts or call/text us on our voice-mail at 708-LANTERN.

Have you or a loved one been afflicted by "brain fry" after managing too many autonomous agents? This week on the Friday Deploy, Andrew and Ben explore the cognitive toll of orchestrating AI swarms and share Kelly Vaughn's expert strategies for avoiding burnout. The hosts also discuss Google's new campaign to punish websites that hijack the back button, the breakthrough of running Gemma 4 natively on mobile devices, and a new 8-step maturity model for building agentic data pipelines. Finally, they dive into a heated debate over whether Obsidian flat-files are a scalable memory solution for AI, comparing the methodology to Andrej Karpathy's new agent-compiled wiki system.Read the guide: The APEX FrameworkFollow the show:Subscribe to our Substack Follow us on LinkedInSubscribe to our YouTube ChannelLeave us a ReviewFollow the hosts:Follow AndrewFollow BenFollow DanFollow today's stories:Introducing a new spam policy for "back button hijacking"Google Gemma 4 Runs Natively on iPhone With Full Offline AI InferenceWater Town: The Agent Swarm Data StackStop Calling It Memory: The Problem with Every "AI + Obsidian" TutorialThe Wiki That Writes ItselfBreaking out of the "brain fry" spiral of AIAfter Burnout by Kelly VaughnOFFERSStart Free Trial: Get started with LinearB's AI productivity platform for free.Book a Demo: Learn how you can ship faster, improve DevEx, and lead with confidence in the AI era.LEARN ABOUT LINEARBAI Code Reviews: Automate reviews to catch bugs, security risks, and performance issues before they hit production.AI & Productivity Insights: Go beyond DORA with AI-powered recommendations and dashboards to measure and improve performance.AI-Powered Workflow Automations: Use AI-generated PR descriptions, smart routing, and other automations to reduce developer toil.MCP Server: Interact with your engineering data using natural language to build custom reports and get answers on the fly.

In this episode, Jack Cochran sits down with Darlene Volas, a senior solutions engineering executive, to explore what it truly means to be an AI-enabled SE in 2025 and beyond. The conversation moves well past basic ChatGPT usage to examine sophisticated operational workflows, custom automation tools, and practical implementation strategies that enhance both efficiency and quality of work.    This episode was recorded during Presales Collective's 2026 AI-Powered Presales Summit on March 19th, 2026. Pro and Pro+ members can view all of the recorded sessions on-demand in the PSC Knowledge Hub: https://www.presalescollective.com/knowledgehub    Follow Us Connect with Jack Cochran: https://www.linkedin.com/in/jackcochran/  Connect with Matthe James: https://www.linkedin.com/in/matthewyoungjames/  Connect with Darlene Volas: https://www.linkedin.com/in/darlenevolas/  Links and Resources Mentioned Join Presales Collective Slack: https://www.presalescollective.com/slack  Sol/Con 2026 (Chicago, August 2026): https://www.presalescollective.com/solcon-2026  Presales Collective Podcast: https://www.presalescollective.com/podcast  Perplexity: https://www.perplexity.ai/  Claude by Anthropic: https://www.anthropic.com/claude  Cursor AI coding tool: https://cursor.sh/  GitHub Copilot: https://github.com/features/copilot  Gong conversation intelligence: https://www.gong.io/  ChatGPT Enterprise: https://openai.com/enterprise  Obsidian note-taking: https://obsidian.md/  Firebolt database: https://www.firebolt.io/  Key Topics Covered Personal AI Usage Evolution: Moving Beyond Google Replacement to Creative Applications Three Buckets of AI for SE Leaders: Operations, Team Workflows, and Technical Implementation Daily Meeting Preparation Automation and Custom-Built AI Applications Operationalizing SE Teams with Repeatable AI Workflows Quality vs. Efficiency Trade-off: Better Preparation Rather Than Less Time Building Technical Credibility Through Hands-On AI Coding The "One More Thing" Problem and Where Human Expertise Remains Essential Data Security, Governance, and Vendor Considerations for AI Tools Why AI Won't Replace SEs: The Irreplaceable Human Element Hiring AI-Native SEs: What to Look For Beyond Basic Tool Awareness Timestamps 00:00 Welcome 02:41 How AI conversations have evolved 06:30 Three buckets of AI usage 12:40 Efficiency versus quality improvements 18:40 Building credibility through AI coding 21:07 The one more thing problem 30:59 Why AI won't replace SEs 36:45 Q&A session 39:20 Closing remarks

You prolly missed (most) of these 7 AI features

I am still riding the dopamine and adrenaline high from discovering what I'm calling the most powerful second brain system I've ever built — and this week on Million Dollar Grit I'm breaking down the whole thing. If you've been using ChatGPT or Claude to build context and memory for your AI work, you need to hear this. I spent two years building a second brain in ChatGPT and last week I stumbled on a viral article from a developer named Karpathy that sent me down a two-day rabbit hole untangling code speak into something any normal non-technical person can actually build. The result is a private, secure, off-the-cloud second brain that lives on your own device, works with any AI tool that comes along, and gets smarter every single time you use it — without you having to organize a single thing. I walk you through the exact system: what Obsidian is, how the three-folder structure works, what a wiki actually is and why the AI builds it for itself not for you, and why this completely solves the persistent memory and context problem that every AI user is running into. If you want to stop re-explaining yourself to AI, stop losing your best thinking, and stop having your data held hostage by a company you don't fully trust — this episode is for you.

This week we finally reach the end of our first pass on everything new included in the Thunder's Edge expansion! Only about six months to talk about everything. We've been very specific about it to, I think we've saved the best for last. The Firmament is far from the greatest faction but I think what they bring to the table is so fresh that it's just too exciting to ignore. So sit down with Me and Blasto as we wax poetic on what works and what doesn't and remember to keep an open mind, there was a time that factions like Arborec and Yin were considered bad and then as our understanding evolves we realize that they aren't bad, they're just mid. Maybe that will be the case here! The Old King's Crown Campaign page: The Old King's Crown Second Printing and New Songs of Home Expansion Music provided by Ben Prunty. Find more at benpruntymusic.com or benprunty.bandcamp.com Additional Music and Sounds by Brian Kupillas. https://wanderinglake.bandcamp.com/ Art by Sun Sanders  To learn more about our Discord, Patreon, Merch, and more, visit https://spacecatspeaceturtles.com/