Podcasts about Tooling

On today's show, we dive into the cost structure of audio speakers. We start with an article that asks whether 'audiophile' speaker brands are milking you for $20,000. We also read your emails and cover the week's news. News: Important update to your DIRECTV account SVS Auto EQ Room Correction for R|Evolution Subwoofers YouTube TV adds Fox One, Peacock to Primetime Channels store Other: Monoprice Alpha In-Wall Speaker There's never been a better time to grab a new Google TV launcher Are 'Audiophile' Speaker Brands Are Milking You for $20,000 The listeners keep delivering great ideas for show topics. This week Mike LaBorde sent in an article published at headphonesty.com entitled A Former FTC Economist Quit His Job to Prove 'Audiophile' Speaker Brands Are Milking You for $20,000.  The author talks about how a former FTC economist quit his job to design and build affordable high-performance speakers.  He argued that many premium audiophile brands are significantly overpriced because they use similar OEM drivers from the same factories while charging massive markups for branding, cabinets, and dealer margins. We'll break down this article into five points we felt were interesting. The full article is linked and you may want to read it for more details. Many premium audiophile speaker brands rely on the same small group of OEM driver manufacturers (like Sinar Baja/SB Acoustics, SEAS (Scandinavian Electro Acoustic Systems), Scan-Speak, etc.). The same factories and engineering talent supply drivers to both high-end and mainstream brands, even when the final speakers carry vastly different logos and price tags. "Custom" or "proprietary" drivers are often overstated. Most brands customize only the "soft parts" (cone, surround, voice coil) on top of standard off-the-shelf "hard parts" from OEM suppliers, rather than designing and building drivers entirely from scratch. Pricing of speakers — The actual cost of the drivers is a tiny fraction of the retail price. In the Wilson Audio Yvette example, the three drivers cost roughly $530–$580 total, representing only about 2% of the $25,000+ selling price. The vast majority of the cost comes from cabinetry, finish, dealer margins (40-50%), distribution, marketing, and brand prestige, with a typical 5x markup from manufacturing cost to retail. Only a few brands truly manufacture their own drivers in-house. Companies like Focal, KEF, Dynaudio, Paradigm, and Bowers & Wilkins are exceptions. Most premium brands outsource driver production due to the high cost and complexity of vertical integration. High performance doesn't require extreme prices. Former FTC economist Dennis Murphy's Philharmonic Audio proves this by offering well-engineered speakers (like the $850/pair Ceramic Mini using quality SB Acoustics drivers) with minimal overhead, direct sales, and no lavish dealer/showroom costs — challenging the idea that great sound must come with five-figure price tags. The article essentially argues that much of the ultra-premium speaker market is driven more by branding and distribution economics than by revolutionary driver technology. What is the Cost Breakdown of Thousand Dollar Speakers? After going through the previous article we wondered what the actual cost breakdown of Passive bookshelf speakers retailing at $1,000 per pair? ThinkKEF Q series, ELAC Debut Reference, or similar mid to high end consumer hi-fi brands. They balance good performance with accessible pricing.  What follows is our best estimation based on the data we uncovered. If you are in the industry and have better data, please let us know and we will update this analysis. Sources for this analysis include - Audio Science Review, AVS Forum, WhatHifi, headphonesty.com, hubhifi, and a few others.  1. Design & Development (R&D) – Upfront Investment Typical cost: $50,000–$250,000+ for a new model line. Includes acoustic modeling, driver selection/tuning, crossover design, enclosure simulation, multiple prototypes, listening tests, and anechoic chamber measurements. For this price tier, brands often use a mix of off-the-shelf and mildly customized drivers rather than fully bespoke high-end ones.   Amortization: Spread over production volume and for this exercise we used a production run of 5,000–20,000 pairs. This adds roughly $5–$25 per pair at a reasonable scale. 2. Prototyping & Tooling Prototypes: 5–15 iterations at $300–$1,200 each which include custom cabinets, driver samples, hand-assembled crossovers. Tooling: CNC molds/jigs for cabinets, baffle cutting, or vinyl wrap tooling: $8,000–$40,000 upfront. Amortized to $2–$10 per pair. 3. Bill of Materials (BOM) – The Biggest Per-Unit Cost For a typical 2-way passive bookshelf (6.5" woofer + 1" tweeter) at this price point: Drivers - $80–$180 - 6.5" coated paper woofer (~$30–$70 ea.), soft dome or aluminum tweeter (~$15–$50 ea.). Brands like SEAS, SB Acoustics, or custom OEM. Cabinet -  $60-$130, - Braced MDF (18–25mm), vinyl wrap or basic veneer, internal damping, port tube, terminals. Real wood veneer adds premium. Crossover - $30-$80 - 2nd/3rd order with air-core inductors, film capacitors, resistors. Higher quality parts (Mundorf-level) push toward the upper end. Other (grille, wiring, hardware, terminals) - $20-$50 - Magnetic grilles, internal wiring, binding posts. Total BOM per pair: $190–$440 at volume production (typically in China or Vietnam for most brands). Premium touches (better drivers, thicker bracing, nicer finishes) push BOM toward the higher end. 4. Manufacturing, Assembly & Overhead Labor & Assembly: $25–$60 per pair (cabinet gluing/bracing, driver mounting, crossover soldering, final wiring, testing). Quality Control & Testing: Burn-in, frequency sweeps, distortion checks: $10–$25. Factory Overhead/Utilities: $35 - $50. Total Manufacturing per pair: $70 - $135 5. Full Cost Structure to Retail ($1,000/pair) We will assume a large brand that sells 20,000 units and has already invested in tooling and requires minimal new tooling for each new speaker design.  Design and R&D Amortized - $5 Prototype and Tooling  - $2 Bill of Materials - $315 - We split the $190 - $440 down the middle Manufacturing -  $103 - We split the $40 - $135 down the middle Shipping, duties etc to distributor per pair on average - $50 Total to Manufacture $474. The rest of the thousand dollars covers the distribution chain, branding, and profit. And in reality, depending on the efficiency of the factory and ability to leverage design histories from years of experience, the soft costs can be about a third of $110 we came up with, bringing the total cost to about $400. Key Variables Affecting Cost Volume: Higher production = lower per-unit costs. Driver Quality: Exotic materials (beryllium tweeters, carbon fiber) can double driver costs. Cabinet Finish: Vinyl vs. real walnut veneer = big difference. Brand Positioning: Established names (KEF, ELAC) have higher R&D/marketing allocation than direct-to-consumer brands. For comparison DIY builders can replicate similar performance for $300–$600 per pair in parts using higher quality drivers and crossover components and flat-pack or self-built cabinets, eliminating most of the overhead and markups. And after building over 30 sets of speakers I can say without doubt that what you build will sound as good as speakers costing ten times the amount. Plus you can use material that works best for you as well as customizing the look to match your decor. Even my latest set built from stock off the shelf components bought from Part Express for about $200 sound simply amazing!  

In this episode of China Manufacturing Decoded, Adrian is joined by Paul Adams, Head of New Product Development at the Sofeast Group's contract manufacturer Agilian Technology, to discuss one of the most common assumptions hardware founders make before moving into tooling: that tooling will take “8 to 12 weeks.” Paul explains why that figure can be true in very simple cases, but why it is often misleading for real consumer electronics, IoT, and hardware products. Tooling timelines depend on design readiness, DFM review, part complexity, steel selection, toolmaker capacity, customer responsiveness, and the timing of Chinese holidays such as Chinese New Year and Golden Week. They also discuss why the tooling clock does not really start when the purchase order is placed, why T0, T1, and T2 trials need to be planned carefully, and why founders should build schedule buffers before cutting steel. For hardware startups and product teams preparing for injection molding, metal stamping, die casting, or other production tooling, this episode explains how to build a more realistic tooling schedule and avoid costly launch delays.   Podcast sections 00:00:31 – The “8 to 12 week tooling timeline” 00:02:28 – What tooling includes and why it matters 00:04:21 – Tooling cost and why first-time founders get caught out 00:06:08 – Where the 8 to 12 week figure comes from 00:07:23 – Why real consumer electronics products are more complex 00:08:35 – When the tooling timer really starts 00:11:10 – Why design readiness and DFM review are critical 00:13:26 – How part complexity affects tooling lead time 00:13:50 – Steel selection: P20, H13, and tool life 00:15:40 – Responsiveness during T0, T1, and T2 trials 00:16:26 – Why being in China can speed up tooling decisions 00:19:03 – Planning around Chinese New Year, Golden Week, and May Day 00:21:47 – How to create a tooling schedule that works 00:22:05 – Reviewing the DFM report properly before cutting steel 00:24:00 – Building a tooling specification and critical path plan 00:25:34 – Understanding T0, T1, T2, and rework cycles 00:27:45 – Why you should always build in a schedule buffer 00:28:56 – Why many tooling delays come from the customer side 00:30:15 – Final advice: understand the full tooling process   Related content Tooling Management for Plastic Injection Molds in China Plastic Injection Mold Tooling Management & Risk Reduction [Podcast] Common Design For Manufacture Improvements On Plastic Injection Molded Parts Injection Mold Tooling Roadmap: How to Get from Smart Design to T1 Samples What are Plastic Injection Mold Tooling Revisions? (3 examples) How To Make Faster Injection Mold Tooling [7 Tips] Plastic Injection Molding Pilot Runs: What You Need To Know The Four Levels of Plastic Injection Molding Suppliers in China Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB

A Washington state manufacturer of tooling and parts for advanced industries plans to establish its third production facility in Montana — and create about 2,000 jobs.Janicki announced Tuesday that it selected Great Falls, Montana, for the $800 million project, which would complement the company's existing production facilities in Northwest Washington and suburban Salt Lake City.The privately-owned engineering and manufacturing company, established in 1993, says it designs and builds tools, parts, assemblies and prototypes for a wide range of industries, including aerospace, defense, architectural and marine applications. It specializes in composite fabrication and precision machining utilizing its proprietary 5-axis mills, which it says are among the largest in the world.Janicki officials said in a statement that growth in its aerospace and defense programs, in particular, has pushed demand beyond its capacity in Washington and Utah. The Montana plant, they added, will be part of a “multi-state, phased growth strategy.”The company anticipates building a campus that would add 2 million square feet of production space over the next decade. The project would create about 1,000 jobs within the first five years and more than 2,000 jobs overall once construction is complete — a total that would roughly double its current workforce.Montana Free Press reported that Janicki would receive a 50% property tax break from the city and county over five years, which would then be gradually phased out over the following five years. The incentives would reportedly be applied separately to each of the project's four phases of construction.Janicki expects to begin construction next month and open the first phase of the new facility by the end of next year. #manufacturing, #aerospace, #defense, #advancedmanufacturing, #industrialnews, #manufacturingnews, #economicdevelopment, #jobs, #factory, #engineering, #supplychain, #composites, #precisionmachining, #madeinamerica, #industrynews

In dieser SEOPRESSO-Livestream-Episode spricht Björn Darko mit Artur Kosch, Co-CEO und Mitgründer der kkp agency über KI-Automatisierung im SEO- und AI-Search-Umfeld. Im Mittelpunkt stehen Claude Code, MCPs, KI-Agenten und die Frage, wie sich Agenturarbeit dadurch grundlegend verändert.Artur erklärt, dass KI bei KKP kein zusätzliches Tool mehr ist, sondern zur zentralen Arbeitsumgebung geworden ist. Viele Aufgaben, die früher manuell, mit Make, n8n, Custom GPTs, Excel, Präsentationen oder klassischen SEO-Tools erledigt wurden, laufen heute über Claude Code, eigene Skills, Agenten und ein internes „KKP-Brain“.Besonders spannend sind die konkreten Workflows: KKP automatisiert Prompt Research, AI-Visibility-Analysen, Sentiment-Auswertungen, Content-Erstellung, Digital-PR-Kampagnen und sogar Landingpages. Dabei zeigt Artur, dass es in AI Search nicht reicht, einfach nur von KI-Systemen erwähnt zu werden. Entscheidend ist, ob eine Marke positiv empfohlen wird und im Vergleich zur Konkurrenz überzeugt.Die Episode macht deutlich: KI ersetzt nicht einfach Menschen, sondern verschiebt ihre Rolle. Weniger manuelle Fleißarbeit, mehr Strategie, Qualitätskontrolle, Kundenverständnis und Bewertung der Ergebnisse.Takeaways:KI ist ein Systemwechsel, kein Tool-UpgradeClaude Code ist bei KKP nicht nur ein weiteres Tool, sondern die zentrale Infrastruktur für viele SEO-, Content- und AI-Search-Prozesse.Prompt Research muss datenbasiert seinPrompts einfach zu erfinden, ist laut Artur fahrlässig. KKP nutzt Keywords, Synonyme, Query Fanouts und Clustering, um relevante Prompts systematisch abzuleiten.AI Visibility braucht SentimentEine Brand kann sichtbar sein und trotzdem verlieren, wenn sie von KI-Systemen im Vergleich zur Konkurrenz negativ oder nur eingeschränkt empfohlen wird.MCPs machen Automatisierung skalierbarÜber MCPs wie DataForSEO oder Statista greifen die Workflows auf Crawling-Daten, SERPs, Trends, Statistiken und Quellen zu.Content entsteht aus Daten, nicht aus BauchgefühlGute KI-Workflows verbinden Brand Guidelines, Produktdaten, SERP-Analysen, LLM-Antworten, TF-IDF-Daten und Deep Research.Menschen bleiben wichtigStrategie, Einordnung, Kundenkommunikation, Qualitätssicherung und fachliche Bewertung werden wichtiger als reine operative Umsetzung.Agenturarbeit wird outputstärkerArtur beschreibt, dass sich der Output deutlich erhöht hat. Entscheidend bleibt aber, Ergebnisse zu liefern statt nur Analysen, Folien oder Tabellen.Kapitelmarken00:00 Intro & Vorstellung von Artur Kosch03:15 Warum KI für KKP ein Systemwechsel ist05:34 Claude Code vs. Make, n8n und Custom GPTs07:40 Mindset Shift in der Agenturarbeit10:34 AI Visibility messen: Warum eigene Reports entstehen12:26 Prompt Research, Synonyme und Query Fanouts20:06 Reporting über ChatGPT, AI Mode, AI Overviews und Perplexity24:14 Welche Modelle werden abgefragt?25:00 Sentiment Deep Dive: Warum Erwähnung nicht reicht28:56 Digital PR und Social Listening mit KI31:00 Automatisierte Kampagnen und Content Assets33:12 Landingpages in Minuten statt Wochen36:04 Content Workflows mit Guidelines, SERPs und Deep Research40:39 Beispiel: KI-generierter Ratgebertext43:46 Daily Routine in einer KI-zentrierten Agentur46:34 Warum KKP trotz Automatisierung weiter einstellt48:50 Kosten und Tooling rund um Claude Code50:33 Braucht man künftig noch klassische CMS?53:17 DataForSEO, Agentur-Brain und Skill-Setup54:39 MCP vs. API55:13 Qualitätssicherung und Versionierung57:42 Abschluss & Hinweis auf SISTRIX MCP / Prompt Research

The gang have a competency porn montage----------------------------------------For a full visual experience of a classic episode head to our ⁠⁠YouTube channel⁠----------------------------------------If you like what you hear please support the show at ⁠⁠⁠⁠Patreon⁠⁠⁠⁠ to get early access, exclusive content and moreALSO - we have new merch with the amazing Patreon feed cover art by the legendary Stefan Poag, you can find all manner of ways to drape these horrifying visages on your body at our ⁠⁠Redbubble Store⁠Wally Van Der Meer is played by Jenny at GrimHumorMagnus Daintry is played by Scott Dorward from Good Friends of Jackson EliasNorm O'Neill is played by Spencer Game of Keep Off the BorderlandsBT Raven is played by Barney from Loco LudusKeeper - Andy Goodman from Expedition to the Grizzly Peaks

Thanks to our Partners, Pico Technology and AutelWatch Full Video EpisodeIn this episode, Matt Fanslow uses Game of Thrones, specifically the arc of Daenerys Targaryen, as a metaphor for what can happen when a mechanical or technical specialist moves from employee to shop owner. The comparison is not that former technicians suddenly “burn everything to the ground,” but that people can start with strong ideals, endure pressure, accumulate responsibility, and slowly rationalize decisions they once hated from the other side of the counter.Matt draws a parallel between Daenerys' journey, from abused and powerless exile to powerful ruler, and the path of a technician who opens a shop after years of saying, “If I were in charge, I'd do things differently.” At first, that new owner may try to build the kind of workplace they always wanted: better pay, better equipment, better treatment, and fewer manipulative incentive structures. But then reality intrudes. Bills come due. Tooling, software, subscriptions, payroll, benefits, facility costs, and client pressure pile up. What once looked like greed from the employee side may start to look like survival from the owner side.A major thread in the episode is the difference between explaining behavior and excusing it. Matt is careful not to justify poor management, bad pay plans, or unfair treatment. Instead, he looks at how stress, fear, frustration, and financial pressure can slowly change a person's beliefs. The former employee who despised production-based pay may eventually install a production-based pay plan. The shop owner who wanted to buy the best equipment may eventually stop doing that when employees fail to care for it. The person who promised to never become “that owner” may wake up, or perhaps never wake up, having become very close to the thing they once opposed.The episode also touches on incentive design. Matt discusses how incentive-based pay plans can increase production, but only if the surrounding system is fair. When a mechanical or technical specialist is paid based on production, but too many external forces affect their ability to produce, the pay plan can feel like punishment. Dispatch, workflow, parts delays, bad information, poor estimating, broken processes, and uneven support can all take money out of the worker's hands. In that environment, the game feels unfair, even if the pay plan itself is not inherently unethical.Matt argues that pay plans should not be used as a substitute for management. A compensation structure cannot do the work of leadership, communication, process improvement, fairness, and accountability. Straight hourly can work. Flat rate can work. Hybrid incentive plans can work. But none of them work automatically, and none of them remove the need for honest management and honest self-assessment.The larger point is that people rarely change all at once. They shift slowly. The language changes first. Then the justifications. Then the policies. Then the culture. Like Daenerys, the fall is not simply about one bad decision at the end. It is the accumulated effect of pressure, loss, betrayal, fear, and power.Matt closes by reflecting on Game of Thrones itself, noting that the show was among the best when it was at its peak, even if the ending remains debated. He suggests that Daenerys' storyline may be worth revisiting not just as fantasy, but as a study in how ideals can erode when pressure, power, and isolation build over time.Key TopicsThe former technician turned shop owner: The episode examines what happens when someone who once criticized shop ownership suddenly has to carry the risk, payroll, bills, tooling costs, subscriptions, client demands, and employee issues themselves.Daenerys Targaryen as a shop-owner metaphor: Daenerys begins with a desire to break abusive systems, but eventually becomes capable of the very behavior she once opposed. Matt uses that arc to frame how former employees can become the kind of owners they used to resent.Explaining versus excusing: A central distinction in the episode is that understanding why owners behave a certain way does not automatically make those behaviors right.Incentive pay and production pressure: Production-based pay plans can produce measurable gains, but they also create resentment when employees are held accountable for factors outside their control.The danger of using pay plans as management: Matt argues that compensation systems cannot replace leadership, process design, accountability, and honest communication.Stress, fear, and rationalization: The episode explores how frustration, anxiety, financial pressure, and disappointment can slowly alter a person's beliefs and management style.The slow drift into becoming what you opposed: The episode's core warning is that becoming “that owner” usually does not happen in one dramatic moment. It happens one rationalization at a time.Quotes“When enough people make false promises, words stop meaning anything. Then there are no more answers, only better and better lies.”“We have to be able to explain things without excusing them.”“The pay plan cannot be the manager.”“You can have a straight hourly shop where production is good. You can have a flat-rate shop where people are happy. But neither one happens by accident.”“A production incentive becomes punishment when too many things outside the employee's control take money out of their hands.”“A lot of people do not become bad owners all at once. It is slow, and then all at once.”“The danger is not just power. It is pressure, fear, frustration, and then the story we tell ourselves afterward.”Thanks to our Partner, Pico TechnologyAre you chasing elusive automotive problems? Pico Technology empowers you to see what's really happening. Their PicoScope oscilloscopes transform your diagnostic capabilities. Visit PicoAuto.comThanks to our Partner, AutelFrom drivability diagnostics and TPMS service to ADAS and advanced safety systems, Autel helps technicians follow OEM procedures and repair with confidence. Learn more at Autel.comContact InformationEmail Matt: mattfanslowpodcast@gmail.comDiagnosing the Aftermarket A - Z YouTube ChannelThe Automotive Repair Podcast Network: https://automotiverepairpodcastnetwork.com/Remarkable Results Radio Podcast with Carm Capriotto: Advancing the Aftermarket by Facilitating Wisdom Through Story Telling and Open Discussion. https://remarkableresults.biz/Business by the Numbers with Hunt Demarest: Understand the Numbers of Your Business with CPA Hunt Demarest. https://huntdemarest.captivate.fm/The Auto Repair Marketing Podcast with Kim and Brian Walker: Marketing Experts Brian & Kim Walker Work with Shop Owners to Take it to the Next Level. https://autorepairmarketing.captivate.fm/The Weekly Blitz with Chris Cotton: Weekly Inspiration with Business Coach Chris Cotton from AutoFix - Auto Shop Coaching. https://chriscotton.captivate.fm/Speak Up! Effective Communication with Craig O'Neill: Develop Interpersonal and Professional Communication Skills when Speaking to Audiences of Any Size. https://craigoneill.captivate.fm/

Wie hat dir die Folge gefallen?Gut

Send us Fan MailWe back guest Joshua Bowers about a year after his last appearance, this time with show-and-tell including the Steel Driver rotary that emulates a coil stroke, the Heavy Hand weighted pencil grip (plus an Apple Pencil prototype), and a battery adapter that turns a battery into a power supply and can shift weight off the machine. They discuss foot switches vs wireless/constant-on setups, cord management, and why many artists return to coil-style performance after starting on pen machines. The conversation shifts to how social media escalates tattoo drama into public “movements,” online validation, and public therapy, including examples of inflammatory accusations and appropriation debates. They also warn about corporate consolidation and looming regulations that could price out small makers.Support the show

Matt Paige and Thomas Schlossmacher discuss a shift from typing to talking as AI makes voice dictation accurate enough to use without constant corrections, arguing speech is faster and more natural and helps maintain thought flow when interacting with AI tools.Schlossmacher is building Resonant, a Mac voice dictation tool designed to run on-device so nothing goes to the cloud, motivated by privacy concerns and data retention/training practices of cloud-based alternatives like Whisper Flow.They explore the tradeoffs of local vs server inference, noting current consumer hardware can struggle to run full speech-to-text plus LLM post-processing fast enough, but expects improvement in 1–2 years.Schlossmacher explains differentiators like taste/brand, his design workflow using inspiration sources and ShadCN, his path into AI-assisted building, his stack (Claude Code, Next.js, Convex, Vercel), and a vision for proactive, context-aware agent features and potential open-sourcing and enterprise/self-hosted options, with beta/free access at https://www.onresonant.com/.--Key Moments:01:47 Making the Switch05:00 Why Build Resonant08:25 Local LLM Reality Check11:23 Standing Out in AI14:52 Designing Resonant Brand19:16 Building Taste Systems22:25 Learning to Build Apps23:43 Early Computer Curiosity25:41 Entrepreneur First and AI Shift27:49 Teaching Yourself with Agents29:05 Tooling and Tech Stack31:05 Resonant Product Vision35:14 Proactive Voice Workflows36:42 Beta Launch and Monetization41:15 Where to Try Resonant--Key Links:ResonantConnect with Thomas on LinkedInMentioned in this episode:Free report from HatchWorks AI — State of AI 2026What's real in AI this year, what's hype, and what leaders should prioritize — including production lessons, designing for agents, and governance. https://hatchworks.com/state-of-ai-2026/AI Opportunity FinderFeeling overwhelmed by all the AI noise out there? The AI Opportunity Finder from HatchWorks cuts through the hype and gives you a clear starting point. In less than 5 minutes, you'll get tailored, high-impact AI use cases specific to your business—scored by ROI so you know exactly where to start. Whether you're looking to cut costs, automate tasks, or grow faster, this free tool gives you a personalized roadmap built for action.

Jack Cochran and Matthew James welcome Kintan Brahmbhatt, CEO and co-founder of Olto, to discuss how AI agents are fundamentally reshaping the presales workflow and buyer experience. Drawing from over 12 years at Amazon building personalized experiences for Alexa, Amazon Music, and Prime Video, Kintan explores why B2B buyers receive generic "Acme Corp" demos while B2C consumers get highly personalized recommendations, and how product-trained agents can finally close this gap economically. The conversation goes beyond productivity gains to examine how buyers, products, and SE roles have evolved rapidly while metrics, compensation plans, and tooling have remained static.  Follow Us Connect with Jack Cochran: https://www.linkedin.com/in/jackcochran/  Connect with Matthew James: https://www.linkedin.com/in/matthewyoungjames/  Connect with Kintan Brahmbhatt: https://www.linkedin.com/in/kintan/  Links and Resources Mentioned Join Presales Collective Slack: https://www.presalescollective.com/slack  Sol/Con 2026 (Chicago, August 2026): https://www.presalescollective.com/solcon-2026  Olto: https://olto.com/psc  (3 months free promotional offer mentioned) Key Topics Covered Why AI Timing Is Better Now: Moving Beyond Productivity to Workflow Transformation The Personalization Gap Between B2C and B2B Buyer Experiences What Olto Is: Product-Trained AI Agents Across the Revenue Journey Kintan's Amazon Background: Building Personalized Experiences at Scale SE Capacity Economics and the Unspoken Rule About Qualified Deals How Product-Trained Agents Differ from Generic AI The New SE Workflow: Agents Handle Discovery, SEs Focus on Sense-Making Evolution of SE Metrics, Compensation, and Tooling for the AI Era Implementation Challenges and Change Management The Future of the Presales Profession Timestamps 00:00 Welcome 04:04 Now vs a year ago 05:40 What is Olto 07:52 B2C vs B2B personalization disconnect 11:15 Agent capabilities and limitations 21:35 Future of the solutions roles 28:26 Key takeaways from solutions leaders

Tommy Grot talk about his "tools.virtualbytes.io tools, how they work and how he built them by converting anisible scripts with AI. Tony Foster and Eric spend time talking about Tommy's basement setup and how he manages it and his tools.

Parce que… c'est l'épisode 0x2F3! Shameless plug 9 au 17 mai 2026 - NorthSec 2026 3 au 5 juin 2026 - SSTIC 2026 24 et 25 juin 2026 - Troopers 26 et 27 juin 2026 - leHACK 19 septembre 2026 - Bsides Montréal 1 au 3 décembre 2026 - Forum INCYBER - Canada 2026 24 et 25 février 2027 - SéQCure 2027 Description Présentation des invités Dans cet épisode technique de Polysécure, l'animateur reçoit deux analystes de l'équipe TDR (Threat Detection and Research) de Sekoya. Charles Meslay se spécialise en reverse engineering et en analyse de malware, tandis que Félix Aimé se concentre sur l'étude de campagnes liées à des États — cyberespionnage, sabotage — et joue un rôle central dans le développement d'outils internes pour mener les investigations. L'épisode prend appui sur un billet de blog récemment publié par l'équipe portant sur une campagne d'APT28, groupe étatique lié à la Russie, pour élargir la discussion à l'ensemble du tooling utilisé en CTI. Du reverse engineering manuel à l'automatisation Le point de départ concret est l'analyse d'un malware écrit en .NET, attribué à APT28 et découvert début 2025. Initialement, le travail reposait sur des outils classiques comme dnSpy : une interface graphique permettant de décompiler le code, de renommer les fonctions et de comprendre progressivement leur logique. Ce processus, bien que relativement accessible, est extrêmement chronophage — de une à trois semaines par binaire et par analyste. Avec l'émergence des LLM, Charles a d'abord commencé à copier-coller manuellement des portions de code dans ChatGPT pour accélérer l'analyse. Cette pratique l'a conduit à une idée d'automatisation : la création d'un serveur MCP (Model Context Protocol), un protocole permettant à un LLM d'interagir avec des outils externes via une interface de type API. Ce serveur, mis en open source, est en réalité une brique d'un outil plus large développé en interne : Sara. sarA : un orchestrateur d'analyse automatisée Sara est présentée comme le cœur de l'écosystème d'analyse de Sekoya. Son fonctionnement est le suivant : on lui soumet un fichier, le LLM identifie le type de fichier et sélectionne les outils adaptés — qu'il s'agisse de Ghidra, d'IDA Pro ou d'outils maison en ligne de commande — pour procéder à l'analyse. À l'issue du processus, Sara génère un rapport structuré comprenant la description du comportement du binaire, les différentes couches d'obfuscation détectées, des scripts de désobfuscation si nécessaire, et une liste explicite des angles morts de l'analyse, notamment en cas de limitations liées aux tokens ou au nombre de passes effectuées. Le gain est spectaculaire : le temps d'analyse est passé de plusieurs semaines à quelques minutes. Au-delà du gain de vitesse, Sara a également élargi le cercle des analystes capables de contribuer au reverse engineering, y compris ceux qui n'avaient pas de formation approfondie dans ce domaine. Les analystes spécialisés, comme Charles, continuent quant à eux à intervenir sur les cas complexes que l'outil ne résout pas seul. Un écosystème d'outils progressivement construit Félix retrace l'histoire du tooling interne, développé de façon itérative au fil des années. Au départ, l'équipe disposait d'un simple serveur de cache connecté à des API tierces comme VirusTotal, permettant de limiter la consommation de quotas. Ce serveur a ensuite été refondu pour gérer de manière transparente les clés d'API, simplifiant ainsi la vie des développeurs internes. L'équipe a ensuite créé un ensemble d'API maison pour automatiser des tâches courantes : requêtes DNS, récupération de plages d'IP sur des AS, etc. Ces briques ont permis de construire 150 transformes pour Maltego, un logiciel d'analyse permettant d'appliquer des micro-opérations sur des entités (adresses IP, noms de domaine, etc.) afin d'enrichir les investigations. Aujourd'hui, l'équipe envisage de migrer vers Flosint, une solution open source française au fonctionnement similaire. Pour le suivi dans le temps des infrastructures malveillantes, deux outils ont été développés. Tracker interroge des services comme Shodan, Censys ou VirusTotal avec des règles précises pour surveiller en quasi-temps réel des infrastructures ou des malwares. Irma, plus orientée vers le hunting, permet d'initier des investigations à partir d'heuristiques poussées — par exemple, détecter un nom de domaine enregistré chez un registraire douteux qui résout vers un routeur potentiellement compromis en France. L'ergonomie au cœur du développement Un principe philosophique fort ressort de l'échange : l'ergonomie prime sur la complexité technique. Félix insiste sur le fait que les outils en ligne de commande, aussi puissants soient-ils, finissent par être abandonnés si leur utilisation requiert de consulter le manuel à chaque fois. L'objectif est que l'intégralité des outils soit accessible depuis un navigateur web, via des sous-domaines dédiés, avec une interface de recherche permettant de trouver un outil par mot-clé (par exemple, taper « LLM » pour lister tous les outils liés à l'intelligence artificielle). Cette centralisation présente plusieurs avantages : harmonisation des dépendances, déploiement automatisé via des pipelines CI/CD, et adoption effective par l'ensemble de l'équipe. Comme le résument les deux invités, un outil que personne n'utilise ne vaut rien — peu importe ses capacités techniques. L'IA comme accélérateur transversal L'arrivée des LLM a transformé deux autres facettes du travail. D'abord, le prototypage : là où il fallait parfois des semaines pour valider une preuve de concept, quelques heures suffisent aujourd'hui pour déterminer si une idée mérite d'être poursuivie ou abandonnée. Ensuite, la capitalisation du renseignement. L'équipe ingère des rapports publics d'éditeurs tiers, les modélise au format STIX — un standard structuré d'objets liés (campagnes, groupes d'attaquants, indicateurs de compromission) — et enrichit sa base de connaissance. Ce travail, autrefois fastidieux et manuel, est aujourd'hui en grande partie automatisé grâce aux LLM, avec une revue humaine finale. L'analyste se retrouve alors libéré des tâches répétitives pour se concentrer sur ce qui reste hors de portée de l'IA : la création de règles YARA, le développement de trackers d'infrastructure, et l'identification de détails techniques fins qui nécessitent encore un vrai jus de cerveau. Conclusion Cet épisode offre un regard rare et concret sur le quotidien d'une équipe CTI de pointe. Entre automatisation intelligente, philosophie d'ergonomie et intégration progressive de l'IA, Charles et Félix décrivent un métier en pleine mutation — où l'analyste humain reste indispensable, mais se concentre désormais sur ce qu'il fait le mieux. Notes APT28, sarA Is watching you! Collaborateurs Nicolas-Loïc Fortin Charles Meslay Félix Aimé Crédits Montage par Intrasecure inc Locaux virtuels par Riverside.fm

Greg Hinkle, co-founder of Nimbalyst and former VP of Software Engineering at Salesforce, joins Scott to discuss the future of AI-assisted development. They explore the challenges of managing multiple AI coding agents, finding flow state in an agentic world, and why visual workspaces matter. Greg shares Nimbalyst's opinionated approach to integrating tools like Excalidraw, task management, and session organization directly into the developer workflow. https://nimbalyst.com

Wie hat dir die Folge gefallen?Gut

https://clearmeasure.com/developers/forums/ Chet Husk is a Product Manager on the .NET Tools team at Microsoft, where he leads the .NET SDK, MSBuild, Template Engine, and Install Scripts teams -- shaping how millions of .NET developers build, publish, and containerize their applications. Before joining Microsoft in 2021, Chet was deeply embedded in the F# open-source community, serving on the F# Software Foundation Board and co-maintaining Ionide, the popular F# extension for VS Code. At Microsoft, he drove the built-in container publishing support that lets developers create container images with just "dotnet publish" -- no Dockerfile required -- and recently shipped SLNX, the new XML-based solution file format for the .NET CLI. He is also exploring the intersection of AI and build tooling with an open-source MCP server that lets AI assistants analyze MSBuild binary logs. Mentioned in this Episode GitHub LinkedIn .NET Blog Recent projects / posts Blog: "Introducing support for SLNX, a new, simpler solution file format in the .NET CLI" (Mar 2025, .NET Blog)  mcp-binlog-tool: MCP server for AI-assisted MSBuild binary log analysis  Blog: "Announcing built-in container support for the .NET SDK" (.NET Blog) .NET Conf 2023 talk: ".NET Containers advancements in .NET 8"  .NET Conf 2022 Keynote presenter  SLNGEN .NET Tool /dotnet/skills GitHub repo structed nuget package - devlooped EBNF Grammar (Extended Backus–Naur Form) https://msbuildlog.com/ https://github.com/devlooped/StructId Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Welcome back Matt Liberty (Joulescope) and Luke Beno (Werewolf.us) Matt has been a guest on episodes 527 and 607 Luke was a guest on episode 272 Luke launched a new cable manufacturing and power supply company in the US called Werewolf.us Matt is working on the JS320 We discussed how PartsBox is a great ERP solution but Matt and Luke decided to go fully custom with Claude Code. Jan Rychter was a guest on episode 542 We discussed the differences with Product Lifecycle Maintenance. Michael Corr of the recently acquired Duro Labs was on episode 577 CAM workflow A fully verticalized PCB factory is something Jonathan Hirschmann talked about on episode 299 Jeff Bezos is investing 100B in a fund that is looking at automation in the factory using AI Matt recently had success with Claude Code and verilog programming Saleae for hardware in the loop using their APIs Other tools to check out pyelf pdfdk blast superpowers skill (by past guest at Teardown Jesse Vincent) Luke used OpenClaw to power a chat agent in his ERP system Working with distributors TI backlog Chris recently learned that Digikey has a developer API Cocotb verification framework (in Python) Luke is working on vision experiments for inhouse developed AOI solutions

What do you do when your entire business model collapses almost overnight? For Sven Klatt and the team at Vineburg Machining, the answer wasn't to retreat—it was to reinvent. After losing their three largest customers to overseas outsourcing in the early 2000s, the company made a bold decision: walk away from high-volume commodity work and rebuild from the ground up around complex, high-mix machining that couldn't easily leave the U.S. That transformation didn't just change what they made—it changed how they thought. From investing in CNC technology to embracing five-axis machining, Vineburg steadily evolved into a shop capable of tackling highly technical aerospace and defense work. But even with three shifts running, Sven kept running into the same frustrating reality: too many machines sitting idle when people weren't there to run them. Instead of accepting that limitation, he decided to solve it. What started as a rough sketch for a better pallet system turned into a fully functional in-house automation solution—one designed specifically for high-mix environments, tight shop footprints, and real-world machinist workflows. After years of testing, breaking, and refining, that internal tool became something much bigger. In this episode, Sven shares the full journey—from survival-driven reinvention to building a lights-out automation system that now powers their shop and has entered the market through a strategic partnership. Along the way, he reveals hard-earned lessons on risk-taking, continuous improvement, workforce challenges, and what it really takes to maximize spindle uptime without burning out your team. You will want to hear this episode if you are interested in... (3:11) Sven's journey to Vineburg and the shop's high-volume origins (8:06) Investing in five-axis machining and unlocking new growth (11:17) Running three shifts and maximizing shop flexibility (14:02) The problem: idle machines and limited labor capacity (16:24) From failed purchase to building a custom solution in-house (19:52) Prototyping, testing, and proving the system in production (21:06) Using automation to extend machining hours and increase uptime (23:19) Check out the Hennig WorkFlow pallet automation system (24:10) Winning work through value, capability, and risk-taking (28:01) Standardizing production and improving customer partnerships (30:14) Designing the system: footprint, capacity, and simplicity (37:21) Making the system operator-friendly with intuitive controls (39:38) Head to the DN Solutions Manufacturing Without Limits event (40:36) The impact of the pallet system on Vineburg Machining (42:12) Tooling, process control, and making lights-out reliable (47:30) Scaling automation to reduce reliance on night shifts (49:59) Get a free report of opportunities in your industry from FacturMFG.com/chips (53:28) Partnering with Hennig to bring the product to market (56:26) The breakthrough moment and realizing its full potential (58:48) A shop could pay off the system within the first year (1:01:11) Lessons learned: testing, delegation, and stepping out of the bottleneck Resources & People Mentioned Check out the Hennig WorkFlow pallet automation system Head to the DN Solutions Manufacturing Without Limits event Get a free report of opportunities in your industry from FacturMFG.com/chips Connect with Sven Klatt Connect on LinkedIn Vineburg Machining  Connect With Machine Shop Mastery The website LinkedIn YouTube Instagram Subscribe to Machine Shop Mastery on Apple, Spotify

Today, in episode 324, Adrian is rewinding one of our most popular episodes ever: breaking down the New Product Introduction (NPI) process and why it's the difference between a smooth product launch… and a costly failure. If you've ever: Rushed into tooling too early Hit quality issues in production Faced unexpected delays or rising costs There's a good chance your NPI process wasn't solid. In this episode, Renaud and Adrian walk through what NPI actually looks like in practice, not theory, and how it helps you validate your design, test assumptions, and reduce risk before scaling production. What you'll learn What the NPI process really is (and what most people get wrong) The key stages: requirements → feasibility → prototyping → tooling → pilot run → mass production Why skipping steps leads to expensive problems later How to balance speed vs risk depending on your product and volume Real examples of what goes wrong without a structured process Why this episode matters Too many companies treat NPI as optional, or rush through it to “save time.” In reality, that's usually what creates: Quality failures Supplier issues Cost blowouts Delayed launches This episode explains how to avoid that.   Episode Sections: 00:00:12 — Introduction 00:02:24 — Rewind to the NPI Process 00:05:04 — Understanding the NPI Process 00:08:09 — Prototyping and Feasibility 00:12:57 — Tooling and Production Samples 00:18:01 — Pilot Run and Testing 00:20:56 — Assessing the NPI Process 00:26:08 — Balancing Risks and Quality 00:26:31 — Closing Remarks and Future Topics   Related content… The NPI Process (Includes graphic) Analysing the (NPI) New Product Introduction Process & its Benefits [Podcast] The New Product Introduction Process Guide (Long Read) Remember, we can help you develop and manufacture your new product following our structured NPI process to reduce your risks, and more.   This episode is brought to you by The Sofeast Group and includes links in the show notes to our blog posts and resources, and recommended books. For help with manufacturing in Asia, inspections, auditing, new product development, contract manufacturing, 3PL warehousing and fulfillment, visit sofeast.com.  Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB

Monorepo, Polyrepo, Frontend hier, Backend dort, Mobile-App nochmal woanders. Klingt nach sauberer Trennung, führt in der Praxis aber oft zu genau dem, was wir als Entwickler:innen am wenigsten brauchen: Reibung. Abhängige Pull Requests, aufeinander wartende Releases, doppelte Tooling-Arbeit und jede Menge Koordination zwischen Teams. Die spannende Frage ist also nicht nur, ob Monorepos ein Comeback feiern, sondern ob sie heute, mit besserem Tooling und AI im Rücken, endlich ihr Versprechen einlösen.In dieser Episode sprechen wir mit Max Kless, Senior Software Engineer bei Nx, über den aktuellen Stand von Monorepos. Wir klären, was ein Monorepo eigentlich ist, warum Monorepo nicht gleich Monorepo ist und wieso ein pragmatischer, hybrider Ansatz für viele Teams sinnvoller ist als ein einziges gigantisches Repository. Außerdem schauen wir auf CI, Caching, Project Graphs, Code Ownership, Plattform-Teams und die kulturelle Seite hinter dem Thema. Denn Monorepos sind nicht nur Architektur und Tooling, sondern auch Zusammenarbeit, Standards und ein bisschen Inner Source im Alltag.Besonders spannend wird es bei AI, LLMs und Coding Agents. Wenn mehr Kontext zu besserer Unterstützung führt, werden Monorepos plötzlich wieder hochrelevant. Wir diskutieren, warum ein gemeinsamer Code-Kontext für AI-Systeme ein echter Hebel sein kann, wo die Grenzen liegen und worauf du bei einer Einführung achten solltest. Wenn du wissen willst, ob Monorepos 2026 mehr sind als alter Google-Glanz, dann bist du hier genau richtig.Bonus: Selbst Jenkins bekommt einen kleinen Ehrenmoment.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Guy and Eitan discuss several very interesting new features recently announced by Microsoft. Relevant links for more info: Stop defragmenting and start living: introducing auto index compaction | Microsoft Community Hub Automatic Index Compaction - SQL Server | Microsoft Learn Database DevOps (preview) in SSMS 22.4.1 | Microsoft Community Hub Manage SQL database schemas in VS Code: Publish dialog and item templates - Azure SQL Dev Corner Publish SQL Database Projects from Visual Studio Code - SQL Server | Microsoft Learn SQL code analysis in VS Code: Configure rules without editing your project file - Azure SQL Dev Corner SQL Projects Roadmap - DacFx Wiki Author Custom Code Analysis Rules - SQL Server | Microsoft Learn

Getting your product to market is one thing. Making sure it's profitable is another. In this episode, Adrian is joined by Paul Adams to break down how product costs really work, and why so many teams get it wrong. From BOM and tooling to logistics and hidden costs, they walk through what goes into your final unit price and how to avoid nasty surprises before launch. They also explore practical design-to-cost strategies, including value engineering, supplier decisions, and smart trade-offs that can significantly reduce costs without compromising quality. If you're developing a product and want to protect your margins, this episode will help you think about cost the right way: early, holistically, and strategically.   Episode Sections: 00:00:12 — What Is Design-to-Cost? 00:00:49 — Why Costing Is Often Overlooked 00:01:55 — The 4 Core Cost Drivers (BOM, NRE, Tooling, Logistics) 00:05:24 — Value Engineering & Smarter Design Decisions 00:08:54 — Reducing Assembly Cost & Complexity 00:10:10 — Supplier Strategy: Cost vs Quality Trade-offs 00:12:20 — Tooling Costs & Budget Pitfalls 00:15:04 — NRE Explained: Hidden One-Time Costs 00:19:40 — Logistics: The Most Underestimated Cost 00:22:52 — Design for Cost: How to Reduce Product Cost 00:28:08 — Why You Must Think About Cost Early 00:31:47 — Biggest Costing Mistakes to Avoid   Related content… Design for Manufacturing (DFM) Why Product Idea Validation Is Crucial Before Spending Big on Development Product Design Cost: 10 Factors That Affect Electronic Products The Benefits of a Feasibility Study (during new product development) 7 Must Do New Product Introduction Tasks For Successful Product Launches The Design for X Approach: 12 Common Examples   This episode is brought to you by The Sofeast Group and includes links in the show notes to our blog posts and resources, and recommended books. For help with manufacturing in Asia, inspections, auditing, new product development, contract manufacturing, 3PL warehousing and fulfillment, visit sofeast.com.    Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB

In this episode of The Fleet Success Show, RTA VP of Product, Marc Canton. sits down with Jake Johnson, former fleet maintenance supervisor and current RTA Fleet Success Manager, to break down one of the most critical and misunderstood topics in fleet: outsourcing. Whether you're a government fleet manager with limited resources, a trucking fleet with scale, or just trying to figure out how to do more with fewer techs, you're probably outsourcing more than you think—and leaving data and dollars on the table if you're not managing it properly. Jake brings his 20+ years of hands-on and leadership experience in trucking fleets to share how to decide what to send out, how to build strong vendor relationships, and how to track outsourced work like you would your own shop.   Key Takeaways Don't outsource blindly: Use VMRS codes to evaluate where you're spending the most time and money to decide what to outsource... and what to train for instead. Tooling and training determine viability: If your team lacks the tools or training, and it's not cost-effective to invest—send it out. Vendor performance must be tracked: Track vendor jobs like in-house work, with proper work orders, status updates, and SLAs for turnaround and comeback rates. Use outsourcing to protect your tech bandwidth: Don't send out the big, expensive job if small ones can be sublet faster and cheaper, freeing your shop for higher-value work. Relationships matter: Vendor partnerships should be built on honesty, clarity, and expectations. Think long-term and treat vendors like part of your team. Speaker Bios Jake Johnson Fleet Success Manager at RTA, Jake spent two decades working his way up from diesel tech to service manager to fleet leader in trucking operations. He now helps fleets across the country optimize everything from shop staffing to outsourced vendor networks. Marc Canton VP of Product & Consulting at RTA, Marc is a fleet operations veteran and co-host of The Fleet Success Show. He blends hands-on consulting experience with strategic leadership across public and private sector fleets.   Looking to take the next step to fleet success? Start by requesting your free copy of The Fleet Success Playbook. Written by fleet professionals for fleet professionals, the Playbook breaks down the four key pillars of fleet success, and gives you the tools you need to build a truly great fleet. Request your free (yes, really, free!) copy here: https://rtafleet.com/resources/fleet-success-playbook?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213 Control fleet chaos with RTA Fleet360, proven software designed by fleet managers for fleet managers: https://rtafleet.com/book-a-demo?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213

Your tool set isn't just a collection of utilities — it's the environment you live in every day, and it's shaping you whether you realize it or not. In today's episode, I explore two principles that senior engineers consistently apply to their workflows, regardless of which specific tools they're using. As our industry goes through one of the most rapid periods of change in the last 20 years, the engineers who thrive won't be the ones chasing every new tool — they'll be the ones who obsess over reducing friction in the work they do most often. Honor the Grief: Many engineers are experiencing a real sense of loss as the deep cultural connections to languages, communities, and hand-written code begin to shift. Recognizing and processing that grief — rather than letting it turn into reflexive rejection of new tools — is essential to thinking clearly about what comes next. "We Shape Our Tools, Then Our Tools Shape Us": Your tools aren't neutral. A bad monitor height, a faulty keycap, or a clunky deployment process all shape you back — draining focus, breaking flow, and compounding over time. The most senior engineers treat this relationship as a first-class concern. Principle 1 — Tools Are Your Environment: There's a spectrum from "tool" to "environment," and most of what you work with sits somewhere in between. Your terminal, your desk, your claude.md file — all of these are environment. Sharpening your tools means shaping your environment, and shaping your environment is sharpening your tools. Friction Is the Lever: You don't need a dramatic overhaul to change your behavior. Tiny reductions in friction — a two-letter alias, a key binding to run tests, setting your shoes out the night before — have an outsized effect on how often you actually do the things you want to do. James Clear's Atomic Habits framework applies directly to engineering workflows. Principle 2 — First Order Thinking: Borrowed from Adam Savage's concept of "first order retrievability," the idea is simple: identify what you do most often and invest in making that better. Not faster, not just automated — better. If you do something a hundred times a day, even a small improvement compounds dramatically. Invest in the Fundamentals: Your standups, your one-on-ones, your specifications, your prompting skills — these are the repetitive, high-frequency activities where your biggest growth opportunities live. Stop assuming you've "arrived" on the basics just because nobody is giving you negative feedback. Episode Homework: Look around your workspace right now — physical and digital. Identify one thing you do repeatedly where friction is slowing you down or discouraging follow-through, and make one small change to reduce that friction today.

Most founders assume scaling means hiring. Jesse Hanley built a 7-figure SaaS and refused to. From Japan, Jesse runs Bento — a profitable email marketing platform — almost entirely on his own. In this episode, he explains why he turned down a ~$10M acquisition offer and the frameworks that make a one-person company possible today. Topics include: ● The “Main Quest vs Side Quest” framework for staying focused in an AI-everything world ● Why Jesse refuses to hire full-time employees (and his “cockroach business” philosophy) ● Turning down a ~$10M acquisition offer to protect his lifestyle ● How AI agents now handle support, bugs, and development tasks ● Building a new product in 5 days with AI that now generates ~$10K MRR ● The Max MRR framework that explains why SaaS companies plateau ● The revenue milestone that finally made him feel financially secure Tropical MBA is a podcast for entrepreneurs building location-independent businesses. Subscribe for weekly episodes on business, money, and the entrepreneurial lifestyle. Hang out exclusively with 7+ figure founders in DC BLACK Our sponsor, Bento - Email marketing for bootstrapped founders CHAPTERS (00:00:00) Solo Founder Lifestyle & Intro (00:03:16) Meet Jesse & Bento + Why Build Email SaaS (00:04:53) AI Models, Tooling & Product Direction (00:07:32) Work Grind, Family & Financial Goals (00:11:12) No Hiring, Contractors & AI Leverage (00:17:48) Main Quest vs Side Quest (Core Strategy) (00:22:13) Getting Customers, Self-Serve & Churn Limits (00:26:44) MRR, Pricing & Positioning (00:34:45) AI Workflows, Agentic Tools & Discipline (00:40:24) Revenue Goals, Daily Routine & 4-Hour Vision CONNECT: Dan@tropicalmba.com Ian@tropicalmba.com Past guests on TMBA include Cal Newport, David Heinemeier Hannson, Seth Godin, Ricardo Semler, Noah Kagan, Rob Walling, Jay Clouse, Einar Vollset, Sam Dogan, Gino Wickam, James Clear, Jodie Cook, Mark Webster, Steph Smith, Taylor Pearson, Justin Tan, Matt Gartland, Ayman Al-Abdullah, Lucy Bella. PLAYLIST: The $10K Projects You Never Do (AI Just Changed That) How to Build a 6-Figure Digital Business with Claude Code 4 Ways to Start a Business From Scratch in 2026

Packtech Tooling, based in Cape Town and led by Kim Naran, sits at the start of that system. Packtech Tooling, a specialised manufacturing business based in Cape Town, has built a strong reputation within South Africa's printing and packaging sector. Founded by Werner Weber, the company supplies precision tooling to the printing, packaging and narrow web label industries across South Africa and parts of the African continent. Today, the business is headed by Managing Director Kim Naran, whose leadership reflects decades of hands-on industry experience.

Fortran. Eine Sprache von 1957. Und trotzdem taucht sie im TIOBE Index plötzlich auf Platz 12 auf. Zufall, Messfehler oder ein echtes Comeback in High Performance Computing? Wenn du Fortran bisher in die Schublade Legacy und Lochkarten gesteckt hast, wird diese Episode deine Perspektive ziemlich sicher verschieben.In dieser Interviewfolge nehmen wir Fortran auseinander, aber fair. Mit dabei ist Martin Diehl, Professor an der KU Leuven, Materialwissenschaftler und Open-Source-Contributor. Wir klären, warum Fortran für wissenschaftliches Rechnen gebaut wurde, warum Performance und Memory Layout bis heute zählen und weshalb du bei NumPy und SciPy oft indirekt Fortran-Code nutzt. Dazu geht es um Modern Fortran, Rückwärtskompatibilität, Module, Typensystem, Tooling, den Fortran Package Manager FPM sowie neue Compiler wie Flang und L Fortran auf LLVM-Basis.Zum Abschluss wird es HPC konkret. OpenMP für Shared Memory, MPI für Distributed Memory und als Fortran-Spezialität Co Arrays – quasi Shared-Memory-Feelings im Cluster. Wenn du wissen willst, ob Fortran Teil des Problems oder der Lösung im Two-Language-Dilemma ist, dann hör rein.Bonus: Naming is hard, aber F minus minus war schon eine Ansage.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Automation and lights-out manufacturing are often framed as the future of machining, but for many shops that future is already here. In this episode of MakingChips, we sit down with longtime industry leader Keith Grano to talk about what lights-out machining actually looks like in practice. Drawing on years of experience working with manufacturers, Keith explains how automation, machine monitoring, and disciplined processes allow shops to run more efficiently and extend production beyond the traditional workday. Lights-out machining isn't about replacing people. It's about using technology to make better use of the time, talent, and equipment already inside a shop. When done well, it increases capacity, improves consistency, and helps manufacturers grow even when skilled labor is limited. Keith walks through the practical considerations behind unattended production, including machine reliability, process stability, tooling strategy, and the systems required to keep parts running when no one is standing at the control. Along the way, we explore why many shops struggle to implement automation and why incremental steps often work better than trying to jump straight into fully autonomous production. This conversation also connects to a theme we've been exploring across our Generation CNC series: the next generation of manufacturing leaders is entering an industry where automation and digital systems are becoming foundational capabilities. Understanding how lights-out machining works, and when it makes sense, will shape how the next generation builds and scales their shops. Segments (1:28) Introducing Keith Grano and his background in manufacturing automation (3:06) What "lights-out machining" actually means in a modern shop (7:23) Why automation is about maximizing equipment and people, not replacing labor (12:09) The operational discipline required to run machines unattended (14:52) How ProShop ERP can help you achieve on-time delivery (20:11) Why process stability matters more than the machine itself (25:08) Tooling strategy, monitoring, and the systems that support unattended production (29:38) If you want the speed of AI without the risk, go to PaperlessParts.com (30:53) The mindset you need to have to implement lights-out machining (33:13) Where do you start with lights out automation?  (40:08) How to adjust your mindset to allow for automation (46:33) How machine monitoring and data change decision-making on the shop floor (51:27) Why we created Hire MFG Leaders (and why you should use it) (51:58) The most affordable way to automate a five-axis setup (58:54) How state, local, and federal grants can help cover purchases (1:00:47) How to determine what to charge for a machine's time  Resources mentioned on this episode Visit proshoperp.com/95 to get a free guide to achieve on-time delivery If you want the speed of AI without the risk, go to PaperlessParts.com Why we created Hire MFG Leaders (and why you should use it) ROI Calculator Connect With MakingChips www.MakingChips.com On Facebook On LinkedIn On Instagram On Twitter On YouTube

-A Cause for CONCERN Regarding Caserio's O-Line for these Texans..? -The Drive 'FAMILY' (that's YOU!) Sounds OFF on Texans/Caserio/O-Line! -Demand MORE, Demand SUCCESS from Your Team You FAN For!

Davy and PJ discuss why the future of design workflow isn't just better handoff—it's starting with the code itself.

Katherine O'Toole, National Tooling and Machining Association Executive Director | 2-23-26See omnystudio.com/listener for privacy information.

Good day ladies and gentlemen, this is IRC news, and I am Joy Stephen, an authorized Canadian Immigration practitioner bringing out this Canada Work Permit application data specific to LMIA work permits or employer driven work permits or LMIA exempt work permits for multiple years based on your country of Citizenship. I am coming to you from the Polinsys studios in Cambridge, OntarioNew Brunswick issued work permits between 2015 and 2024 for Machinists and machining and tooling inspectors under the former 4 digit NOC code 7231, currently referred to as NOC 72100.A senior Immigration counsel may use this data to strategize an SAPR program for clients. More details about SAPR can be found at https://ircnews.ca/sapr. Details including DATA table can be seen at https://polinsys.co/dIf you have an interest in gaining assistance with Work Permits based on your country of Citizenship, or should you require guidance post-selection, we extend a warm invitation to connect with us via https://myar.me/c. We strongly recommend attending our complimentary Zoom resource meetings conducted every Thursday. We kindly request you to carefully review the available resources. Subsequently, should any queries arise, our team of Canadian Authorized Representatives is readily available to address your concerns during the weekly AR's Q&A session held on Fridays. You can find the details for both these meetings at https://myar.me/zoom. Our dedicated team is committed to providing you with professional assistance in navigating the immigration process. Additionally, IRCNews offers valuable insights on selecting a qualified representative to advocate on your behalf with the Canadian Federal or Provincial governments, accessible at https://ircnews.ca/consultant.Support the show

Amit Chita is the Field CTO at Mend.io. In this episode, he joins host Paul John Spaulding to discuss the future of AI appsec tooling, including how AI should be used as a force multiplier, not a replacement, new risks, and more. Securing The Build is brought to you by Mend.io, the leading application security solution, helping organizations reduce application risk efficiently. To learn more about our sponsor, visit https://mend.io.

In this episode of Semaphore Uncut, Malcolm Matalka (Terrateam) discusses GitOps, Terraform tooling, OpenTofu workflows, and building developer tools that stay invisible. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

Today I'm joined by Stephanie Blair, Founder of Know & Flourish (https://knowandflourish.com/), for a practical conversation on digital career growth in Customer Success. We dig into how to build a career identity (not just a title), why experimentation matters, and how to expand your lane without burning out. You'll hear a real-world example from my team of turning a scrappy spreadsheet into a lightweight web tool, and what that kind of initiative can do for your brand inside the business.We also talk about the shift in CS org design: the rise of digital program managers, AI-assisted workflows, and yes - why human, IRL moments still win renewals. If you're exploring a pivot into CS (from sales/marketing/product) or within CS (service → expansion, or IC → leader), Stephanie breaks down how to translate your skills, control your narrative, and interview like a peer.Housekeeping: I'll be co-chairing the CS Summit in Austin later this month, and the Digital CX Masterclass is coming soon join the waitlist at https://DigitalCustomerSuccess.com/Masterclass to be first in line. Support the show+++++++++++++++++Like/Subscribe/Review:If you are getting value from the show, please follow/subscribe so that you don't miss an episode and consider leaving us a review. Website:For more information about the show or to get in touch, visit DigitalCustomerSuccess.com. Buy Alex a Cup of Coffee:This show runs exclusively on caffeine - and lots of it. If you like what we're, consider supporting our habit by buying us a cup of coffee: https://bmc.link/dcspThank you for all of your support!The Digital Customer Success Podcast is hosted by Alex Turkovic

Bitcoin Core doesn't stand still even if consensus rules don't change. In this episode, Stéphan (Core Developer at Brink) explains how the Kernel and multiprocess projects are reshaping Bitcoin Core for long-term reliability. From modular validation logic to safer development workflows, this conversation shows why maintenance work matters. Hosted by Shinobi of Bitcoin Magazine.#BitcoinCore #BitcoinDevelopment #BitcoinKernel ⭐️⚔: SIGN UP WITH DUELBITS TODAY FOR A CHANCE TO WIN UP TO 2 BTC:

AI agents aren't “coming” to Ethereum—they're already here, spinning up on dedicated machines, clicking through wallets, deploying contracts, and even building apps for themselves. In this episode, Ryan and David sit down with Davide Crapis and Austin Griffith to map the emerging agent stack: ERC-8004 as a decentralized identity + reputation layer, x402 as payment rails for agent-to-agent commerce, and the real-world “Clawdbot” experiments that show what happens when an agent gets a wallet, a codebase, and a mandate. Along the way: prompt-injection risks, why agents read calldata like it's their native language, and why it may be the best time in history to be a solo builder—even as it gets harder to be a junior dev. ---

Performance creative consultant Dara Denney joins the show to break down how modern brands are approaching creative strategy in 2026. The conversation opens with the shifting role of content creators versus strategists, and why creative velocity, operations, and in-house production are increasingly shaping how brands scale.From there, they dig into how AI is actually being used inside creative workflows - where it speeds up research and briefing, and where human judgment still matters, especially around roadmapping and idea selection. The group also explores the growing convergence of organic and paid, including how organic performance signals influence paid creative, why upper-funnel content belongs in performance accounts, and when “organic-first” ideas can still drive results.The episode wraps with a candid discussion on performance measurement beyond short-term ROAS, touching on creative diversity, upper-funnel impact, and how operators think about long-term growth when building scalable content systems.If you have a question for the MOperators Hotline, click the link to be in with a chance of it being discussed on the show: https://forms.gle/1W7nKoNK5Zakm1Xv6Powered by:Motion.⁠⁠⁠https://motionapp.com/?utm_campaign=marketing-operators&utm_medium=sponsor&utm_content=motion-sign-up&utm_source=marketing-operators-podcastMotion Creative Strategy Bootcamp.https://motionapp.com/2026-creative-strategy-bootcamp-paid?utm_campaign=marketing-operators&utm_medium=sponsor&utm_content=creative-strategy-bootcamp-2026&utm_source=marketing-operators-podcastPrescient AI.https://www.prescientai.com/operatorsRichpanel.https://www.richpanel.com/?utm_source=MO&utm_medium=podcast&utm_campaign=ytdescAftersellhttps://www.aftersell.com/operatorsHaushttps://haus.io/operatorsGet the 9 Operators Newsletterhttps://9operators.com/

A working prototype does not mean your product is ready for mass production. In this episode, our host Adrian and Paul Adams, Sofeast's head of NPD, explore a real-world case where ignored DFM feedback led to predictable, preventable, and extremely costly manufacturing issues. From tooling limitations to material behavior and assembly inconsistency, this conversation explains why DFM exists, and why skipping it can cost hundreds of thousands (or even millions) later.   Episode Sections: 01:17 – Why DFM feedback gets ignored (and why it's dangerous) 01:58 – Real case: prototype worked, DFM warnings dismissed 03:19 – What prototypes are actually meant to validate 04:56 – Why prototype tolerances don't match production reality 05:00 – Material differences: same polymer, different behavior 06:08 – Tooling realities: demolding, deformation, surface damage 07:02 – How cosmetic defects become functional failures 07:32 – Assembly inconsistency, labor costs, scrap, and rework 08:21 – Transport and environmental failures after launch 09:07 – The true cost of returns, warranty, and brand damage 09:53 – The cost multiplier: pre-tooling vs post-tooling fixes 10:34 – How rushing actually delays your launch 11:50 – Investor pressure and the hidden risk it creates 13:36 – Best practices: how DFM should really be used 14:48 – Why early CM involvement matters 16:41 – The role of NPI checklists and structured processes 18:06 – Final warning: don't ignore expert manufacturing feedback   Related content… Sofeast conducts your DFM review for Manufacturing in Asia The New Product Introduction Process Guide Handover to Manufacturing: What NOT to do & Best Practices Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB

⁠⁠⁠⁠

Crypto didn't remove trust — it refactored it.Which means the real question isn't whether blockchains work… it's whether the people who build them bear any responsibility for what happens next.In this episode we extend the previous conversation on crypto literacy, privacy UX, and incentive design to tackle a hard question with no clean answers:Do builders have responsibility beyond tooling?We explore the “blacksmith problem,” the myth of neutral systems, and how zero-knowledge, chain analysis, and UX choices shape outcomes — intentionally or not. This is not a price talk episode. It's about the ethics, incentives, and trade-offs embedded in decentralized infrastructure.Topics Covered • Crypto literacy and centralization of expertise • Privacy vs usability (and why it's not zero-sum) • Trust: from institutions → networks → intermediaries • The “neutral tools” dilemma in Web3 • When incentives create harm (and who owns it) • ZK systems, mixers, forensics, and emergent behavior • Builders vs system designers vs policymakersKey QuestionWhere does technical responsibility end, and ethical responsibility begin?If you're new hereThis episode continues directly from last week's cliffhanger. Go watch that one first if you want the full arc.Join the CommunityJoin the Discord for builders, OGs, privacy folks, ZK learners, and lurkers:(QR code in the video)Support the ShowLike, comment, subscribe, and clip moments that hit you. We actually watch them.For CommentersAnswer this in one word:Do builders have responsibility beyond tooling? — YES or NO?

Alex Merced talks about how his optimism about the Agentic AI tool and poses the question, if people can run as fast as they could before AI, instead of resenting them for it, ask yourself how much further you can now run with AI. Follow Alex on Social: AlexMerced.com The Data Lakehouse Community: https://www.datalakehousehub.com

In hour 3 of Steiny and Guru, the guys get further into the Warriors outlook and if trading Kuminga will bring them the right piece to help them reach a playoff berth. Plus, if they do re-tool will it be enough?

Marketing Update by KentonChad B. breaks down his new AI tooling agents that will help ship code and identify problems. A New Node Operator, DeFIRE, joins the space and talks about why he became a new Node Operator!

The ForgeCast is back! Sam is back in the host seat after nearly a year away from the internet, and he brought on a guest to help discuss why and how it all happened, as well as explore the nature of mental health and the effects smithing has on it. Carolyn Farris of Evergreen Forgeworks has dedicated her platform to journaling her experience as a smith, and also her struggles with anxiety, depression, and PTSD.

Why do so many AI rollouts stall right after the tools ship?In this episode of Alexa's Input (AI), Alexa talks with Melissa Reeve, author of the book Hyper Adaptive: Rewiring the Enterprise to Become AI Native, about what it actually takes to get AI adopted in large organizations.Melissa shares how her background in lean, Agile, and DevOps transformation shaped her view that AI adoption is less about “buying the tool” and more about rewiring how work happens. Together, they break down why many AI initiatives fail (and why ROI is slow), the FOCUS framework, the “AI time paradox,” and how support structures like AI activation hubs, social learning, and better success metrics can raise quality and accelerate impact.A must-listen for engineering leaders, product teams, and executives trying to move beyond pilots and turn AI into real operational leverage.Learn more about Melissa and Hyper Adaptive below.LinksWatch: ⁠⁠⁠https://www.youtube.com/@alexa_griffith⁠⁠⁠Read: ⁠⁠⁠⁠⁠https://alexasinput.substack.com/⁠⁠⁠⁠⁠Listen:⁠ https://creators.spotify.com/pod/profile/alexagriffith/⁠More: ⁠⁠⁠https://linktr.ee/alexagriffith⁠⁠⁠Website: ⁠⁠⁠https://alexagriffith.com/⁠⁠⁠LinkedIn: ⁠⁠⁠https://www.linkedin.com/in/alexa-griffith/⁠⁠⁠Find out more about the guest at:LinkedIn: https://www.linkedin.com/in/melissamreeve/Book: https://itrevolution.com/product/hyperadaptive/KeywordsAI adoption, enterprise transformation, Hyper Adaptive model, organizational change, DevOps, Lean, Agile, AI integration, customer-centricity, innovation accounting, social learningChapters00:00 Introduction to AI Adoption in Enterprises03:00 Melissa's Journey and the Foundation of AI Thinking06:06 The Analogy of DevOps and AI Implementation08:47 Cultural Shifts vs. Tooling in AI Adoption11:49 The Hyper Adaptive Model for AI Integration14:48 Sociology of Workflows and Organizational Change17:49 Understanding AI Initiative Failures21:00 Customer Centricity in AI Solutions23:58 The AI Time Paradox and Learning26:58 AI Activation Hubs and Their Role30:54 The Role of Human Oversight in AI Automation34:03 Incentivizing AI Engagement in Organizations35:59 Social Learning and AI: The Power of Collaboration40:57 Practical Applications of AI in Daily Life44:44 Quality vs. Productivity: The AI Dilemma46:13 The Focus Framework: Prioritizing AI Use Cases48:23 Influencing AI Adoption in Organizations51:07 The Future of Hyper Adaptive Organizations55:08 Decision-Making in the Age of AI57:37 Key Takeaways for Leaders in the AI Revolution

Some conversations feel scripted. This one… absolutely did not. Larry Robbins walked in ready to talk life, passion, family, culture, workholding, philosophy, and whatever else popped into his head — and somehow it all connected back to manufacturing. This episode of MakingChips is one of the most unhinged, hilarious, honest, and wisdom-packed conversations we've ever recorded. Larry has been in the industry for nearly 46 years, and he's collected enough stories, scars, and laughs for ten careers. From his father dragging him into the business ("long hair doesn't work here") to his famous explanation that SMW makes "magic hands," Larry blends humor and experience into lessons every shop owner needs to hear. His passion for the industry is unmatched — and his candor is even better. Throughout the episode, the crew dives into culture, leadership, lying (don't), modularity, flexibility, high-density workholding, predictable setups, financing equipment, and why you should stop crawling across a dollar to pick up a dime. Larry opens up about the future of manufacturing, warns against bad advice, and reminds everyone that machining touches every single thing in the world. If you're ready for an episode that's equal parts educational and unhinged in the best possible way, buckle up — Larry Robbins is in rare form. Segments (1:00) Larry's background, early failures, and the stories that shaped his approach to leadership (3:31) An investment in ProShop is an investment in your business (3:32) Culture, loving your work, and leadership lessons (5:07) Entering the family business, retirement humor, and long-term commitment (7:23) The reality of workplace culture, honesty, and handling difficult employees (10:02) Integrity, truth-telling, and early lessons on character (13:18) Appreciating machinists and the unseen parts of manufacturing (15:05) Workholding vs. cutting tools and why workholding matters more than people think (16:09) "Magic hands" — Larry's explanation of workholding for a 5-year-old (17:20) Workholding misconceptions and the cost of poor setups (19:00) Vendor trust, trying equipment, and choosing partnerships wisely (20:22) Setup reduction, rigidity vs. flexibility, and predictable processes (22:12) Cutting 12-hour setups and the value of internal vs. external setups (24:16) Why we love Phoenix Heat Treating for Outside Processing (25:24) Expensive machines + cheap vices = lost potential (27:26) Modular workholding, infinite adjustment, and the origins of the industry (29:18) When not to sell a customer — long-term trust over short-term gain (30:19) Why shops "don't know what they don't know" about proper workholding (31:58) Financing workholding and proving ROI to shop owners (33:09) Tooling certs and buying the solution, not just the machine (35:24) High-density workholding and maximizing machine real estate (37:12) Protecting customers from bad investments and the role of good vendors (38:01) The LEGO analogy and building reusable workholding systems (40:13) Trusting experts and using the right resources in decision-making (41:19) Grow your top and bottom line with CliftonLarsonAllen (CLA) (41:57) Buzzwords like Industry 4.0 vs. solving real problems (43:49) Competing with global labor costs and running unattended (44:19) Extending the life of old machines with better processes (46:41) Universal truth: If you're not making chips, you're not making money  Resources mentioned on this episode Connect with Larry Robbins and SMW Autoblok An investment in ProShop is an investment in your business Why we love Phoenix Heat Treating for Outside Processing Grow your top and bottom line with CliftonLarsonAllen (CLA) Smart Money Moves: Equipment Financing Tips with Ty Willis Connect With MakingChips www.MakingChips.com On Facebook On LinkedIn On Instagram On Twitter On YouTube

What drives execution velocity—better tools or better clarity? Loïc Houssier, CTO of Superhuman Mail (post-Grammarly acquisition), argues that most velocity problems stem from unclear team missions, not inadequate tooling. From steering DocuSign's French acquisition through complex carve-out negotiations to building Superhuman's offline-first architecture with a 100-millisecond interaction rule, Loïc shares hard-won lessons about engineering metrics that actually matter (PR per engineer per week trends over absolutes), when to resist microservices (until it's genuinely painful), and why promotion frameworks determine product quality. Technical leaders will learn how vertical team alignment eliminates dependencies, why guild structures maintain consistency without blocking speed, and how European safety nets create under-appreciated opportunities for technical risk-taking.

Jacob Effron of Redpoint joins Nick to discuss How Model Progress Shifts the Goalposts, Why The Death of Software Is Overstated, and How to Diligence Hypergrowth Without Getting Burned. In this episode we cover: Investing in AI and Vertical Applications Model Layer Advancements and Future Milestones Challenges and Opportunities in Agentic AI Investing in Tooling and Middleware Product Market Fit and Defensibility in AI Applications Verticals with Real Product Market Fit The Evolution of AI Investing Metrics Future Trends in AI and Robotics Guest Links: Jacob's LinkedIn Jacob's X Redpoint's LinkedIn Redpoint's Website The host of The Full Ratchet is Nick Moran of New Stack Ventures, a venture capital firm committed to investing in founders outside of the Bay Area. We're proud to partner with Ramp, the modern finance automation platform. Book a demo and get $150—no strings attached.   Want to keep up to date with The Full Ratchet? Follow us on social. You can learn more about New Stack Ventures by visiting our LinkedIn and Twitter.

Matthew Elder joins Tomi and I on the show this week. Matthew is a technician out of Texas, He is just beginning his path in the automotive diagnostic world. We'll share advice for being successful, Tooling options, & finding a good shop. Website- https://autodiagpodcast.com/Facebook Group- https://www.facebook.com/groups/223994012068320/YouTube- https://www.youtube.com/@automotivediagnosticpodcas8832Email- STmobilediag@gmail.comPlease make sure to check out our sponsors!SJ Auto Solutions- https://sjautosolutions.com/Automotive Seminars- https://automotiveseminars.com/L1 Automotive Training- https://www.l1training.com/Autorescue tools- https://autorescuetools.com/   

Elixir creator, José Valim, is throwing his hat into the coding agent ring with Tidewave –a coding agent for full-stack web development. Tidewave runs in the browser alongside your app, but it's also deeply integrated into Rails and Phoenix. On this episode, José tells us all about it. Also: his agent flow, YOLO mode, an MCP hot take, and more.