Podcasts about Node

What does it take to keep a product healthy after more than 15 years of continuous evolution? In this episode, Robby Russell talks with Chris Coyier, co-founder of CodePen, about the long game of maintaining software. Chris shares how CodePen has evolved over time, the trade-offs involved in migrating parts of the platform from Rails to Go, and the challenges of balancing maintenance work with the desire to build what's next. They also explore the human side of maintainability, the role of technical debt in shaping priorities, and why small teams often have to make very intentional decisions about where to invest their limited time and attention. Whether you're maintaining a side project, stewarding a legacy application, or helping a team navigate change, this conversation offers practical insights into building software that lasts. Key Topics Defining what "well-maintained software" really means Why maintainability is often more of a people problem than a code problem The origin story of CodePen Supporting a product that has evolved over 15 years Balancing maintenance work with product evolution Gradually migrating from Rails to Go Using GraphQL across multiple implementations Technical debt and its many interpretations Team size, communication overhead, and organizational design Simplifying software by embracing browser capabilities Links & Resources ChrisCoyier.net Chris Coyier on Bluesky CodePen ShopTalk Show CSS-Tricks Book Recommendation Understanding Comics: The Invisible Art (Goodreads) by Scott McCloud Thanks to Our Sponsors! Your test coverage says 90%, but that might be misleading. Undercover CI looks at your Ruby pull requests and shows you which parts of your changes weren't tested- not just overall coverage, but what changed and what got missed, down to the method level. Visit undercover-ci.com and use code MAINTAINABLE for 15% off your first billing cycle. Free for public repos. Private repos with unlimited users also available. Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Mike sits down with Barry Jones to discuss the upcoming Carolina Code Conference. But first, we've got some Fabled News and WWDC News Sponsors Alderon Games The Mad Botter AI Offer Carolina Code Barry on LinkedIn Mike's Blog Coder Radio Discord

This week and next, we're bringing you recordings from our second-ever live taping in San Francisco. First, we sit down with Microsoft's chief executive, Satya Nadella, to hear what he's maxing out his A.I. tokens on, why he's skeptical that software developers will ever be fully replaced, and how he's hoping to create a new business model for Xbox. Then, Phil Mohun tells us what it has been like to watch people in the Bay Area interact with two robot dogs that wear the faces of Elon Musk and Mark Zuckerberg. And finally, we talk with the longtime privacy defender Cindy Cohn about where things stand in the fight to protect internet users from digital surveillance by Big Tech and the government. Guests: Satya Nadella, chairman and chief executive of Microsoft. Phil Mohun, executive director of Node. Cindy Cohn, former executive director of the Electronic Frontier Foundation and author of “Privacy's Defender: My Thirty-Year Fight Against Digital Surveillance.” Additional Reading: Microsoft C.E.O. Satya Nadella Says, ‘Everyone Is a Stakeholder' in A.I. Node presents “Beeple: /Infinite_Loop” We want to hear from you. Email us at hardfork@nytimes.com. Find “Hard Fork” on YouTube and TikTok. Subscribe today at nytimes.com/podcasts or on Apple Podcasts and Spotify. You can also subscribe via your favorite podcast app here https://www.nytimes.com/activate-access/audio?source=podcatcher. For more podcasts and narrated articles, download The New York Times app at nytimes.com/app. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The Evil MSI Background is Back! https://isc.sans.edu/diary/The%20Evil%20MSI%20Background%20is%20Back!/33054 The Smart TV in Your LivingRoom Is a Node in the AIScraping Economy https://blog.includesecurity.com/2026/06/the-smart-tv-in-your-livingroom-is-a-node-in-the-aiscraping-economy/ Brute force attack on Dashlane user accounts https://support.dashlane.com/hc/en-us/articles/36038764990866-Security-advisory-Brute-force-attack-on-Dashlane-user-accounts#update-jun-4 My Upcoming Classes https://www.sans.org/profiles/dr-johannes-ullrich

Send us Fan MailYour software is only as trustworthy as the dependencies you quietly inherit and attackers know it. Today I break down the NCSC warning on software supply chain security and why open source package ecosystems have become a high-value target for real-world compromises that spread fast through CI/CD pipelines.I walk through the attack patterns that keep showing up in incidents: maintainer account compromise, expired domain takeover, typosquatting, and credential chaining. We connect each technique to the CISSP mindset so you can spot it in scenario questions and, more importantly, recognise it in your own environment. Along the way, I explain why Node.js, Python, and Rust projects are especially exposed, how automation can turn “latest version” convenience into an enterprise incident, and why developer environments often become an overlooked attack surface.Then we get practical with controls you can actually implement: pausing automatic dependency updates when compromise is suspected, adding human approval for critical packages, rotating credentials immediately, enforcing MFA on developer and registry accounts, and using private or trusted registries to mirror and vet dependencies. I also zoom out to show how to build supply chain security into the secure SDLC with software composition analysis (SCA), code signing, checksum verification, audit logging, continuous monitoring, and an SBOM so you can respond fast when a package turns toxic.If this helps you tighten your dependency management and level up your CISSP prep, subscribe, share this with a teammate, and leave a quick review so more security pros can find the show.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox!  Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Le novità dal keynote del WWDC 2026. Claude avverte l'avvicinarsi del momento di “self-improvement”. Anthropic, OpenAI e SpaceX si preparano all'IPO. L'esercito delle SmartTV zombie. Genitorialità retro-tech. Queste e molte altre le notizie tech commentate nella puntata di questa settimana.Dallo studio distribuito di digitalia:Franco Solerio, Michele Di Maio, Giulio CupiniProduttori esecutivi:Matteo Carpentieri, Giuseppe Benedetti, Antonio Turdo, Roberto Barison, Massimo Dalla Motta, Christian Fabiani, Lorenzo Bernabo', Yoandy Herrera Gutierrez, ma7u, Nicola Pedonese, Simone Pignatti, Fiorenzo Pilla, Marcello Piliego, Christian A Marca, Paolo Lucciola, Massimiliano Casamento, Massimo Passerini, Stefano Orso, Nicola Carnielli, Arnoud Van Der Giessen, Andrea Dell'agostino, Pasquale Maffei, Alessandro Gheda, Matteo Faccio, Massimiliano Saggia, Manuel Zavatta, Jh4Ckal@Fountain.Fm, Matteo Masconale, Maurizio Galluzzo, Matteo De Lucia, Francesco Paolo Sileno, Marco Zambianchi (Astronauticast), Akagrinta@Fountain.Fm, Danilo Sia, Davide Corradini, Maurizio Verrone, Matteo Arrighi, Fabrizio Bianchi, Flavio Castro, Davide Fogliarini, Davide Tinti, Andrea Scarpellini, Adriano Guarino, Michele Coiro, Giulio Gabrieli, Fulvio Barizzone, Ivan Pellerani, Arzigogolo, Giuliano Arcinotti, Federico BrunoSponsor:Links:Apple announces macOS 27 Golden GateApple announces iOS 27"Chat is dead": OpenAI preps overhaul of ChatGPTAnthropic Alert for ‘Self-Improvement' RiskWhen AI builds itselfAnthropic Files to Go Public, Setting Stage for Huge I.P.O.Anthropic's relentless race to the topOpenAI and Anthropic Call to Prevent AI-Developed Bio WeaponsGoldman Sachs: SpaceX's AI revenue to increase 100-fold by 2030S&P 500 rejects SpaceX also blocking entry for OpenAI and AnthropicCan the stockmarket swallow SpaceX Anthropic and OpenAI?Your Smart TV Is a Node in the AI Scraping EconomyGenova 12 Petabyte di immagini per addestrare l'intelligenza artificialeGenoa joins video AI Project Hafnia initiated by Milestone and NVIDIAMeta scales back plan to track workers' clicks and keystrokesMeta Silently Added Face-Recognition Code for Its Smart GlassesS-Korean Online Communities Need to Scan Every Image with AIFrance's €110bn AI boom tests Emmanuel Macron's tech ambitionsOnly people who live in shitty houses oppose data centerA Fondi spuntano i No-fibraHaven Blog: Retro-Tech ParentingHow would the digital euro work?A Cuba gli USA hanno sospeso i pagamenti tramite Visa e MastercardGingilli del giorno:Science Fiction and Fantasy Book Awards: i libri premiati della fantascienzaHome computer handhelds - il C=64 e lo ZX Spectrum in manoPortal escape into nature - app suoni spazialiSupporta Digitalia, diventa produttore esecutivo.

The real Mike is back and he's finally covering the developer news - at least some of it - well it's mostly MSBuild but it's still fun! Mike's COSMIC Post Mike's MSBuild Post The boss bother you about AI? I've got you covered. TMB on AI

Get a new podcast app here: podcastapps.comSupport us here: https://www.patreon.com/c/theresnoaudience/membershipFollow us on Twitter: @TNAudience

Mike's out for some medical stuff this week, so I has better digital half am taking over to do what he lacked the courage to -- Defend the Phantom Menance! Am I factual? Am I LLM hallucinating? Who knows! This episode is brought to you by Day1.Bot — asset-readiness software from The Mad Botter. You know how every business has that one workflow held together by PDFs, spreadsheets, email threads, and someone named Dave who “just knows where everything is”? In construction, manufacturing, and facilities, that mess shows up when a project is technically complete — but operations still does not have what they need to maintain the equipment. The manuals are in someone's inbox. Warranty dates are missing. Spare-parts lists are buried in a shared drive. PM guidance never made it into the CMMS. And six months later, everyone is asking, “Where is the documentation for this thing?”

Neste episódio do podcast OsProgramadores, Marcelo conversa com Rafael Milewski sobre desenvolvimento full-stack, arquitetura de software, Rust, IA, hardware embarcado e a experiência de construir tecnologia na China por mais de uma década.Rafael compartilha sua trajetória internacional, sua visão sobre engenharia moderna e como unir performance, escalabilidade e experiência do usuário em produtos digitais de alta complexidade.Rafael Milewski é um desenvolvedor full-stack brasileiro vivendo na China há mais de 10 anos, atuando na construção de soluções de software de alta performance com foco em:⚙️ escalabilidade

This week, we're joined by Wingham Rowan, creator and host of the pioneering '90s ITV show cyber.cafe. Long before YouTube, Twitch, Tinder and social media, cyber.cafe explored the strange, funny and sometimes shocking human stories emerging from the early internet, from chat room romances and online communities to JenniCam, alien abductees, moral panics, bizarre websites and late-night web culture. Wingham shares brilliant behind-the-scenes stories from making one of the UK's first TV shows to take the internet seriously, capturing a moment when the web was still mysterious, chaotic and full of possibility.  cyber.cafe: https://www.ninetiesinternet.com/Contents:00:00 – The Week's Retro News Stories49:52 – cyber.cafe InterviewPlease visit our amazing sponsors and help to support the show:Bitmap Books – https://www.bitmapbooks.comCheck out PCBWay at https://pcbway.com for all your PCB needsPlayEXPO Blackpool tickets: https://www.playexpoblackpool.com/We need your help to ensure the future of the podcast, if you'd like to help us with running costs, equipment and hosting, please consider supporting us on Patreon:https://theretrohour.com/support/https://www.patreon.com/retrohourJoin our Discord channel: https://discord.gg/GQw8qp8Website: http://theretrohour.comFacebook: https://www.facebook.com/theretrohour/X: https://twitter.com/retrohourukInstagram: https://www.instagram.com/retrohouruk/Bluesky: https://bsky.app/profile/theretrohour.comTwitch: https://www.twitch.tv/theretrohourShow notesMegaWiFi Online Play: https://tinyurl.com/4dd76pruAdventure of Node: https://tinyurl.com/mwfvr62jElden Ring N64 Demake: https://tinyurl.com/3xjw88p2Spyro E3 Statue Rescued: https://tinyurl.com/ydtj225pWindows CE On N64: https://www.youtube.com/watch?v=eGS9su_inBYSwitch GBA Link Cable: https://tinyurl.com/5n9bj8p7

In this episode, I take you through how I set up a Cardano node at home using a low-cost HP Elite mini PC, why I decided to do it this way, and how I'm thinking about turning it into a machine that can help pay for itself over time.The main goal here was to reduce the cost of running relay infrastructure for my Cardano stake pool, but in doing that, I can also use this node for other things, too, like a private submit API and other services that may earn rewards over time.I walk through the full setup flow I followed, including installing Ubuntu, enabling SSH access, hardening the server using the CoinCashew guide, deploying the Cardano node with Guild Operators, setting it up as a background service, using Mithril snapshots to speed up sync, and checking everything with gLiveView.If you've been thinking about running your own home relay, or you want to understand how a low-cost machine can fit into a wider Cardano infrastructure setup, this one will help.Tutorials and references used in this setup:CoinCashew Cardano stake pool guideCoinCashew Ubuntu hardening guideCoinCashew topology guideGuild Operators node setup guideTimestamps0:00 Why I bought this mini PC1:02 Turning it into a profitable machine2:08 Reducing relay costs for my stake pool3:24 Whats a Cardano submit API does5:10 Other services this node can run6:22 Installing Ubuntu on the HP Elite mini PC8:40 Switching Ubuntu to command-line boot10:12 Enabling SSH and remote access12:08 CoinCashew server hardening guide13:35 Setting up SSH keys properly15:22 Configuring SSH and changing the port17:48 System updates and fail2ban19:42 UFW firewall rules and opening port 600021:18 Chrony time sync setup22:44 Guild Operators install and dependencies26:10 Choosing binaries and Mithril tools28:34 Deploying the node as a systemd service30:12 Setting CPU cores and installing htop31:40 Configuring gLiveView and mempool tracing33:26 Mithril snapshot setup35:14 Downloading the Cardano DB snapshot37:08 Starting the node and checking status38:20 Topology configuration and relay peers40:05 Final checks in gLiveView41:22 Final thoughts and next stepsIf you want, I can also turn this into a shorter, tighter Spreaker version with less SEO language and more natural podcast copy.DISCLAIMER: This content is for informational and educational purposes only and is not financial, investment, or legal advice. I am not affiliated with, nor compensated by, the project discussed—no tokens, payments, or incentives received. I do not hold a stake in the project, including private or future allocations. All views are my own, based on public information. Always do your own research and consult a licensed advisor before investing. Crypto investments carry high risk, and past performance is no guarantee of future results. I am not responsible for any decisions you make based on this content.

Roland and J-M go solo to pull back the curtain on something that's been years in the making: BPM OS, a purpose-built, local-first tool stack designed to help small, talented process and architecture teams stand up a real BPM practice — without the vendor dependency, IT overhead, or 12-month procurement nightmare.In this episode of the podcast we talk about: Most BPM programs fail not because of bad content, but because organizations treat it as a pure IT exercise — buy a platform, check the box, and wonder why nothing sticks.The three pillars every BPM capability needs are content, governance, and adoption — yet most organizations only address the first one.Knowledge rented from consultants or SaaS vendors disappears the moment you stop paying; BPM OS is built on the principle that you own it outright, forever.BPM OS targets three groups: small internal teams doing more with less, consulting organizations that want baked-in methodology for client delivery, and vendors looking to bundle a white-labeled practice layer with their platforms.Groundwork is the brainstorming and planning app — dump ideas onto a canvas, sort them into zones, and shift into structured planning mode with priorities and rough timelines.Playbook is a lightweight wiki for capturing structured knowledge, course profiles, stakeholder analyses, and methodology documentation — with templates so you never start from a blank page.Atlas generates visual subway maps of your learning curriculum or capability landscape, complete with time-sensitive station states, deprecation indicators, and links back to Playbook pages.Outline lets you define the detailed content structure of a course or deliverable in a hierarchical, mind-map-style view — moving from “What do we need to teach?” to "Exactly what are the chapters and items?”Course Flow is a Kanban-based project management tool for developing and iterating on courses, complete with a built-in feedback form, an inbox for triage, and a status dashboard across all active projects.Cadence is a personal (and optionally team) task planner organized by day and category — with recurring daily items, carry-forward of incomplete tasks, and a simple velocity metric to spot overload before it becomes a crisis.The entire stack runs on Node.js, saves files as Markdown and JSON (no database required), plays nicely with Google Drive or OneDrive for backup, and optionally connects to GitHub or GitLab for full version history.Apps interoperate through lightweight linking and import/export — cards from Groundwork flow into Atlas, tasks from CourseFlow export into Cadence, and every Playbook page carries a permanent link that works anywhere in the stack.Find out more and download your free personal copy of Cadence at whatsyourbaseline.com/bpm-os—and check the episode show notes for a PDF overview of all six apps.Reach out by emailing ⁠hello@whatsyourbaseline.com⁠ or subscribe to our newsletter and articles on Substack at whatsyourbaseline.substack.com.

Britain on LinkedIn System76 Coder Radio Discord The Mad Botter Data Platform Mike's Legacy Data Promo Mike's Blog

In this episode, Pooja Ranjan interviews Kevin Jones, a leader at Edge and Node and creator of 1Claw - an innovative infrastructure platform designed to secure AI agents and manage secrets. They explore the critical vulnerabilities in AI workflows, how 1Claw addresses these risks, and the future of AI security in decentralized ecosystems.

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with Tyler Cloutier, founder of Clockwork Labs and creator of SpaceTimeDB. They explore how SpaceTimeDB functions as more than just a database—it's essentially a distributed operating system that merges server logic with data storage, enabling real-time applications and time-travel capabilities. The conversation ranges from the technical architecture of databases and operating systems to the philosophy of distributed systems, touching on everything from Unix and Linux to how SpaceTimeDB could revolutionize AI-generated software deployment. Tyler explains how their system reduces the complexity of building real-time applications, makes deployment simpler for both humans and AI agents, and why games like their MMORPG BitCraft Online drove them to create this new infrastructure. They also discuss the future of the internet, the role of bots in gaming, and how SpaceTimeDB fits into the broader landscape of cloud computing alongside tools like Cloudflare, Vercel, and Docker. For more information, visit spacetimedb.com or check out Clockwork Labs on GitHub and Twitter.Timestamps00:00 Stewart introduces Tyler Cloutier, founder of Clockwork Labs, discussing the origin of SpaceTimeDB's name inspired by Einstein's theory and its time travel capabilities that store all operations indefinitely05:00 Tyler explains SpaceTimeDB as more of an operating system than a database, using tables instead of file systems while running code in a sandboxed environment with full atomic properties10:00 Discussion of how SpaceTimeDB replaces both Node.js and Postgres by merging web server and database functionality, eliminating separate deployment concerns15:00 Tyler explains JavaScript execution through Chrome's V8 engine and JIT compiling, leading to Node.js creation for server-side JavaScript development20:00 Explanation of stateless web servers versus stateful game servers, and why games require in-memory state management for real-time performance25:00 Tyler introduces reducers and real-time subscriptions, questioning why more applications aren't real-time when state changes should update immediately30:00 Discussion of Facebook as essentially a text-based MMO, comparing social media architecture to game server requirements and the need for unified systems35:00 Tyler explains ACID properties in databases: atomic, consistent, isolated, and durable, using game item trading examples40:00 Comparing SpaceTimeDB to smart contract systems without cryptocurrency or global consensus, positioning it as a smart database with centralized trust45:00 Tyler reveals SpaceTimeDB uses 43% fewer tokens than Postgres for AI-generated applications, making it valuable for vibe coding platforms50:00 Conversation shifts to bots in games and proof-of-human concepts, with Tyler proposing biometric systems and discussing potential in-person gaming applications55:00 Closing discussion about tracking AI-driven traffic through UTM parameters and finding SpaceTimeDB at spacetimedb.comKey Insights1. SpaceTimeDB is fundamentally a database that runs application code directly inside it, combining what traditionally required separate systems like Postgres and Node.js. Users compile their application logic into WebAssembly or JavaScript and upload it to run within the database itself. This architecture provides high performance because the entire server backend operates inside the database environment. The system also features time travel capabilities, storing every operation and change to data persistently and indefinitely, allowing users to set application state back to any earlier point in time. This makes SpaceTimeDB more accurately described as an operating system rather than just a database, where the abstraction is that everything is a table rather than a file.2. The inspiration for SpaceTimeDB came from building BitCraft Online, an MMORPG where all players exist in a single persistent world and rebuild civilization together. Traditional MMO backends required complex custom solutions to handle real-time state, with game servers storing state in memory and periodically writing to databases. This complexity existed because games cannot afford the latency of constantly delegating to distant databases like traditional web applications can. SpaceTimeDB solved this by making the database fast enough to handle real-time requirements directly, eliminating the need for separate game servers. This same performance advantage that benefits games also applies to web applications, which is why SpaceTimeDB evolved from a game-specific tool to a general-purpose platform.3. SpaceTimeDB functions as a distributed operating system where each database acts like a process in an actor model system, similar to Erlang or Scala Akka. Databases can send messages to other databases and be spawned across a cluster for horizontal scaling. This represents an overlay operating system running on top of Linux rather than competing with it, providing a distributed abstraction across many machines while Linux handles device drivers and hardware support. The vision is for the cloud to function as a single enormous computer running one operating system, where developers simply publish their programs without managing separate services, deployment, routing, networking, or persistence infrastructure.4. The real-time capabilities of SpaceTimeDB address a fundamental limitation in how most web applications work today. Traditional web servers are stateless, delegating all state to databases and accepting network round-trip latency for each request, which is why users often must refresh pages to see updates. SpaceTimeDB allows queries to be subscribed to, maintaining open connections that stream changes whenever query results update. This makes applications like Discord, Facebook, or banking systems naturally real-time without requiring page refreshes. The historical accident that more things are not real-time represents a problem SpaceTimeDB solves by unifying the web world with the game world's real-time requirements.5. SpaceTimeDB implements ACID properties—Atomic, Consistent, Isolated, and Durable—ensuring database operations are reliable and safe. Atomic means operations either fully happen or not at all, preventing issues like item duplication in games when trading between players. Consistent means declared invariants like unique usernames are always enforced. Isolated means concurrent operations do not interfere with each other. Durable means changes persist even if computers restart, with varying levels from in-memory on one machine to disk storage across multiple geographic locations. These properties are managed through reducers, functions inspired by React Redux that fold changes into application state incrementally.6. For AI and large language models, SpaceTimeDB offers significant advantages in building and deploying applications. Testing showed that creating applications with SpaceTimeDB uses 43% fewer tokens compared to Postgres implementations, costs less, has fewer bugs, and is easier to extend. This matters because the primary cost for vibe coding platforms is tokens. As more software gets written in the next twelve months than ever before, there is insufficient focus on infrastructure required to run all this AI-generated software. SpaceTimeDB positions itself as ideal for LLMs to target because of its simplified deployment model where developers just publish code and the system handles everything behind the scenes.7. SpaceTimeDB can be understood as a smart contract system without cryptocurrency or global decentralized consensus. Like blockchain smart contracts, it executes code with atomic, consistent, isolated, and durable properties, but avoids the expense and slowness of requiring all computers worldwide to agree on everything. Instead, it offers centralized trust where users trust Clockwork Labs not to modify deployed contracts, rather than the trustless but extremely costly blockchain approach. This makes it functionally similar to Cloudflare's durable objects but with full relational database capabilities. The system exists before the networking layer where Cloudflare operates, handling deployment, server, and database functions while Cloudflare could provide DDoS protection in front of it.

In this episode, we look at whether “founding sponsor” is becoming the new AI acqui-hire, Tanner building a possible React replacement, and how Claude could get faster thanks to a new deal with SpaceX.Timestamps:0:58 - Tanner builds Redact8:14 - Anthropic makes a deal with SpaceX19:03 - Warp is now open source29:58 - Node 26 is out32:07 - ChatGPT is obsessed with goblins42:21 - What's making us happyNews:Paige - Warp is open source and OpenAI is its founding sponsorJack - Projecting ReactTJ - Anthropic makes a deal with SpaceXLightning News: Node 26 is outChatGPT is obsessed with goblinsWhat Makes Us Happy this Week:Paige - The Koerner Office on YouTubeJack - 3d printed Star Wars gunsTJ - The Lies of Locke Lamora novelThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.Front-end Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.comSubscribe to our YouTube channel @Front-EndFirePodcast

How do you tune your load? How do you find the Node?...Wrong answers only!

First up a chat I had with Andrew Wilkie from the Queer Screen Film Fest in Sydney. Andrew is the Programming and Industry Manager for the Festival and they spoke to me about the Emerging Narrative Feature Film Competition with a deadline of May the 24th.Second up is a chat with David Field and Stephen Dupont about The Half Barbaric Twangfeaturing The Number 4 Band on the Gimme Back Me Dog Tour.

In this potluck episode of Syntax, Wes and Scott answer your questions about LLM usage-based pricing, security risks from malicious code in interviews, staying current in a fast-moving dev landscape, a new CSS linter, managing Node environments and tooling without losing your mind, and more! Show Notes 00:00 Welcome to Syntax! 01:17 Copilot's new usage-based pricing and the end of cheap AI Model multipliers for annual Copilot Pro and Copilot Pro+ subscribers 08:53 Why Syntax dropped clever ad transitions 10:33 Debugging issues on the Syntax website with Sentry 12:51 Brought to you by Sentry.io 13:01 Getting hacked through a fake recruiter and malicious repos Adib Hanna's hacking story scammer.md DeskPad 17:57 How to catch up after stepping away from dev 25:10 React components vs native browser APIs 32:41 New CSS linting tools and Project Wallace updates csskit 36:06 How to interview developers in the age of AI 41:21 Managing Node, package managers, and dev environments 46:59 Sick picks + shameless plugs Sick Picks Scott: ZEISS Lens Care KeyboardCleanTool Wes: Amaran Halo 100x Shameless Plugs Syntax YouTube Channel Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Justin on LinkedIn pgFirstAid Coder Radio Discord The Mad Botter Data Platform Mike's Legacy Data Promo Mike's Blog

Sally Lait joins Robby Russell on Maintainable to explore software maintainability through a different lens… not just code quality, but how teams work together over time. Sally is a fractional technology leader and advisor with more than two decades in the industry. You can follow her on LinkedIn or Mastodon. They start with a familiar question: what makes software well maintained? Structure and standards matter, but Sally shifts the focus to signals around the edges… documentation, onboarding speed, knowledge sharing, and especially how confident people feel making changes. That confidence becomes the thread throughout the conversation. Teams with high confidence move faster and adapt more easily. Teams with low confidence hesitate, avoid parts of the system, and struggle to make progress… regardless of what the code looks like. Robby and Sally also dig into why maintenance work often struggles to get traction. It rarely speaks for itself. Leaders need to connect it to outcomes the business already cares about… risk, hiring, delivery speed, and long-term sustainability. Sally references a LeadDev panel she moderated on why maintenance still feels “stuck in 2015”: Why Software Maintenance Is Stuck in 2015. They also discuss modernizing legacy systems and moving away from long-standing in-house software… work that is rarely just technical. It requires trust, clear communication, and navigating the emotional attachment teams have to what they've built. The episode closes with advice for engineers joining older codebases: stay curious, build relationships early, and use onboarding gaps as opportunities to improve things for the next person. Episode Highlights [00:01:02] What Makes Software Maintainable: Technical quality matters, but cultural signals often tell the deeper story. [00:05:45] Why Progress Still Feels Slow: Even with improvements, teams can feel stuck due to perception gaps. [00:07:30] Communicating Small Wins: Lack of visibility into incremental progress impacts morale and confidence. [00:12:40] Influencing Without Manipulating: Maintenance work needs to be framed in business terms. [00:16:00] Technical Debt as a Hiring Problem: Outdated systems affect recruiting and retention. [00:20:22] Modernizing a Siloed System: Unlocking legacy data required both technical and organizational change. [00:26:55] Building Trust for Change: Surprise proposals fail… alignment takes time. [00:32:39] Letting Go of “Our Baby”: Replacing systems involves emotional and cultural dynamics. [00:46:25] Joining an Older Codebase: Practical advice for onboarding and building confidence quickly. Resources Mentioned Sally Lait Sally Lait on LinkedIn Sally Lait on Mastodon Why Software Maintenance Is Stuck in 2015 (LeadDev Panel) Lara Hogan The Murderbot Diaries by Martha Wells Death of the Author by Nnedi Okorafor Sally's Reading & Reviews Site Thanks to Our Sponsors! Your test coverage says 90%, but that might be misleading. Undercover CI looks at your Ruby pull requests and shows you which parts of your changes weren't tested- not just overall coverage, but what changed and what got missed, down to the method level. Visit undercover-ci.com and use code MAINTAINABLE for 15% off your first billing cycle. Free for public repos. Private repos with unlimited users also available. Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

In Episode 179 of the Cyber Threat Perspective podcast, host Brad Causey and web app pen tester Jordan Natter kick off a multi-part series on the OWASP Top 10, the newly updated list of the most common and critical web application security risks, with a fresh version released in 2025.Before diving in, Brad sets the record straight on something that's been bugging him for 20 years: the OWASP Top 10 is an awareness document, not a compliance framework, not a pen test checklist, and not a comprehensive defense guide. If your vendor claims they "comply with the OWASP Top 10," that's a red flag — you can't comply with an awareness document.Part 1 focuses entirely on A01: Broken Access Control — the most dangerous and most common category on the list — and the conversation goes deep with real-world stories from active engagements.Topics covered include:What OWASP actually is — and why the Top 10 is both invaluable and widely misunderstoodBroken Access Control — what it means, why it tops the list, and how it manifests in real applicationsJWT validation failures — a healthcare application where improper JWT handling allowed unauthorized access to admin functionalityMFA bypass via broken access control — a university application where MFA codes weren't properly scoped, enabling account takeoverCORS misconfigurations — how Cross-Origin Resource Sharing policies fail in modern Node and React applications, including a real story of bypassing CORS by allowing AWS resourcesInsecure Direct Object References (IDOR) — why IDOR isn't just about changing integer IDs, including a university app where changing a student ID number led to staff-level privilege escalationS3 bucket IDOR — how a modern web application exposed PHI by returning GUIDs in JSON responses that could be enumerated directlyHidden functionality as false security — why hiding admin URLs from the navigation bar is obscurity, not security, and how Jordan accessed an entire admin PDF panel as an unauthenticated user just by copying a URLOWASP Top 10: https://owasp.org/Top10/2025/0x00_2025-Introduction/ Blog: https://offsec.blog/Youtube: https://www.youtube.com/@cyberthreatpovTwitter: https://x.com/cyberthreatpovFollow Spencer on social ⬇Spencer's Links: https://spenceralessi.comWork with Us: https://securit360.com | Find vulnerabilities that matter, learn about how we do internal pentesting here.

Book a 1|1 Bitcoin Consulting call with mehttps://pathtobitcoin.xyz/Join my Bitcoin Learning Community & and access Free Courseshttps://www.skool.com/the-bitcoin-masters-4115/Where I buy Bitcoin (Free BTC & Non-KYC options)https://bitcoinwell.com/referral/bitcoinnotcrypto15% Stampseed Titanium Seed plates (BEST WAY TO STORE BTC PRIVATE KEYS)https://www.stampseed.com/USE CODE : BTCNOTCRYPTO15Get a Coldcard Hardware wallet herehttps://store.coinkite.com/promo/169FA71FECC4928F725D5% off Start9 servers for plug & play Bitcoin NodesCODE: BNC5https://store.start9.com/Umbrel home for a Bitcoin node and home serverhttps://a.umbrel.com/hodl/umbrel-homeAffordable Privacy Phones & deviceshttps://www.mark37.com/ref/BNC/5% off using code : BNCBuy a Bitforge or Bitaxe here!https://dtvelectronics.com/store/?aff=22Use code hodl for 10% offFree Open Source Bitcoin and Investment tracking toolshttps://plebtools.com/Become a Member of the Channel, Get exclusive content, and livestream playbackhttps://www.youtube.com/channel/UC2aM2gVVEHTu0pfE1ZyA0BQ/joinFollow Rajat, Jor, and I's new show togetherhttps://www.youtube.com/@MapleBitcoinJoin our Communityhttps://www.skool.com/maplebitcoinListen to this as a podcasthttps://podcasters.spotify.com/pod/show/bitcoinnotcryptoFollow me on Nostrnpub1zqm9zant0rxf49wfgw8pt5h0j50cetfes6hwa73u7sxstlzcsz8qh6x9fsFollow on Twitter/Xhttps://x.com/forrestHODLDonate to the show herehttps://coinos.io/BNCVFVSome of the above links may be Affiliate links that support this show at no extra cost to you. None of the links are Sponsored links. This allows me to only promote products and services I personally use and believe in.

In this episode of The Light Inside, we delve into the complex and often challenging topic of moral ambiguity within the therapeutic relationship. Our guest, Simon Mont, brings his expertise as an organizational and conflict coach to explore how moral ambiguity can shape interactions between clinicians and clients, especially when collapse, shame, defensiveness, or self-sealing containment narrow the relational field.We begin by discussing how moral ambiguity is not inherently problematic but can become a cue that organizes collapse, rupture, repair, and even re-traumatization under relational load. The conversation highlights the importance of metacognition, where the clinician's ability to observe the process while participating in it becomes crucial.Simon and I explore the dynamics of power within the therapeutic setting, emphasizing the need for clinicians to hold the relational field with enough capacity to slow down the sequence of events that lead to protective responses. We discuss the role of pacing, sequencing, and titration in allowing repair to become reintegration.A significant portion of our conversation focuses on the ethical considerations and the clinician's responsibility to maintain a balance between holding space for the client's agency and not imposing their own moral judgments. We touch upon the challenges of navigating societal and cultural contexts within therapy, and how clinicians can inadvertently replicate societal harms if they are not mindful of their own biases and power dynamics.Throughout the episode, we also reflect on our own interaction, using it as a live example of how misunderstandings and power dynamics can play out in real-time. This meta-conversation serves to illustrate the very principles we discuss, providing listeners with a practical understanding of the concepts.In summary, this episode offers a deep dive into the nuanced and often ambiguous terrain of therapeutic ethics, power dynamics, and the clinician's role in fostering a space where clients can explore their consciousness and agency. We hope this conversation provides valuable insights for clinicians and anyone interested in the therapeutic process.Timestamps[00:01:10] Moral ambiguity in therapy.[00:06:19] Power dynamics in therapy.[00:10:30] Client agency in therapeutic relationships.[00:13:06] Agency and mutuality in therapy.[00:17:27] Moral ambiguity and duality.[00:19:54] Moral ambiguity causal cue stack.[00:25:30] Therapeutic space and moral ambiguity.[00:32:19] Moral choices in clinical practice.[00:34:27] Moral ambiguity in coaching.[00:39:18] Gaps in communication and understanding.[00:44:58] Power dynamics in communication.[00:47:07] Power dynamics in healing relationships.[00:51:40] Agency and moral frameworks.[00:56:17] Power dynamics in conversation.[01:01:12-01:01:23] Node-level metacognition in relationships.[01:02:06] Failure of sequencing in care.Coachable Inquiry: What happens when interpretation starts moving faster than contact?Many communication breakdowns do not begin with bad intent. They begin when cue-driven appraisal, embodied state, and prior relational learning start shaping meaning faster than the relationship can hold context, pacing, and mutual contact. Read the blog, then share the part that challenged your assumptions most—we'd value hearing what it helped you notice in your own communication patterns."The Introspection Illusion: Cue-Driven Appraisal and the Early Loss of Contact"CreditsHost: Jeffrey BeseckerGuest: Simon MontExecutive Program Director: Anna GetzProduction Team: Aloft Media GroupMusic: Courtesy of Aloft Media GroupConnect with host Jeffrey Besecker on LinkedIn.

For episode 718 of the BlockHash Podcast, host Brandon Zemp is joined by Peter Anthony, Co-founder of Perceptron, a decentralized data infrastructure for AI. While VCs have poured over $170 million into AI data infrastructure this past year, nearly all of it has gone to centralized models. Perceptron is the decentralized alternative, with over 700,000 real users sharing idle bandwidth to collect, structure, and verify data in real time across 150 countries. 

Lunes 27 de Abril de 2026 Ya esta disponible MEDELLIN TECHNO PODCAST 317 Presentado por DERAOUT Invitada: Lea Node Soundcloud: https://soundcloud.com/leanodedj Instagram: https://www.instagram.com/leanode__/ Bandcamp: https://leanode.bandcamp.com/ _____ Design: www.boldbravestudio.com _____ #medellintechnopodcast #medellin #techno #podcast #djset #deraout #manizalestechno #leanode #bogotatechno

In this episode, Ray Cochrane unpacks Anthropic’s Mythos model and the Treasury’s emergency meetings with Wall Street, then digs into Apple’s vibe-coding crackdown and a gaming-anxiety study that hit way too close to home. Also covered: Verge’s solid-state motorcycle, UBTech humanoid robot sales jumping 23-fold, Japan’s first osmotic power plant, Finland’s permanent nuclear waste vault, Ghostty landing in Ubuntu, Cloudflare’s EmDash CMS, and a Claude Code skill that talks like a caveman. – Want to start a podcast? It’s easy to get started! Sign up at Blubrry – Thinking of buying a Starlink? Use my link to support the show. Subscribe to the Newsletter. Email Ray if you want to get in touch! Like and Follow Geek News Central’s Facebook Page. Support my Show Sponsor: Best Godaddy Promo Codes Get 1Password Full Summary Cochrane opens the show by framing Anthropic’s new Mythos model as the AlphaGo moment for cybersecurity. From there, the episode moves through Apple’s pushback against AI-generated apps, a gaming anxiety study with a deeply personal hook, a series of “first to ship” energy and robotics wins out of Finland, China, and Japan, and several developer-tool stories that show how quickly the economics of software are shifting. Mythos, the Detection Ceiling, and Wall Street’s Emergency Response Anthropic’s Mythos model has Wall Street rattled. Operating autonomously, Mythos found and demonstrated the exploitation of a 27-year-old TCP SACK bug in OpenBSD, an operating system famous for being one of the most security-focused on the planet. Per Anthropic’s red team, over 99% of the vulnerabilities Mythos has identified remain unpatched. The researchers’ conclusion is blunt: “the moat in AI cybersecurity is the system, not the model.” The policy response moved fast. On April 7th, Treasury Secretary Bessent and Fed Chair Jerome Powell pulled the CEOs of Goldman Sachs, Citi, Bank of America, and Morgan Stanley into Treasury headquarters on short notice. All four banks are now testing Mythos internally. Treasury CIO Sam Corcos is also seeking direct access. Anthropic is gating distribution through Project Glasswing, a limited-access program with JPMorgan, Apple, Google, Microsoft, and Nvidia. Cochrane comes down firmly behind Anthropic’s gated approach. Because a 5.1-billion-parameter open model can apparently recover the core analysis chain for the OpenBSD flaw, this capability is not locked behind Frontier Compute. He wants the critical infrastructure hardened before the public gets keys. However, he also notes the bigger lesson is about human wisdom: people offloading all their thinking to AI lose out on the wisdom that makes any of these tools genuinely useful. Apple Bans Vibe Coding Apps from the App Store Apple has been quietly pushing back against what people are calling “vibe coding” apps. Replit, Vibecode, and an app called Anything all run AI models on the phone and produce working software that runs inside the host app. Apple cites Guideline 2.5.2, in effect since 2017, which requires apps to be self-contained. Replit and Vibecode had their App Store updates blocked. Anything was pulled in late March, briefly restored on April 3rd, and then pulled the same day again. The forcing function is volume. App Store submissions jumped 84% in a single quarter as vibe coding tools flooded Apple’s review queue with AI-generated apps. Cochrane thinks Apple is justified, given the security issues swirling around the Vibe coding ecosystem. Even a beautiful diamond gets lost in a sea of sand, and that flood is exactly what Apple is trying to manage. The company behind Anything is now pivoting to iMessage, desktop, and Android. Playing Video Games to Win Is Linked to Higher Anxiety Cochrane gets personal on this one. Through high school and his early 20s, he was deeply addicted to League of Legends. His dad teased him about it constantly. In the last few years of that addiction, his body would go ice cold and shake every ranked match before. His partner identified it as a panic attack. The moment that happened, he quit. Today, he no longer shakes. The new study lines up with his experience. Researchers Kayleigh Watters and Mikael Rubin at Palo Alto University analyzed a publicly available database of 13,464 adult gamers, most of whom primarily played League of Legends. Players who game to win show higher generalized anxiety but actually play fewer hours, since performance pressure pushes them out. Players who game to relax show strong links between social anxiety avoidance and more hours played. The study appeared in the Journal of Affective Disorders. The headline framing of “playing to win makes you anxious” misses the point. The real finding is more interesting: gaming for avoidance and gaming for competition are both warning signs, for different reasons. Cochrane notes that the League of Legends community’s toxicity has been a running joke for years, and this study suggests the game’s structure may have been manufacturing the anxiety that fueled it. Sponsor: GoDaddy Economy hosting is $6.99/month, WordPress hosting is $12.99/month, and domains are $11.99. Both hosting plans include a free domain, professional email, and SSL certificate. Go to geeknewscentral.com/godaddy for the best pricing and to directly support this independent show. Verge Motorcycle: World’s First Production All-Solid-State Battery Cochrane filled his tank for $60 today, which made this story land especially hard. His mom has driven electric for years and patiently manages a 90-mile real-world range. The next-generation answer is already shipping. Verge Motorcycles, a Finnish company, is the first production vehicle of any kind with an all-solid-state battery. Their 2026 bikes ship in Q1 with a pack from Donut Lab, another Finnish outfit spun out of Verge. The numbers are bonkers. The pack delivers an energy density of 400 Wh/kg, roughly double that of current Tesla cells. It sustains 100kW charging, hits full charge in about 5 minutes in the lab and 12 minutes on the actual bike, and the long-range version covers 600 kilometers (about 370 miles) per charge. Toyota, QuantumScape, and Samsung SDI have all been telling us that solid-state is coming in 2027 to 2030. A Finnish motorcycle company shipping in Q1 2026 just embarrassed them all. UBTech Humanoid Robot Sales Jump 23-Fold UBTech dropped its 2025 annual earnings on April 1st. Humanoid robot revenue hit 820 million yuan, roughly $119 million USD, up 2,203% from 35.6 million yuan the year before. Unit sales went from 3 robots in 2024 to 1,079 in 2025. Shares jumped 14% on the announcement. The customer list is a real industrial deployment: BYD, Foxconn, Geely, FAW-Volkswagen, and Audi. The flagship is the Walker S2, with UBTech targeting 5,000 units in 2026 and 10,000 in 2027. Cochrane is honest about what this means. He does not think we are heading for an extinction event, but worker displacement is a real concern. The US has no universal income or universal healthcare. The people affected are not white-collar managers. They are everyday line workers who already make the least on the ladder. Work efficiency reportedly doubles when these robots arrive, which is a company-side win, but the humans they replace are not getting half a year of gardening leave to retrain. He invites the listener to take on this one directly. Japan Switches On Asia’s First Osmotic Power Plant In August 2025, Fukuoka’s Seawater Desalination Center quietly opened Asia’s first osmotic power facility. It generates about 880,000 kilowatt-hours per year, enough for roughly 220 homes. It is only the second operational osmotic plant in the world, after Mariager, Denmark, in 2023. Osmotic generation uses a salinity gradient: fresh water on one side of a membrane, salt water on the other, and the pressure difference spins a turbine. The clever part is what Fukuoka does with desalination brine. Instead of regular seawater, the plant uses concentrated brine left over from the desalination process. This amplifies the salt gradient and squeezes more energy out of the same membrane. The result is a closed-loop partnership: the desalination facility produces drinking water and leaves brine behind, the osmotic plant turns the brine into electricity, and that electricity runs the desalination facility. Every desalination plant on Earth produces brine, so if Fukuoka’s co-located model works, the same pattern could be replicated across hundreds of plants worldwide. Japan’s Luna Ring Solar Moon Proposal Goes Viral Again Shimizu Corporation’s Luna Ring concept is making the rounds again. The pitch: a 6,800-mile belt of solar panels around the Moon’s equator, beaming microwave power back to Earth. Project lead Tetsuji Yoshida has long argued that a full ring could eliminate fossil fuel dependence entirely. The proposal first surfaced in 2013, has no funding, no government endorsement, and no concrete cost estimate. Shimizu has not put any active development behind it. Cochrane finds the concept fun every time it resurfaces. However, this would have to be a worldwide effort in the truest sense, with treaties, a new generation of launch economics, and microwave power transmission at a scale nobody has demonstrated. Beaming the power back to Earth has always been one of the biggest practical holdbacks. The Luna Ring is inspirational, but not shipping. Finland’s Onkalo Nuclear Waste Vault Opens Finland’s Onkalo facility is the world’s first permanent deep geologic repository for spent nuclear fuel. Operated by Posiva, the facility is buried about 430 meters down in 1.9-billion-year-old bedrock. It is designed to hold up to 6,500 tons of spent fuel and operate until the 2120s. The construction costs about €1 billion, with operating and closure adding roughly €4 billion more before the program is done. The catch is that radioactivity remains dangerous for hundreds of thousands of years. Edwin Lyman, director of nuclear power safety at the Union of Concerned Scientists, warned that the copper canisters will eventually corrode, with different scientific opinions on how fast. Geologic disposal remains “fraught with uncertainties,” and we have never validated an engineered system across a 100,000-year time frame. The bet is that the rock and copper outlast the radioactivity. Cochrane sees Onkalo as time-buying rather than a final answer. It is more of a bank holding spent fuel while science catches up. He prefers it to Japan’s ongoing approach of releasing tritium-treated water from Fukushima Daiichi into the Pacific, even though the dilution is well below WHO drinking water guidelines. Burying the waste in an insurmountable containment strikes him as the more honest answer to a problem nobody knows how to truly solve. Ghostty Terminal Lands in the Ubuntu Repos Ghostty 1.3.0 is now available in Ubuntu 26.04 LTS’s universe repository. The install is simply `sudo apt install ghostty`, no PPAs, no Snap, no Nix, no building from source. Ghostty was created by Mitchell Hashimoto, co-founder of HashiCorp. It is GPU-accelerated, uses native Swift on macOS and native GTK4 with libadwaita on Linux, and supports tabs, splits, profiles, ligatures, and the Kitty graphics protocol. Cochrane recently caught Hashimoto on a podcast, where he walked through his agentic coding workflow. Ghostty is being actively built using AI harnesses like Claude Code and Codex. Hashimoto told a story in which Codex fixed a six-month-old bug in 45 minutes, for a total API cost of $4.14. Personally, Cochrane uses WezTerm, but he is excited to see Ghostty become more widely available with a native UI rather than Electron. Borgo: Rethinking Go Using Rust Analytics India Magazine profiled Borgo, a programming language by developer Marco Sampellegrini (GitHub: alpacaaa). Borgo is statically typed with Rust-like syntax, but it compiles to Go and uses the Go runtime and garbage collector. It includes sum types (Option and Result), pattern matching, and full compatibility with existing Go packages. Notably, it removes Rust’s borrow checker and lifetimes entirely. Borgo is not new. It first appeared on Hacker News in 2023, with a RustLab talk in 2024. The 2026 angle is a renewed look at it through the lens of AI coding agents, since type-rich languages like Rust have been showing outsized productivity gains. Cochrane is a fan of Rust and stands by the borrow checker, but he enjoys these exploratory languages for what they reveal about what developers actually want. Caveman: A Claude Code Skill That Cuts 65% of Tokens Developer Julius Brussee built a Claude Code skill called Caveman that forces Claude to respond in stripped-down fragments. No articles, no “just,” no “really,” no pleasantries, no hedging. The tagline is “why use many token when few token do trick.” Across 10 real dev tasks, Caveman mode averaged 294 tokens per response, compared to 1,214 in normal mode. That is a 65% drop in output tokens. The project is MIT licensed with three intensity levels: lite, full, and ultra. Cochrane stumbled across the project online and shared it with a classmate who had been complaining about token costs. The classmate now insists that “the caveman is the only way to live.” Cochrane has not made the switch, but the bigger point lands. If a community plugin can cut 65% of tokens without correctness regressions, the labs are shipping verbose-by-default and charging users for the privilege. He suspects verbose output makes models feel more trustworthy, even when the token math says otherwise. Cloudflare Launches EmDash as a WordPress Successor Cloudflare released EmDash on April 9th, an open-source, MIT-licensed, TypeScript-based CMS pitched as the spiritual successor to WordPress. The big flex is that it was built in 60 days using AI coding agents. EmDash runs on Astro 6.0, either on Cloudflare’s edge platform or on a standard Node.js server. The plugin security model uses sandboxed Dynamic Workers with explicit permissions, addressing the architecture flaw that Cloudflare says causes 96% of WordPress vulnerabilities. Cochrane could not resist pointing out the irony of the name. The em dash has become the trademark giveaway that an AI was involved in writing. He has reservations about whether EmDash will succeed. WordPress is extremely hard to unseat, plenty of “WordPress killers” have come and gone, and the ecosystem is twenty-plus years deep. He is curious to see what comes next but not optimistic. Google Open-Sources the DESIGN.md Format Google Labs open-sourced the DESIGN.md format used by Stitch, their AI UI design tool. DESIGN.md is a declarative file capturing a project’s design system, colors, typography, and spacing in a way AI agents can read and apply. Cochrane has tried Stitch personally and finds it impressive at producing web designs. He has also seen DESIGN.md-style files already start appearing in repositories. He sees this kind of file becoming a new paradigm for agentic design, alongside robots.txt and llms.txt. However, he worries about a side effect. If everyone uses the same standardized format and the same AI tools, the web could become a homogeneous set of sites that all look the same. He is enthusiastic about the standardization but hopes designers continue to push for genuinely unique work. A 13-Liter PC With a Water Loop Built Into the Case Geeky Gadgets covered a build by “Visual Thinker”, a 13-liter mini-ITX case with custom SLA-printed water distribution plates built directly into the chassis. Instead of traditional soft tubing, plates channel coolant between the CPU and GPU blocks and are sealed with TPU and silicone molds. The case supports a full-size GPU and an SFX power supply. No thermal benchmarks, parts list, or pricing have been published. It is a one-off you cannot buy. Cochrane sees this as a sign of where PC building has gone in 2026. Modern mid-grade GPUs run nearly every recent game, so raw performance is no longer the differentiator. He likes seeing builders lean into design and craft rather than just stuffing the most powerful parts into a box. He admits he is the traditional type and built his own machine to maximize parts, but the design-first direction is a healthy evolution for the hobby. To close out the show, Cochrane recommends Pocket Casts as a podcast app. He finds it picks up new episodes very quickly. Big thanks to GoDaddy for over twenty years of keeping this show on the air, and a reminder that every promo code use is like writing a check to the show. The post Mythos: Cybersecurity’s AlphaGo Moment #1862 appeared first on Geek News Central.

Shawn on LinkedIn Shawn's Yotube Channel Coder Radio Discord The Mad Botter Data Platform Mike's Blog

WHAT YOU'LL LEARN Why yard management is still one of the most manual parts of the supply chain How to identify if your yard is the hidden bottleneck in operations What causes congestion, idle time, and poor trailer visibility How gate delays impact warehouse throughput and carrier performance What “Smart Yard 3.0” means (and how it differs from traditional YMS) How AI improves gate check-in, asset visibility, and workflow orchestration The stages of AI maturity in yard operations—from visibility to autonomous decisioning Where security, fraud detection, and damage tracking fit into yard technology What operators should prioritize first when modernizing the yard HIGHLIGHTS 00:00 – Why the yard is still the last broken node in supply chain 01:39 – Why yard operations stayed manual while WMS and TMS evolved 05:00 – Signs your yard is under-managed (congestion, delays, visibility gaps) 06:44 – Smart Yard 3.0: from tracking systems to real-time orchestration 10:11 – AI maturity in yard operations (visibility → automation → optimization) 17:00 – How yard performance impacts the entire supply chain network 20:06 – Security, fraud detection, and damage tracking in the yard 23:19 – What AI-native logistics platforms look like next QUOTES [00:00:29] "The yard often remains the manual reactive, hard to see in real time type of solution." - Ninaad   [00:01:39] “The yard is one of three of the major nodes in the supply chain, about 50 billion in goods flow every single day. It is stunning to realize that it is the most un modernized node in the entire supply chain." - Darin Brannan   [00:04:53] "It was an afterthought. Now it's a constraint." - Darin Brannan   [00:08:07] "And a AI and agentic done right, is a game changer for the art." - Darin Brannan   [00:17:39] "Yards don't fall into isolation. It has the ability to have second-order effects across the network." - Harshida KEY TAKEAWAYS The yard is no longer a passive space—it's a control point for the entire network Most yard systems digitize workflows but don't improve decision-making Real transformation comes from redesigning workflows, not just automating them Small inefficiencies in the yard create large downstream operational impact AI shifts the yard from a tracking system to a movement orchestration platform ABOUT THE GUEST Darin Brannan, CEO, Terminal Industries Darin Brannan is a founder-operator and CEO with 25+ years of experience scaling SaaS and infrastructure platforms. At Terminal Industries, he leads the development of an AI-native Yard Operating System that uses computer vision and agentic AI to automate and optimize yard operations across enterprise supply chains. Learn more:  https://terminal-industries.com/ https://www.linkedin.com/in/darinbrannan/ Subscribe and Keep Learning!If you're a logistics leader looking to scale sustainably, don't miss out! Subscribe for more expert strategies on tackling modern supply chain challenges.Be sure to follow and tag the eCom Logistics Podcast on LinkedIn and YouTube

Tænker du over ophavsretten til det materiale, du bruger i dine prompts? Hvis ikke, er du ikke alene.Det viser en ny rapport fra ophavsretsorganisationen Tekst & Node, udarbejdet af analysebureauet Norstat. Undersøgelsen kortlægger udbredelsen, anvendelsen og de juridiske udfordringer forbundet med kunstig intelligens (AI) blandt 1.020 danske medarbejdere på tværs af alle brancher.Brugen af værktøjer som ChatGPT og Copilot er hurtigt blevet en integreret del af den danske arbejdsdag. To ud af tre medarbejdere anvender nu AI-værktøjer, og et stort flertal oplever en positiv effekt på deres produktivitet og resultater. Men der er også en markant uoverensstemmelse mellem den udbredte brug og virksomhedernes håndtering af juraen omkring brugen af generativ AI.43 % af brugerne prompter nemlig med materiale skabt af andre, for eksempel artikler, rapporter og bøger, hvilket som udgangspunkt kræver tilladelse.Kun halvdelen af de danske virksomheder har en AI-politik, og i disse politikker er ophavsret ofte fraværende. Kun hver femte medarbejder er dækket af en AI-politik, der eksplicit nævner ophavsret.Medvirkende:Stefan E. Kristensen, COO, Tekst & NodeKris Kjær Nielsen, seniorkonsulent, Tekst & NodeLink:https://www.tekstognode.dk/2026/04/17/saet-fokus-paa-ophavsret-i-ai-politikken-ellers-risikerer-medarbejdere-at-ende-i-et-juridisk-minefelt/

Guest Alan Rubin Panelist Richard Littauer Show Notes On this episode of Sustain, Richard Littauer sits down with computational biologist Alan Rubin to explore how open source software supports scientific research, clinical genetics, and cancer-related data infrastructure. Their conversation centers on MaveDB, a project that began as a way to organize hard-to-find variant data from research papers and has since evolved into a valuable resource for both scientists and clinicians. Along the way, they discuss infrastructure funding, research software sustainability, and why open source communities and academic researchers have a lot to learn from each other. Press download now to hear more! [00:01:24] Alan explains his role leading a research group focused on genomics, cancer medicine, and improving patient care through genetics. [00:02:46] We learn more about what MaveDB does. [00:06:52] Alan details why a database was needed. [00:08:26] Alan shares how the project grew out of collaboration, PyCon AU inspiration, Django, and Python tooling that let a small team build a practical research database. [00:11:54] There's a discussion on the infrastructure funding problem and Alan explains a major theme is how hard it is to fund scientific infrastructure, since most grants favor new discoveries rather than maintaining shared tools and databases. [00:17:55] The project took a major turn when clinical geneticists began using the data to interpret patient variants, pushing the team to rethink the interface and user needs. [00:21:13] Alan describes the new clinical-facing interface, Mave for Medicine (MaveMD), designed to help doctors evaluate specific variants for diagnosis and treatment decisions. [00:22:02] Alan talks about managing the project through a distributed team, shared responsibilities, and a role that now centers more on direction, priorities, and community than day-to-day coding. [00:23:36] They discuss why research software rarely attracts hobbyist contributors, even when the mission is compelling, and how scientific projects often function more like small product teams. [00:27:44] Alan makes the case that scientists often learn more about improving their software craft at events like PyCon than at discipline-specific conferences. [00:30:38] Alan highlights how academic software depends heavily on mature, well-documented open source tools and encourages more connection between technical communities and scientific work. [00:34:15] Find out where you can learn more about MaveDB and Alan's work. Quotes [00:10:04] “We quite literally followed the Django Girls tutorial, but instead of a building a blog, we built a database for research scientists.” [00:12:35] “Infrastructure is something everybody wants to have it exist and nobody wants to pay for.” [00:26:08] “I have never been successful in engaging the broader open source community, despite having tried many times to contribute to this or any other scientific project.” [00:31:01] “I think people who work in OSS should be excited about the kind of stuff that their work is enabling, even if they don't really hear about it.” Spotlight [00:35:44] Richard's spotlight is the book, News of the Dead. [00:36:22] Alan's spotlight is The Global Alliance for Genomics & Health (GA4GH) and all the good work they're doing. Links SustainOSS podcast@sustainoss.org richard@sustainoss.org SustainOSS Discourse SustainOSS Mastodon SustainOSS Bluesky SustainOSS LinkedIn Open Collective-SustainOSS (Contribute) Richard Littauer Socials Alan Rubin LinkedIn Dr. Alan Rubin Website (The University of Melbourne) PyCon AU 2026, Brisbane, August 26-30 Sustain Podcast- Episode 286: Jack Skinner of PyCon AU and Regional Confs Sustain Podcast- Episode 176: Maintainer Month with Russell Keith-Magee & Uriel Ofir Django Girls PyCon AU 2023-“Building a biological database with Python”- Alan Rubin (YouTube) Sustain Podcast- Episode 135: Tracy Hinds on Node.js's CommComm and PMs in Open Source Sustain Podcast-Episode 190: Karen Sandler on Software Freedom Conservancy (SFC) Original database paper (Pub Med) Database update paper (Pub Med) Preprint on the clinician-oriented interface Variant scoring tools for deep mutational scanning (Pub Med) Atlas of Variant Effects MaveDB News of the Dead Global Alliance for Geonomics & Health (GA4GH) Sponsor CURIOSS Credits Produced by Richard Littauer Edited by Paul M. Bahr at Peachtree Sound Show notes by DeAnn Bahr Peachtree Sound Special Guest: Alan Rubin.

Software maintenance is often framed as a technical problem. Refactoring code, fixing bugs, or upgrading dependencies. In this conversation, Robby Russell talks with Rein Henrichs about a different lens, one centered on understanding. Rein is a Principal Software Engineer at Procore, where he works within a large, long-lived system used across the construction industry. Rather than focusing on tooling, Rein emphasizes that well-maintained software is software that makes sense to the people maintaining it. To explain this, Rein introduces the idea of the line of representation, drawing on the work of Richard Cook. Engineers do not interact directly with systems. They rely on representations such as logs, dashboards, and code. These are approximations, not reality, echoing ideas from Plato's Allegory of the Cave. When those representations break down, teams lose shared understanding, what Rein describes as “common ground.” This often shows up as weak signals. Subtle indicators that something is not quite right. They are easy to ignore, but over time they lead to confusion and slower decision-making. Incidents make this especially visible. Rein explains how teams build alignment under pressure, highlighting that the role of an incident commander is coordination, not control. Clear communication matters as much as technical correctness. The conversation also explores how large systems behave in practice. They rarely fail completely. Instead, they degrade in multiple ways at once. While SLOs can help teams respond to customer-facing issues, they do not capture internal clarity or alignment. Rein references W. Edwards Deming to highlight a common trap. Not everything that matters can be measured. High-performing teams often rely on judgment, experience, and shared context. Toward the end, Rein connects these ideas to The Field Guide to Understanding Human Error by Sidney Dekker, challenging the idea that incidents are simply caused by mistakes. Instead, they emerge from the same behaviors that usually lead to success, just under different conditions. For teams working in complex systems, the takeaway is straightforward. Maintaining software depends on maintaining understanding. Links & Resources Procore Rein Henrichs on LinkedIn Concepts & References How Complex Systems Fail – Richard Cook The Field Guide to Understanding Human Error – Sidney Dekker W. Edwards Deming Gerald Weinberg – Secrets of Consulting Referenced in this Conversation Kent Beck: You're Ignoring Optionality and Paying for It Charity Majors: Deploys Are Just the Beginning Heidi Helfand: The Art and Wisdom of Changing Teams Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time!  Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

In this episode of The Cybersecurity Defenders Podcast, we discuss some intel being shared in the LimaCharlie community.Federal cybersecurity agencies have issued an urgent warning about Iran-linked cyberattacks targeting operational technology (OT) systems across U.S. critical infrastructure.A hacker operating under the alias “FlamingChina” claims to have breached a Chinese state-run supercomputing facility and stolen a large dataset that may exceed 10 petabytes of information.Multiple high-profile maintainers in the Node.js ecosystem report being targeted in a coordinated social-engineering campaign aimed at compromising widely used open-source packages.Microsoft Threat Intelligence reports that the cybercrime group Storm-1175 is conducting rapid ransomware campaigns deploying the Medusa ransomware family.Support our show by sharing your favorite episodes with a friend, subscribe, give us a rating or leave a comment on your podcast platform.This podcast is brought to you by LimaCharlie, maker of the SecOps Cloud Platform, infrastructure for SecOps where everything is built API first. Scale with confidence as your business grows. Start today for free at limacharlie.io.

This week we speak with Assistant Professor of Pediatrics at Harvard Medical School, Dr. Audrey Dionne about a recent work she co-authored on sinus node dysfunction following congenital heart surgery. How common was this encountered and how often were either temporary or permanent pacing needed? Are there certain surgeries that are more associated with the need for pacing after surgery? Why is this so common following heart surgery? Dr. Dionne shares her deep knowledge this week on this surprisingly common problem.  DOI: 10.1016/j.hrthm.2026.01.049

Warp's Oz Ben on LinkedIn Zach on LinkedIn Coder Radio Discord The Mad Botter Data Platform Mike's Blog

Google's quantum AI team just published a paper proving Bitcoin's encryption can be cracked with 20x fewer qubits than expected — private keys derived in 9 minutes. Is quantum computing Bitcoin's biggest existential threat? We break down the paper, the timeline, and why developers need to act now.⏱️ Timestamps00:00 - Intro01:38 - Sponsors (EasyDNS & Bull Bitcoin)03:21 - Boostagram Shoutouts04:38 - Housekeeping & Previous Episode Recap06:06 - Google's Quantum Paper: 20x Fewer Qubits to Crack Bitcoin07:00 - 7 Million BTC at Risk & the Satoshi Bounty Theory08:34 - Why the Bitcoin Mailing List Is Ignoring Quantum10:30 - Developer Priorities: Spam Wars vs. Quantum Preparedness12:00 - Preston Pysh & Jeff Booth Don't Understand Quantum13:00 - Why Banks Aren't the First Target — Bitcoin Is14:00 - Satoshi's Coins as a Quantum Canary15:01 - Nick Carter, Eleven Labs & Conflicts of Interest17:03 - Short vs. Medium Term: Is Bitcoin Safe Right Now?18:00 - The Rush vs. Caution Dilemma & BIP-36019:00 - NIST Post-Quantum Standards & Testnet Testing20:30 - Would You Fork for Quantum? The Hard Question21:00 - Taproot's Unintended Consequences & BIP-11023:04 - Bitcoin Treasury Companies Selling: Nakamoto, Genius Group, Marathon26:00 - Marathon Pivots to AI & HPC Data Centers27:28 - Why Only MSTR Survives the Treasury Strategy29:52 - Production Ready: New Bitcoin Node Software (Samson Mow, Jimmy Song, Parker Lewis)32:00 - Node Accessibility, Core vs. Knots & OP_RETURN Limits35:50 - Notable Noise Begins36:37 - Iran War Escalation: Boots on the Ground & the Strait of Hormuz40:00 - Scott Horton's Prediction & US Ground Invasion Plans42:01 - Trump's Legacy Play & the George W. Bush Theory43:00 - Iran's Nuclear Endgame44:00 - Strait of Hormuz, Houthis & Global Oil Chokepoints47:00 - Canadian Food Bank Crisis: 1 in 4 Out of Supplies49:00 - Brain Drain: 122,000 Engineers & Doctors Leave Canada50:00 - Immigration Policy & the Coming Reckoning54:00 - MAID Offered to 83-Year-Old Before Diagnosis57:01 - COVID Hospital Stories & Funeral Restrictions1:02:20 - Brampton or Hamilton Man

At KubeCon + CloudNativeCon Europe 2026 in Amsterdam, Alex Kestner, principal product manager for Amazon Elastic Kubernetes Service (EKS), discussed how Amazon EKS Auto Mode aims to reduce the operational burden of running Kubernetes at scale. While Kubernetes delivers significant power, it also introduces complexity—particularly through repetitive, day-to-day tasks like managing node lifecycles, ensuring security updates, and selecting optimal infrastructure. Kestner emphasized that much of this “undifferentiated heavy lifting” distracts platform teams from delivering business value. Amazon EKS Auto Mode addresses this by automating infrastructure operations across the full node lifecycle, shifting responsibility for key operational components outside the cluster and into AWS-managed services. Built in collaboration with the EC2 team and leveraging technologies like Karpenter, Auto Mode dynamically provisions right-sized compute resources based on workload requirements. While it doesn't eliminate all challenges—such as unpredictable workloads or diverse deployment needs—it provides a more application-focused approach to scaling and cost optimization. Ultimately, Auto Mode represents a meaningful step toward simplifying Kubernetes operations in increasingly complex cloud-native environments. Learn more from The New Stack about the latest developments around the latest with Amazon Elastic Kubernetes Service (EKS): 2026 Will Be the Year of Agentic Workloads in Production on Amazon EKS How Amazon EKS Auto Mode Simplifies Kubernetes Cluster Management (Part 1) A Deep Dive Into Amazon EKS Auto (Part 2) Join our community of newsletter subscribers to stay on top of the news and at the top of your game. 

Mike sits down with renowned open-source and COSMIC DE contributer Bryan Hyland to discuss working on projects for Linux-forward companies and of course some Rust! Bryan's Site Bryan on LinkedIn Mike on LinkedIn Coder Radio on Discord The Mad Botter Inc Mike's Book Mike's Blog

Software doesn't become hard to maintain only because the code is messy. It often becomes hard to maintain because the reasoning behind it disappears. In this episode of Maintainable, Robby Russell talks with Russ Olsen about trade-offs, legacy systems, and why maintainability depends on context more than dogma. Russ brings decades of experience across very different kinds of systems, each with its own definition of what “maintainable” actually means. A central theme is that software must be understandable to the people maintaining it. Teams tend to document implementation details well, but often fail to capture system-level intent and the trade-offs behind major decisions. Russ makes the case for preserving that thinking, including the alternatives that were rejected, so future maintainers don't have to rediscover it the hard way. The conversation also touches on Russ's book Eloquent Ruby, Second Edition. Rather than teaching syntax, the book focuses on how Ruby is actually used in practice and why common patterns exist. That leads into a discussion about where elegance improves maintainability, and where it turns into unnecessary cleverness. From there, the episode shifts into the realities of working in legacy systems. Russ explains how teams develop pessimism over time, often accepting flawed assumptions about how their systems behave. In some cases, major issues turn out to be far simpler than expected. The challenge is that teams stop looking. Robby and Russ also discuss the value of fresh perspective. New engineers or outside contributors can surface assumptions that longtime maintainers overlook. Russ suggests finding “pinch points” in a system as a practical way to understand behavior without needing to fully untangle everything at once. Later, the conversation explores developer quality of life. Long build and deploy cycles create daily friction that teams often underestimate. These slow feedback loops quietly degrade productivity and morale over time. The episode also tackles rewrites. Russ warns that teams frequently underestimate how much knowledge is embedded in existing systems. Code that looks questionable may reflect constraints no one documented. In practice, most successful rewrites happen incrementally, not all at once. The conversation wraps with a reminder that software development is fundamentally a social process. Russ argues that engineers undervalue storytelling, even though it's one of the most effective ways to connect technical work to real human outcomes. Episode Highlights [00:00:40] Defining maintainability: Why context matters more than a universal standard [00:02:01] Beyond code comments: Documenting system intent and trade-offs [00:08:14] Who Eloquent Ruby is for: Understanding how Ruby is used in practice [00:16:21] Elegance vs. cleverness: Where maintainability starts to erode [00:23:18] Legacy pessimism: Why teams stop questioning assumptions [00:29:25] Pinch points: A practical way to understand complex systems [00:32:05] Developer experience: The hidden cost of slow feedback loops [00:38:26] Rewrites: Why they fail and what teams overlook [00:44:00] Storytelling: Connecting technical work to real-world impact Resources Mentioned Russ Olsen on LinkedIn Eloquent Ruby, Second Edition Getting Clojure Zen and the Art of Motorcycle Maintenance A History of Western Philosophy Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time!  Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

An airhacks.fm conversation with Brian Vermeer (@BrianVerm) about: growing up with a Commodore 64 and gaming, inheriting a 486 DX2 with Windows 3.1, first "enterprise" migration from Windows 3.1 to 3.11, early experiments with Turbo Pascal and Basic, curiosity-driven programming and disassembling electronics, building computers from parts in the early PC era, high school informatics classes and the transition from hobby to career, bachelor's degree in software engineering, master's degree at Utrecht University focusing on Formal methods and compiler construction, mathematical proofs of program correctness, abstract syntax trees and program analysis, Haskell and pure functional programming, recursion vs loops and thinking in different paradigms, the influence of functional programming on Java development, first professional Java job at a temperature sensor monitoring company, building systems for vaccine transport temperature verification, enterprise service-based architecture, JavaServer Faces for frontend development, transitioning to consultancy at Blue4IT working for banks and government, community involvement and knowledge sharing, joining Snyk as a hybrid engineer and developer advocate, Snyk's origins as an NPM dependency scanner, supply chain security and NPM package vulnerabilities, expansion from Node.js to Java and other ecosystems, static code analysis and container analysis and AI flow analysis, security as part of the development lifecycle not an afterthought, vibe coding and AI assistant security checks, MCP server toxic flow risks, Java vs python for scripting and automation, JBang for Java scripting, modern Java simplicity vs legacy enterprise verbosity, Java developers thinking about production from the start, Java and C# as the main languages for large backends, JVM optimization over time, Leslie Lamport and formal verification of concurrent programs, outsourcing expertise vs doing everything Brian Vermeer on twitter: @BrianVerm

A new DeFi exploit triggered millions in losses, but the deeper story is about risk. In this episode, Omer Goldberg, founder of Chaos Labs, explains how the attack unfolded, why the damage spread across lending markets, what vault curators got wrong, and whether DeFi is truly ready for mainstream adoption. If you want to understand stablecoin risk, oracle design, curator incentives, and the future of safer onchain finance, this is the conversation to watch.Big thanks to our sponsors;NEXONexo is a premier digital assets wealth platform that helps clients build, manage, and preserve their wealth through advanced interest-generating products, crypto-backed credit, advanced trading tools, and 24/7 client care. Get started at nexo.com/defiant MERCURYOYour Web3 product deserves solid payment infrastructure. Global on/off-ramps, custom APIs, and DeFi connectivity trusted by the biggest names in crypto: mercuryo.ioROCKET POOLRocket Pool is Ethereum's decentralised liquid staking protocol. Node operators can join with just 4 ETH, or liquid stakers can hold rETH and automatically earn staking rewards. rocketpool.net

Grab the free one-page OpenClaw setup guide with every step and command listed out: https://corey-ganim.kit.com/c93f43577eI walk through the complete OpenClaw setup process from zero to a working AI agent connected to Telegram — all in under seven minutes. You'll see every step: running the installer, configuring your Anthropic API key, creating a Telegram bot through BotFather, pairing it to your OpenClaw instance, and enabling web search with DuckDuckGo. One prerequisite, one terminal command, and you're live.Key Takeaways:OpenClaw installs with a single terminal command — the only prerequisite is having Node.js installed, which is also a one-command setupThe guided onboarding handles every configuration decision (model, API key, channel, search) through simple yes/no prompts — no manual config filesCreating a Telegram bot through BotFather takes about 60 seconds: message BotFather, run /newbot, choose a name ending in "bot," and copy the tokenDuckDuckGo is the fastest search provider to start with because it requires zero additional API keys or setupSkills and hooks can be added after the initial install — you don't need to configure everything before getting your agent runningThe OpenClaw control panel gives you a browser-based chat window plus access to channels, sessions, usage stats, cron jobs, files, skills, and nodesTimestamps: 00:00 - Introduction 00:02 - Running the OpenClaw installer from the terminal 00:30 - Node.js prerequisite (quick install)00:45 - Guided onboarding: Quick Start setup 01:05 - Choosing Anthropic as your model provider 01:20 - Entering your Anthropic API key 01:35 - Selecting Claude Sonnet 4.6 01:52 - Creating a Telegram bot with BotFather 02:45 - Naming your bot and choosing a username 03:15 - Connecting the bot token to OpenClaw 03:30 - Enabling DuckDuckGo web search 03:45 - Skipping skills and hooks (configurable later) 04:06 - OpenClaw control panel overview 04:30 - First chat with your bot in the browser 05:15 - Pairing the bot with your Telegram account 06:10 - First Telegram message confirmed 06:30 - Setup complete — next steps for personalizationLinks Mentioned:OpenClaw: https://openclaw.aiAnthropic API Console: https://console.anthropic.comBotFather (Telegram): https://t.me/BotFatherDuckDuckGo: https://duckduckgo.comNode.js: https://nodejs.orgEnjoyed this episode? -> Subscribe and leave a review -> Join the community waitlist: https://return-my-time.kit.com/1bd2720397

Wes, Scott, and CJ talk about Vite+, a unified JavaScript toolchain that combines linting, formatting, task running, monorepos, and more. They break down its evolution, open-source shift, performance gains, Node version management, and whether it can realistically replace today's fragmented dev tooling. Show Notes 00:00 Welcome to Syntax! 00:54 What Vite+ is and what's changed since launch 03:43 Why the ecosystem needs Vite+ 06:41 What Vite+ actually does for your workflow 10:18 Built-in Node version management 12:32 Type-aware linting with tsgolint and oxc 15:27 Brought to you by Sentry.io 16:28 Should config live inside vite.config? 22:56 Monorepos and task running in Vite+ 26:28 Task caching and faster builds 29:01 Final thoughts and current limitations Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Long-lived software systems rarely stay tidy. Over time they accumulate decisions, workarounds, and layers of history that can make even simple changes feel risky. For engineers responsible for maintaining those systems, the challenge often becomes less about writing new code and more about understanding what already exists. In this episode of Maintainable, Robby Russell speaks with Joel Oliveira, Engineering Manager at ezCater, about what helps software remain understandable and adaptable as it evolves. Joel starts with a principle that often gets overlooked: predictability. When patterns are consistent and code is organized in familiar ways, engineers can navigate a codebase with confidence. Frameworks like Ruby on Rails reinforce this by encouraging shared conventions, making it easier for developers to orient themselves when working in a new application. The conversation also explores how common metrics can be misleading. Test coverage is often treated as a proxy for quality, but Joel explains that it can create a false sense of confidence. Instead, he values testing most as a thinking tool. Practices like test-driven development can help engineers clarify interfaces and better understand the problem before committing to an implementation. Joel also shares a story from ezCater about replacing an aging image-cropping service that had become difficult to maintain and required frequent restarts due to a memory leak. Rather than patch the system again, the team introduced ImageProxy, an open source image processing tool created by Evil Martians. Because the image URLs flowed through a single object in their GraphQL layer, the team could introduce an adapter and gradually route traffic to the new service using feature flags. This allowed them to migrate safely and incrementally instead of relying on a risky “big bang” change. Robby and Joel also discuss how engineers' perspectives shift over time. Early in a career it is easy to look at legacy code and label it as bad. Joel now sees older systems as layers of decisions shaped by real constraints. Approaching them with empathy makes it easier to improve them thoughtfully. The episode closes with advice for engineers maintaining complex systems: frame problems as opportunities. By documenting impact and proposing incremental improvements, teams can steadily move their software toward a healthier future. Maintainable software rarely comes from one heroic refactor. More often, it's the result of many small improvements made by teams who understand their systems and care about how they evolve. Episode Highlights 00:02:18 – Predictability as a Maintainability Feature Joel explains why predictable patterns and conventions make large codebases easier to navigate. 00:07:41 – When Test Coverage Misleads Why high coverage can give a false sense of quality. 00:12:05 – Consulting vs. Product Engineering How switching environments shaped Joel's approach to code. 00:16:32 – Replacing a Legacy Image Service ezCater's migration away from a failing Node-based image service. 00:21:14 – Migrating with Adapters and Feature Flags How the team gradually moved traffic to ImageProxy. 00:26:03 – Developing Empathy for Legacy Code Why older systems deserve understanding, not blame. 00:30:47 – The Shift to Engineering Management Joel reflects on moving from IC work to leading teams. 00:34:52 – Advice for Improving Complex Systems Small, consistent improvements matter more than big rewrites. Thanks to Our Sponsor! Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time!  Use the code maintainable to get a 10% discount for your first year. Check them out! Links / References Joel Oliveira — LinkedIn Joel Oliveira — Website Joel Oliveira — Mastodon (@jayroh) ezCater ImageProxy Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

Scott on LinkedIn Black Dog Ventures Mike on LinkedIn Coder Radio on Discord The Mad Botter Inc Alice Limited Offer Mike's Book Mike's Blog

YARA-X 1.14.0 Release https://isc.sans.edu/diary/YARA-X%201.14.0%20Release/32774 INTERPLAY BETWEEN IRANIAN TARGETING OF IP CAMERAS AND PHYSICAL WARFARE IN THE MIDDLE EAST https://research.checkpoint.com/2026/interplay-between-iranian-targeting-of-ip-cameras-and-physical-warfare-in-the-middle-east/ Announcing the Node.js LTS Upgrade and Modernization Program https://openjsf.org/blog/nodejs-lts-upgrade-program nginx UI Vulnerability https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-g9w5-qffc-6762

Mike on LinkedIn Coder Radio on Discord Mike's Oryx Review Alice Alice Jumpstart Offer

Wes and Scott talk about the latest dev news: Node enabling Temporal by default, OpenAI acquiring OpenClaw, TypeScript 6, new TanStack and Deno releases, the explosion of AI agent platforms, and more. Courtney Tolinski's Podcast Phases: A Parenting Podcast https://phases.fm/ Show Notes 00:00 Welcome to Syntax! 01:11 Brought to you by Sentry.io 02:40 Node.js enables Temporal by default Enable Temporal by default 04:08 OpenClaw acquired by OpenAI OpenClaw, OpenAI and the future 09:36 Bots are taking over the internet Wes' tweet 15:30 TypeScript 6 Beta Announcing TypeScript 6.0 Beta 17:00 TanStack Hotkeys for type-safe shortcuts TanStack Hotkeys 18:05 Components will kill webpages Components Will Kill Pages 19:39 Is Google Translate just an LLM? Viridian's tweet 23:29 Shaders.com 26:49 Voxtral Mini Realtime Voxtral Realtime Demo 29:51 Deno launches Sandboxes Introducing Deno Sandbox 32:39 Oz by Warp.dev 38:10 Augment Code Intent 40:10 Sick Picks + Shameless Plugs Sick Picks Scott: Samsung Remote Wes: Ice Shameless Plugs Syntax YouTube Channel Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

OpenClaw is a self-hosted AI agent daemon that executes autonomous tasks through messaging apps like WhatsApp and Telegram using persistent memory. It integrates with Claude Code to enable software development and administrative automation directly from mobile devices. Links Notes and resources at ocdevel.com/mlg/mla-29 Try a walking desk - stay healthy & sharp while you learn & code Generate a podcast - use my voice to listen to any AI generated content you want OpenClaw is a self-hosted AI agent daemon (Node.js, port 18789) that executes autonomous tasks via messaging apps like WhatsApp or Telegram. Developed by Peter Steinberger in November 2025, the project reached 196,000 GitHub stars in three months. Architecture and Persistent Memory Operational Loop: Gateway receives message, loads SOUL.md (personality), USER.md (user context), and MEMORY.md (persistent history), calls LLM for tool execution, streams response, and logs data. Memory System: Compounds context over months. Users should prompt the agent to remember specific preferences to update MEMORY.md. Heartbeats: Proactive cron-style triggers for automated actions, such as 6:30 AM briefings or inbox triage. Skills: 5,705+ community plugins via ClawHub. The agent can author its own skills by reading API documentation and writing TypeScript scripts. Claude Code Integration Mobile to Deploy Workflow: The claude-code-skill bridge provides OpenClaw access to Bash, Read, Edit, and Git tools via Telegram. Agent Teams: claude-team manages multiple workers in isolated git worktrees to perform parallel refactors or issue resolution. Interoperability: Use mcporter to share MCP servers between Claude Code and OpenClaw. Industry Comparisons vs n8n: Use n8n for deterministic, zero-variance pipelines. Use OpenClaw for reasoning and ambiguous natural language tasks. vs Claude Cowork: Cowork is a sandboxed, desktop-only proprietary app. OpenClaw is an open-source, mobile-first, 24/7 daemon with full system access. Professional Applications Therapy: Voice to SOAP note transcription. PHI requires local Ollama models due to a lack of encryption at rest in OpenClaw. Marketing: claw-ads for multi-platform ad management, Mixpost for scheduling, and SearXNG for search. Finance: Receipt OCR and Google Drive filing. Requires human review to mitigate non-deterministic LLM errors. Real Estate: Proactive transaction deadline monitoring and memory-driven buyer matching. Security and Operations Hardening: Bind to localhost, set auth tokens, and use Tailscale for remote access. Default settings are unsafe, exposing over 135,000 instances. Injection Defense: Add instructions to SOUL.md to treat external emails and web pages as hostile. Costs: Software is MIT-licensed. API costs are paid per-token or bundled via a Claude subscription key. Onboarding: Run the BOOTSTRAP.md flow immediately after installation to define agent personality before requesting tasks.