# presentation Published articles for presentation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response DevFeed: [How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response]() Original publisher: [Read original article]() Author: Vanessa Huerta Granda Published: 2026-09-17T09:30:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [incident](), [Incident response]() Tags: [devops](), [incident](), [incident-response](), [infoq](), [limits](), [organizational](), [outages](), [presentation](), [qcon-san-francisco-2026](), [qcon-software-development-conference](), [real-world](), [stream-incidents](), [structured](), [system](), [transcripts]() ### AI overview Vanessa Huerta Granda discusses how prolonged incidents reveal gaps between planned work and work as performed. Drawing on real-world scenarios, the presentation examines organizational fragility, human limits, system interdependencies, and the need for structured, humane, cross-functional incident response. ### Source excerpt Vanessa Huerta Granda explains how marathon incidents expose the gap between work as imagined and work as done. Drawing from real-world scenarios, she shares how complex outages reveal organizational fragility, human limits, and system interdependencies--and why incident response requires structured endurance, humane rotations, and holistic cross-functional coordination. By Vanessa Huerta Granda ## Modern Android Hacking DevFeed: [Modern Android Hacking]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2026-09-17T04:13:15.404035Z Content type: article Language: en Sources: [Dustin Summers]() Topics: [Hacking](), [Android]() Tags: [android](), [hacking](), [modern](), [presentation](), [summit](), [video]() ### AI overview A presentation titled "Modern Android Hacking" was given at the 2020 Android Summit, which was hosted virtually due to the pandemic. The page provides a video of the presentation. ### Source excerpt This presentation was given at the 2020 Android Summit which was hosted virtually due to the pandemic Video of Presentation: ## Presentation: Teaching Engineers, Trusting AI: How Education Enabled Autonomous Code Review DevFeed: [Presentation: Teaching Engineers, Trusting AI: How Education Enabled Autonomous Code Review]() Original publisher: [Read original article]() Author: Sarah Deitke Published: 2026-09-16T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [Artificial Intelligence](), [Code review](), [Pull Request](), [Tooling](), [engineering-culture](), [observability]() Tags: [adoption](), [agile](), [ai](), [ai-ml-data-engineering](), [architecture-design](), [artificial-intelligence](), [automated](), [automation](), [autonomous](), [case-study](), [code-review](), [code-reviews](), [culture](), [culture-methods](), [developer](), [developer-experience](), [development](), [duolingo-ai-literacy-code-review](), [infoq](), [metrics](), [ml-data-engineering](), [observability](), [pairing](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [transcripts]() ### AI overview Sarah Deitke presents Duolingo's approach to cultural AI adoption through internal AI literacy workshops, observability dashboards, and safe AI guardrails. The presentation includes a case study on redesigning code review with an automated PR risk-assessment bot and reports faster delivery without increased defect rates. ### Source excerpt Sarah Deitke discusses how Duolingo drives cultural AI adoption beyond tooling access. She explains their internal AI literacy workshops and observability dashboards, then shares a case study on redesigning code review using an automated PR risk-assessment bot. Deitke demonstrates how pairing targeted developer education with safe AI guardrails speeds up delivery without increasing defect rates. By Sarah Deitke ## Nail the Narrative DevFeed: [Nail the Narrative]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-09-15T15:11:00Z Content type: opinion Language: en Sources: [Martin Fowler]() Topics: [structure](), [Software]() Tags: [design](), [presentation](), [speaking](), [structure](), [writing]() ### AI overview The article argues that presenters should develop a clear narrative before opening slide software. It recommends defining the central idea and audience, shaping a storyline, and creating a lightweight storyboard before designing slides. ### Source excerpt Sumeet Gayathri Moghe finds many folks building presentations get tangled in building slides without a coherent narrative. He advises distilling the big idea, visualizing the audience, and building a structured storyline. more... ## Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership DevFeed: [Presentation: Lead Without a Ladder: How I Climbed Into Engineering Leadership]() Original publisher: [Read original article]() Author: Pauline Jepp Published: 2026-09-15T09:10:00Z Content type: opinion Language: en Sources: [InfoQ]() Topics: [engineering-leadership](), [systems]() Tags: [alignment](), [careers](), [chief-engineer](), [culture-methods](), [engineering](), [engineering-leadership](), [infoq](), [leadership](), [mentorship](), [presentation](), [qcon-san-francisco-2025](), [qcon-software-development-conference](), [safety](), [team](), [transcripts](), [trust]() ### AI overview Pauline Jepp discusses how systems thinking, rock climbing, and flocking behaviors inform engineering leadership. She covers balancing team autonomy with alignment, supporting mentorship and other invisible work, and transitioning from hands-on engineering to leadership while maintaining organizational trust and psychological safety. ### Source excerpt Pauline Jepp explains how systems thinking, rock climbing, and flocking behaviors apply to engineering leadership. She shares strategies for balancing team autonomy with alignment, supporting invisible work like mentorship, and navigating transitions from hands-on engineer to engineering leader while maintaining organizational trust and psychological safety. By Pauline Jepp ## Presentation: Decision Models in Agentic Architectures: From Production to Agent Skills DevFeed: [Presentation: Decision Models in Agentic Architectures: From Production to Agent Skills]() Original publisher: [Read original article]() Author: Alex Porcelli Published: 2026-09-14T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [Agent Skills](), [Artificial Intelligence](), [Large Language Model](), [NeMo]() Tags: [agent](), [agent-skills](), [agentic](), [agentic-ai-architecture](), [agents](), [ai](), [ai-architecture](), [ai-ml-data-engineering](), [architecture](), [architecture-design](), [architectures](), [artificial-intelligence](), [business](), [decision-models-agentic-ai](), [development](), [enterprise](), [enterprise-architecture](), [governance](), [infoq](), [large-language-models](), [llms](), [ml-data-engineering](), [models](), [nemo](), [presentation](), [production](), [qcon-ai-boston-2026](), [qcon-software-development-conference](), [skills](), [transcripts]() ### AI overview Alex Porcelli explains how DMN decision models can be integrated with LLMs, agent skills, and NeMo guardrails to create auditable and deterministic agentic architectures for high-stakes enterprise decisions. ### Source excerpt Alex Porcelli discusses the critical gap in enterprise AI: non-deterministic output and lack of accountability in high-stakes decisions. He shares how integrating DMN decision models with LLMs, agent skills, and NeMo guardrails creates auditable, deterministic agentic architectures - allowing business leaders to own decision logic while engineers maintain robust architectural governance. By Alex Porcelli ## Presentation: From Retrieval to Reasoning: Building Production-Ready Agentic AI Systems with Knowledge Graphs DevFeed: [Presentation: From Retrieval to Reasoning: Building Production-Ready Agentic AI Systems with Knowledge Graphs]() Original publisher: [Read original article]() Author: Cassie Shum Published: 2026-09-12T11:00:00Z Content type: tutorial Language: en Sources: [InfoQ]() Topics: [Graphs](), [Architecture & Design](), [Retrieval Augmented Generation (RAG)](), [Code]() Tags: [agentic-ai](), [agentic-ai-architecture](), [agents](), [ai](), [ai-architecture](), [ai-ml-data-engineering](), [architecture](), [architecture-design](), [artificial-intelligence](), [code](), [development](), [engineering](), [infoq](), [knowledge-graph](), [knowledge-graphs-agentic-systems-patterns](), [large-language-models](), [ml-data-engineering](), [presentation](), [production](), [qcon-ai-boston-2026](), [qcon-software-development-conference](), [rag](), [reasoning](), [retrieval-augmented-generation](), [transcripts]() ### AI overview A presentation on using knowledge graphs as a foundation for production-ready agentic AI systems. It covers architectural patterns for context bundling, decision provenance, code as truth, and agent visibility, along with a graph-based engineering harness for feedback loops, token optimization, and reliability. ### Source excerpt Cassie Shum discusses why knowledge graphs serve as a critical foundation for agentic systems. Moving beyond basic RAG, she explains 4 practical architectural patterns: context bundling, decision provenance, code as truth, and agent visibility. She demonstrates an engineering harness built on a knowledge graph to streamline feedback loops, optimize token usage, and maintain system reliability. By Cassie Shum ## Presentation: How To Run on Three Clouds at Once, and When Not To DevFeed: [Presentation: How To Run on Three Clouds at Once, and When Not To]() Original publisher: [Read original article]() Author: Ross McFarlane, Kevin Holditch Published: 2026-09-11T11:00:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [networking](), [Databases](), [Kubernetes]() Tags: [amazon](), [architecture](), [architecture-design](), [availability](), [aws](), [cloud](), [cloud-architecture](), [cloud-computing](), [cloud-networking](), [cockroach-labs](), [cockroachdb](), [containers](), [databases](), [devops](), [disaster-recovery](), [engineering](), [europe](), [financial-applications](), [fintech](), [form3-multicloud-architecture](), [infoq](), [kubernetes](), [microservices](), [networking](), [presentation](), [qcon-london-2026](), [qcon-software-development-conference](), [resilience](), [transcripts](), [us]() ### AI overview A presentation on Form3's move from one cloud to a triple-active multi-cloud architecture, covering cross-cloud networking, distributed databases, Kubernetes operators, and regional disaster-recovery expectations. ### Source excerpt Ross McFarlane and Kevin Holditch discuss Form3's evolution from a single-cloud setup to a triple active multi-cloud architecture. They share key engineering strategies for cross-cloud networking, distributed databases with CockroachDB and NATS, custom Kubernetes operators, and navigating distinct regional disaster recovery expectations across the UK, Europe, and US financial markets. By Ross McFarlane, Kevin Holditch ## Presentation: Accelerating Performance by Incrementally Integrating Rust Into Existing Codebase DevFeed: [Presentation: Accelerating Performance by Incrementally Integrating Rust Into Existing Codebase]() Original publisher: [Read original article]() Author: Lily Mara Published: 2026-09-10T09:34:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [rust refactoring](), [Refactoring](), [Integration testing]() Tags: [architecture](), [cost](), [culture-methods](), [design](), [development](), [engineering](), [infoq](), [infrastructure](), [performance](), [presentation](), [python](), [qcon-san-francisco-2025](), [qcon-software-development-conference](), [refactoring](), [rust](), [rust-refactoring](), [system-programming](), [testing](), [transcripts]() ### AI overview A presentation on incrementally refactoring Python bottlenecks into Rust with PyO3 to improve function-level performance, retain integration testing, and reduce infrastructure costs. ### Source excerpt Lily Mara explains how to avoid high-risk software rewrites through incremental FFI refactoring. She shares how engineering teams can replace Python bottlenecks with Rust via PyO3, demonstrating how to achieve dramatic function-level speedups, seamless integration testing, and meaningful infrastructure cost savings without microservice overhead. By Lily Mara ## Postgres AI Workshop DevFeed: [Postgres AI Workshop]() Original publisher: [Read original article]() Published: 2026-07-25T16:00:00Z Content type: article Language: en Sources: [Bruce Momjian: Postgres Blog]() Topics: [Artificial Intelligence](), [Claude Code](), [Command-line interface](), [Claude](), [Testing](), [benchmarking](), [Amazon Web Services](), [browser]() Tags: [ai](), [aws](), [benchmarking](), [browser](), [business](), [claude](), [claude-code](), [code](), [command-line](), [conference](), [data-modeling](), [presentation](), [release-notes](), [testing]() ### AI overview A firsthand account of an AWS-organized AI workshop for Postgres committers and core team members. It covers setting up Claude and Claude Code from the command line, using AI for testing, benchmarking, bug reports, email-thread analysis, patch review, and workflow automation. The author found Claude Code more useful than Claude in a web browser for identifying errors and inconsistencies in content. ### Source excerpt AWS was kind enough to organize an AI workshop this week in Pittsburgh for their employees, and the Postgres committers and core team. The first day covered the basics of setting up Claude and specifically how to use it from the command line to analyze files and automate workflows. We also discussed how AI-automated workflows can do testing, benchmarking, and create proof-of-concept patches to explore ideas that were previously too complex or time consuming to consider. On the second day, we did hands-on setup of Claude Code, and discussed how we can modify and add things to our source tree to improve AI usage. We also discussed how to improve our workflow in analyzing email threads and reviewing patches. On the final day, we picked various bug reports and used AI to improve email thread analysis and patch review. I found the event very relaxing, like a tech retreat, and hope we can do something like it again. During the event, I learned that Claude Code from the command line is much more powerful than using Claude via a web browser. It found many grammatic and typographic errors in my blogs and slides, we well as inconsistencies across my website. While I doubt anyone will notice the improvements, the process did improve the quality of my content. ## Live coding with dir stepper DevFeed: [Live coding with dir stepper]() Original publisher: [Read original article]() Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [intellij-platform](), [IntelliJ IDEA](), [Git](), [ide](), [Code](), [Documentation]() Tags: [code](), [coding](), [git](), [ide](), [intellij-idea](), [intellij-platform](), [kotlinconf](), [plugin](), [presentation](), [procedural](), [refactoring]() ### AI overview The article describes creating a workflow for live-coding presentations after finding that Git commits and interactive rebases were cumbersome for managing sequential coding steps. It explores using IntelliJ IDEA as an extensible platform for a tool that can move through steps, jump to completed states, refactor steps, and keep the process unobtrusive for the presenter and audience. ### Source excerpt Two months ago I gave my first ever live programming talk at KotlinConf. It was called "Talking to terminals (and how they talk back)", and you can watch it here. I've previously done slide-heavy talks which contained small demos or navigating through an existing codebase. Since this talk was starting from nothing, I decided to just write all the code from nothing. This meant spending the majority of the time in the IDE, but also figuring out how to remember what I was supposed to be writing at each step. Making the wrong choice The exceedingly obvious solution to having a series of steps in a live coding presentation is a git repo and a commit for each step. Unfortunately, this is a huge pain in the ass and really doesn't work at all (at least not for me). I started with commits, but by the 7th or 8th commit I was spending more than half my time doing interactive rebases over the entire history. Need a function in step 8 that should've been extracted between step 3 and 4? That's another 10 minutes rewriting history. Because it's a small set of files that are changing, every commit conflicts with any changes to history. It's also not clear how you actually move through the history. We want to start from nothing and move forward through history. Generally, git helps you jump backwards from the latest, not stepping forward from the oldest. It's not impossible, it's just clearly going against the grain. The problem, defined Now thoroughly enjoying this distraction from writing the actual talk, I distilled what I was trying to solve. Ability to manually write the changes required or to simply jump to the finished step. Some steps are important to watch unfold while others are procedural. This also can help with time management when I (inevitably) run low on time. Easily refactor steps as I go. Later steps often requiring refactoring previous ones to minimize the diff. As the talk evolves I want to add or merge steps. Nearly invisible to me and the viewer. I don't want t ## Retronetworking - 2026-07-08: Enabling Lawful Intercept in the Siemens EWSD DevFeed: [Retronetworking - 2026-07-08: Enabling Lawful Intercept in the Siemens EWSD]() Original publisher: [Read original article]() Author: laforge Published: 2026-06-26T16:08:20Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [digital]() Tags: [2026](), [announce](), [bug](), [digital](), [issue](), [presentation](), [tracker]() ### AI overview An announcement for the next RetroNetCall, a retronetworking-oriented spin-off of OsmoDevCall. The event will feature @jolly presenting research on enabling and operating the Lawful Intercept features of the historical Siemens EWSD digital telephony exchange. It is scheduled for July 8, 2026, at 20:00 CEST. ### Source excerpt After a bit of a hiatus, we're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall This time, we have a presentation by @jolly about his successful research efforts regarding enabling and operating the LI (Lawful Intercept) features of the historical Siemens EWSD digital telephony exchange. When: Wednesday, July 8th, 2026 from 20:00 CEST Time Topic Who 20:00 Meet and Greet everyone 20:10 enabling and operating the LI (Lawful Intercept) features of the historical Siemens EWSD digital telephony exchange @jolly Where: https://osmocom.org/RetroNetCall (Big Blue Button of https://franken.de/) ## Ten years of open source: a stained-glass view DevFeed: [Ten years of open source: a stained-glass view]() Original publisher: [Read original article]() Author: Tyler Hannan Published: 2026-06-19T13:32:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Open Source](), [GitHub](), [data](), [SQL](), [Tooling]() Tags: [clickhouse](), [data](), [git](), [github](), [keynote](), [open-source](), [presentation](), [sql]() ### AI overview This article reflects on ClickHouse's ten years as an open-source project through a stained-glass metaphor: many contributors and pieces form a durable whole. It connects community history, GitHub activity, public datasets, SQL, and production use cases such as cBioPortal, while emphasizing contributor credit and repair. ### Source excerpt ClickHouse has been open source for ten years. At Open House San Francisco, we explored this in greater detail in the day 2 keynote. We've all heard open source described as a cathedral and a bazaar, a big tent, etc. We tried a different analogy: staine ## LABScon25 Replay | Gamaredon x Turla: Unveiling a 2025 Espionage Alliance Targeting Ukraine DevFeed: [LABScon25 Replay | Gamaredon x Turla: Unveiling a 2025 Espionage Alliance Targeting Ukraine]() Original publisher: [Read original article]() Author: LABScon Published: 2026-06-02T13:00:58Z Content type: article Language: en Sources: [SentinelLabs - We are hunters, reversers, exploit developers, and tinkerers shedding light on the world of malware, exploits, APTs, and cybercrime across all platforms.]() Topics: [LABScon](), [Malware](), [Threat Research](), [Reverse Engineering](), [Threat Hunting & Intel](), [backdoor]() Tags: [analysis](), [apt](), [attacks](), [backdoor](), [conferences](), [labscon](), [labscon25](), [malware](), [presentation](), [research](), [reverse-engineering]() ### AI overview ESET researchers present technical evidence that Gamaredon facilitated Turla's access to high-value Ukrainian targets between February and June 2025. The presentation examines their operational collaboration, the deployment of Turla's Kazuar backdoor, and the implications for defenders tracking Russian cyberespionage. ### Source excerpt ESET researchers show how Gamaredon facilitated Turla access to Ukrainian targets, revealing rare cooperation between FSB-linked espionage groups. ## Deconstructing OkHttp DevFeed: [Deconstructing OkHttp]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-05-22T12:00:00Z Content type: article Language: en Sources: [Public Object]() Topics: [Library](), [Network](), [Code](), [Kotlin](), [implementation](), [Cache](), [certificates]() Tags: [architecture](), [cache](), [certificates](), [https](), [implementation](), [kotlinconf](), [ktor](), [library](), [network](), [okhttp](), [performance](), [presentation](), [retrofit](), [testing]() ### AI overview A KotlinConf talk examines OkHttp's implementation rather than its basic usage, covering interceptor-based architecture, connection lifecycles, cache state machines, URL decoders, HTTPS testing certificates, performance, and extension mechanisms. ### Source excerpt I presented this at KotlinConf on May 22, 2026. Also available on slides, YouTube, and Speaker Deck. OkHttp is a popular library for making network calls. You might use it directly, or with Ktor, Retrofit, Coil, or gRPC. But this is not a talk on how to use OkHttp. Instead, ## Generate editorial React presentations with one Claude Code prompt DevFeed: [Generate editorial React presentations with one Claude Code prompt]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2026-05-17T08:17:35Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Claude Code](), [React](), [Code](), [Large Language Model](), [Tailwind CSS](), [Vite]() Tags: [animation](), [architecture](), [claude-code](), [code](), [how-to](), [keyboard](), [llm](), [llms](), [presentation](), [prompt](), [prompting](), [react](), [tailwind](), [vite]() ### AI overview A tutorial presents a detailed Claude Code prompt for generating five-slide React presentations as a single Presentation.jsx file. The prompt fixes the design system and narrative structure while allowing the topic content to change, and the result can be used in a Vite, React, and Tailwind project. ### Source excerpt If you caught my YouTube Short on generating presentations as React apps with an LLM, this is the prompt I promised. Paste it into Claude Code, edit the CONTENT block at the top, and you get back a single-file Presentation.jsx -- five slides, keyboard nav, animated counters, an ## ClickHouse Release 26.4 DevFeed: [ClickHouse Release 26.4]() Original publisher: [Read original article]() Author: ClickHouse Published: 2026-05-08T00:00:00Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [SQL](), [Databases]() Tags: [bug](), [clickhouse](), [community](), [contributed](), [contributors](), [features](), [performance](), [presentation](), [release](), [sql]() ### AI overview ClickHouse 26.4 introduces 39 new features, 45 performance optimizations, and 238 bug fixes. The release expands SQL compatibility with features including VALUES as a table expression, EXTRACT units, SET TIME ZONE, NATURAL JOIN, and compound INTERVAL literals. It also includes faster COUNT DISTINCT and improvements to EXPLAIN. ### Source excerpt ClickHouse 26.4 is here! In this release, more features become SQL compatible, COUNT DISTINCT gets faster, EXPLAIN gets even prettier, and more ## How to prepare presentation for a Conference DevFeed: [How to prepare presentation for a Conference]() Original publisher: [Read original article]() Author: Tom Published: 2026-05-04T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [.NET Conf](), [Tool]() Tags: [career-growth](), [communication-skills](), [conference-preparation](), [conference-presentation](), [how-to](), [narrative-throughline](), [pitching](), [presentation](), [presentation-design](), [public-speaking](), [storytelling](), [structure](), [writing]() ### AI overview A practical guide to preparing conference presentations by starting with a clear pitch, developing a narrative throughline, structuring the story, prioritizing clarity, and using slides as visual support. ### Source excerpt Learn how to build impactful conference presentations by focusing on storytelling, narrative throughlines, and audience experience rather than just slides. ## SR-MPLS Workshop Materials DevFeed: [SR-MPLS Workshop Materials]() Original publisher: [Read original article]() Published: 2026-04-20T05:44:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [networking](), [Routing (disambiguation)]() Tags: [2025](), [mpls](), [presentation](), [routing](), [sr-mpls]() ### AI overview A short post shares materials from an SR-MPLS workshop held at ITNOG 10 in Bologna, including a Segment Routing presentation, hands-on workshop slides, lab topologies, and usage guidelines. ### Source excerpt We had a wonderful SR-MPLS workshop @ ITNOG 10 in Bologna on April 20th 2025. If you missed it, explore: The Segment Routing: from Theory to Practice presentation by Tiziano Tofoni The slide deck for the hands-on part of the workshop The lab topologies, and the usage guidelines. ## A few updates: the DGX Spark giveaway, new GPU inference slides, and my Vision AI Course DevFeed: [A few updates: the DGX Spark giveaway, new GPU inference slides, and my Vision AI Course]() Original publisher: [Read original article]() Author: Alex Razvant Published: 2026-04-11T13:03:07Z Content type: opinion Language: en Sources: [Neural Bits]() Topics: [GPU](), [Artificial Intelligence](), [DGX Spark](), [Inference](), [Nvidia](), [FIRST]() Tags: [ai](), [ai-training](), [dgx-spark](), [gpu](), [inference](), [models](), [nvidia](), [presentation]() ### AI overview The author shares updates about the completed DGX Spark giveaway organized with NVIDIA and a GPU and AI slide deck that is still in development. The presentation aims to explain how GPUs are used at scale for AI training and inference. ### Source excerpt What I've been working on behind the scenes, and what I'm preparing next. ## Retronetworking - 2026-04-01: RetroNetCall: 40C3 c3isdn network, new location DevFeed: [Retronetworking - 2026-04-01: RetroNetCall: 40C3 c3isdn network, new location]() Original publisher: [Read original article]() Author: xent Published: 2026-03-30T23:44:02Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [Network]() Tags: [2026](), [announce](), [bug](), [communication](), [https](), [issue](), [location](), [network](), [presentation](), [tracker]() ### AI overview An announcement for the April 1, 2026 RetroNetCall, a retronetworking-oriented spin-off of OsmoDevCall. The session includes a presentation on initial findings from a visit to the Hamburg Messe, the new site for that year's Chaos Communication Congress. ### Source excerpt We're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall This time, we have a presentation about the first findings after @jolly and @xent visit of the Hamburg Messe on 28th March 2026 (the new site for this year Chaos Communication Congress). When: Wednesday, April 1st, 2026 from 20:00 CEST Time Topic Who 20:00 Meet and Greet everyone 20:10 40C3 New Location (Hamburg Messe) @jolly and @xent Where: https://osmocom.org/RetroNetCall (Big Blue Button of https://franken.de/) ## Five ways of looking at Jco, Part 1 DevFeed: [Five ways of looking at Jco, Part 1]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-19T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [JavaScript](), [wasm](), [WebAssembly](), [Rust]() Tags: [blog](), [javascript](), [js](), [presentation](), [technical](), [wasm](), [webassembly]() ### AI overview This first article in a series explains Jco as a layered architecture for the JavaScript and WebAssembly ecosystem. It introduces the projects involved in building JavaScript WebAssembly components, including StarlingMonkey, componentize-js, Wizer, and Jco's CLI and transpilation capabilities. ### Source excerpt Jco (@bytecodealliance/jco on NPM)is a "multi-tool for the JS WebAssembly ecosystem." At the 2026 Bytecode Alliance Plumbers Summit, Technical Steering Committee member Bailey Hayes put it another way: Jco is "like five projects in one." It's certainly a project with many facets--five big ones, arguably! Recognizing what those facets are, and how they fit together, is the key to understanding why Jco matters beyond the JavaScript ecosystem. In this blog series, we'll draw on Victor Adossi's Plumbers Summit presentation to take an in-depth look at Jco from five different perspectives, in order to better grasp how you can use (and contribute to!) Jco today. There's a lot to unpack here, so in this first post, we'll try to get to grips with Jco as a layered architecture that brings together many pieces of the Wasm and JS ecosystem. ## Presentation: netlab Overview and Use Cases (NetBCN) DevFeed: [Presentation: netlab Overview and Use Cases (NetBCN)]() Original publisher: [Read original article]() Published: 2026-03-05T08:24:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Automation](), [Testing]() Tags: [automation](), [event](), [netlab](), [network-automation](), [presentation](), [prototyping](), [use-cases]() ### AI overview The article announces a presentation on netlab use cases delivered at the NetBCN event. The presentation covers examples involving rapid prototyping, testing network automation software, and working with vendor technical assistance. ### Source excerpt Yesterday, I had a short presentation on netlab use cases during the NetBCN event. It covered a dozen examples, from rapid prototyping to testing network automation software and arguing with vendor TAC. I added the "use cases" part of the presentation to the standard netlab presentation; you can view the results on ipSpace.net (no account or registration required). Explore ## Scalable API Response Handling Across Multi-Layered Architectures with Sandwich DevFeed: [Scalable API Response Handling Across Multi-Layered Architectures with Sandwich]() Original publisher: [Read original article]() Author: Jaewoong Eum Published: 2026-02-08T06:25:14Z Content type: tutorial Language: en Sources: [Stories by Jaewoong Eum on Medium]() Topics: [Android](), [Kotlin](), [API](), [kotlin-coroutines](), [Error Handling](), [Network]() Tags: [android](), [api](), [code](), [communication](), [coroutines](), [error-handling](), [exceptions](), [flow](), [kotlin](), [kotlin-multiplatform](), [mvi](), [mvvm](), [network](), [networking](), [presentation](), [responses](), [retrofit](), [viewmodel]() ### AI overview This tutorial explains how to handle Retrofit API responses, errors, and exceptions across multi-layered Android architectures such as MVVM and MVI. It presents Sandwich as a type-safe, composable approach and covers response handling, composition, merging, global error mapping, and Flow integration. ### Source excerpt Unsplash@picoftasty Modern Android applications commonly adopt multi-layered architectures such as MVVM or MVI, where data flows through distinct layers: a data source, a repository, and a ViewModel (or presentation layer). Each layer has a specific responsibility, and network responses must propagate through all of them before reaching the UI. While this separation produces clean, testable code, it introduces a real challenge: how do you handle API responses, including errors and exceptions, as they cross each layer boundary? Most developers solve this by wrapping API calls in try-catch blocks and returning fallback values. This works for small projects, but as the number of API calls grows, the approach creates ambiguous results, scattered boilerplate, and lost context that downstream layers need. You end up with ViewModels that cannot tell whether an empty list means "no data" or "network failure," repositories that swallow important error details, and data sources that repeat the same error handling pattern dozens of times. In this article, you'll explore the problems that emerge when handling Retrofit API calls across layered architectures, why conventional approaches break down at scale, and how Sandwich provides a type safe, composable solution that simplifies response handling from the network layer all the way to the UI. You'll also walk through the full set of Sandwich APIs, from basic response handling to advanced patterns like sequential composition, response merging, global error mapping, and Flow integration, each with real world use cases that show when and why you would reach for them. Retrofit API calls with coroutines Most Android projects use Retrofit with Kotlin coroutines for network communication. A typical service interface looks like this: https://medium.com/media/ebcba33386d664d1cf69a89234d2e22a/href The service returns a List directly. Retrofit deserializes the JSON response body and gives you the data. This works perfectly when the [Next page]()