# pairing Published articles for pairing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## Pair Programming With Your AI Agent DevFeed: [Pair Programming With Your AI Agent]() Original publisher: [Read original article]() Author: blundell Published: 2026-09-06T21:50:09Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [AI Agent](), [Local AI](), [Programming](), [Command-line interface]() Tags: [agent](), [ai](), [ai-agent](), [androiddev](), [antigravity](), [cli](), [gemini](), [geminicli](), [intermediate](), [intermediate-reference-ai-androiddev-gemini-geminicli-pairing](), [pair](), [pairing](), [programming](), [reference](), [terminal]() ### AI overview This tutorial presents sessions with a local AI agent as pair programming and maps four classic pairing styles--unstructured, Driver/Navigator, Strong-Style Pairing, and Ping Pong--to AI-assisted development. It uses Antigravity CLI for examples while noting that the approach is not specific to that tool. ### Source excerpt This post explains how to treat a session with a local AI agent as a pair programming session, and how the four classic pairing styles map onto working with one. I'll use Antigravity CLI for the concrete examples, though nothing here is specific to it. Swap in whichever agent sits in your terminal. The idea [...] The post Pair Programming With Your AI Agent first appeared on Blundell. ## Connect an ESP device and iPhone directly using Wi-Fi Aware DevFeed: [Connect an ESP device and iPhone directly using Wi-Fi Aware]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-25T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Wi-Fi](), [iOS](), [iphone](), [cross-platform](), [P2P](), [Internet of things](), [networking]() Tags: [android](), [app](), [blog](), [cross-platform](), [esp-idf](), [esp-idf-component](), [how-to](), [ios](), [iot](), [iphone](), [ipv6](), [p2p](), [pairing](), [practitioner](), [security](), [wi-fi](), [wi-fi-aware]() ### AI overview This tutorial explains how to connect an ESP device directly to an iPhone using Wi-Fi Aware. It describes service discovery, mandatory six-digit PIN pairing, and an encrypted IPv6 data link without an access point, DHCP server, or internet connection. On supported devices running iOS 26 or iPadOS 26, the connection can operate concurrently with normal Wi-Fi connectivity. ### Source excerpt iOS 26 brings Wi-Fi Aware™ support on iPhone 12 and later, enabling compatible devices to securely discover, pair, and communicate directly. This requires no Access Point and does not affect iPhone's network connectivity over Wi-Fi. This article walks through the steps to set up an ESP device and an iPhone so they can pair and connect using Wi-Fi Aware. ## How to Set Up OpenClaw for Secure, Persistent, and Deterministic Workflows DevFeed: [How to Set Up OpenClaw for Secure, Persistent, and Deterministic Workflows]() Original publisher: [Read original article]() Author: Daniel Moka Published: 2026-03-02T06:20:17Z Content type: tutorial Language: en Sources: [Craft Better Software]() Topics: [OpenClaw](), [AI Agent](), [Security](), [Docker](), [Large Language Model](), [Mac Mini]() Tags: [ai-agent](), [configuration](), [docker](), [installation](), [llms](), [mac-mini](), [openclaw](), [pairing](), [security]() ### AI overview A practical guide to setting up OpenClaw for real work. It recommends using a Mac mini or VPS, running OpenClaw in Docker, configuring the agent's identity, and applying security boundaries such as keeping the gateway private and requiring pairing. ### Source excerpt Setting Up Your AI Assistant of OpenClaw Correctly for Real Work ## Stream of Consciousness Driven Development DevFeed: [Stream of Consciousness Driven Development]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-02-18T16:33:08Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Development](), [Specifications](), [Markdown]() Tags: [concepts](), [development](), [experience](), [markdown](), [pairing](), [specifications]() ### AI overview The author describes a pairing technique for conceptually complex specification work: write the problem, discussion, rejected approaches, proposed solution, and rationale in a Markdown file before changing the specification. This helps partners understand the reasoning and agree on an approach, though the author reports having tried it only once. ### Source excerpt This is something I just tried out last week but it seems to have enough potential to be worth showing unpolished. I was pairing with a client on writing a spec. I saw a problem with the spec, a convoluted way of fixing the spec. Instead of trying to verbally explain it, I started by creating a new markdown file: NameOfProblem.md Then I started typing. First the problem summary, then a detailed description, then the solution and why it worked. When my partner asked questions, I incorporated his question and our discussion of it into the flow. If we hit a dead end with the solution, we marked it out as a dead end. Eventually the file looked something like this: Current state of spec Problems caused by this Elaboration of problems What we tried that didn't work Proposed Solution Theory behind proposed solution How the solution works Expected changes Other problems this helps solve Problems this does *not* help with Only once this was done, my partner fully understood the chain of thought, and we agreed it represented the right approach, did we start making changes to the spec. How is this better than just making the change? The change was conceptually complex. A rough analogy: imagine pairing with a beginner who wrote an insertion sort, and you want to replace it with quicksort. You need to explain why the insertion sort is too slow, why the quicksort isn't slow, and how quicksort actually correctly sorts a list. This could involve tangents into computational complexity, big-o notation, recursion, etc. These are all concepts you have internalized, so the change is simple to you, but the solution uses concepts the beginner does not know. So it's conceptually complex to them. I wasn't pairing with a beginning programmer or even a beginning specifier. This was a client who could confidently write complex specs on their own. But they don't work on specifications full time like I do. Any time there's a relative gap in experience in a pair, there's solutions that are concep ## Mob Programming: Smells Like Team Spirit DevFeed: [Mob Programming: Smells Like Team Spirit]() Original publisher: [Read original article]() Author: Dmytro Kurets Published: 2025-12-04T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Programming](), [Code](), [pull-requests](), [Back end](), [Front end](), [Data analysis](), [Refactoring]() Tags: [back-end](), [code](), [collaboration](), [data-analysis](), [engineering](), [engineering-culture](), [front-end](), [keyboard](), [pairing](), [programming](), [review](), [team]() ### AI overview The article explains mob programming as structured, shared-focus collaboration with one driver, rotating typing roles, and navigators guiding the work. It describes a trivago team experimenting with collaborative review and coding changes to address pull requests piling up and slowing delivery. ### Source excerpt Mob programming often sparks hot takes. "It's counter-productive." "One person could do it faster." "Why waste five people on one keyboard?" If that's what it looks like in your head--one senior ... ## Rope Optimizations, Part 1 DevFeed: [Rope Optimizations, Part 1]() Original publisher: [Read original article]() Author: Thorsten Ball, Antonio Scandurra Published: 2024-11-18T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Data structures](), [Optimization](), [Benchmark]() Tags: [benchmark](), [code](), [data-structure](), [optimization](), [pairing](), [performance]() ### AI overview This Zed Decoded article explains performance optimizations to Zed's Rope data structure, including faster point translation and a further optimization for indexing tabs. It also introduces a companion video of the pairing session. ### Source excerpt In this episode of Zed Decoded, Thorsten and Antonio walk through the performance optimizations Antonio when working on Zed's Rope data structure before they then pair on adding more optimizations ## This Week at Zed Industries: #15 DevFeed: [This Week at Zed Industries: #15]() Original publisher: [Read original article]() Author: Piotr Osiewicz Published: 2023-08-11T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Code](), [wasm](), [GitHub](), [Script](), [Text-based user interface]() Tags: [code](), [commands](), [experimental](), [github](), [implementation](), [pairing](), [performance](), [ranking](), [report](), [script](), [search](), [wasm]() ### AI overview This weekly Zed Industries update covers search performance work, new text manipulation and case-conversion commands, ongoing WASM extensibility experiments for custom language servers, and improvements to a GitHub issue-ranking script. ### Source excerpt Channels permissions woes, performance, and text manipulation commands ## Behind The Code: Jennice Colaco, Backend Developer DevFeed: [Behind The Code: Jennice Colaco, Backend Developer]() Original publisher: [Read original article]() Author: Toni Akinwumi Published: 2018-07-26T19:12:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Development](), [Back end](), [Shopify](), [Ruby](), [debugging](), [Programming]() Tags: [backend](), [debugging](), [developer](), [development](), [learning](), [pairing](), [ruby](), [shopify](), [team]() ### AI overview An interview with Shopify backend developer Jennice Colaco covering her education, work on marketing tools, approach to programming languages, Ruby development and debugging with byebug, continuous learning, and collaborative problem-solving. ### Source excerpt Behind the Code is an initiative with the purpose of sharing the various career stories of our engineers at Shopify, to show that the path to development is non-linear and quite interesting. The features will showcase people just starting their careers, those who made career switches, and those who've been in the industry for many years. Enjoy! ## When to pair program DevFeed: [When to pair program]() Original publisher: [Read original article]() Author: Jack Tarantino Published: 2017-03-14T20:59:32Z Content type: opinion Language: en Sources: [Jacopo Tarantino]() Topics: [pair\_programming](), [Development](), [Code quality]() Tags: [best-practices](), [bugs](), [development](), [pair-programming](), [pairing](), [process](), [programming](), [quality]() ### AI overview An opinion article examines when pair programming is useful. It describes pairing as an Extreme Programming practice and argues that working with a peer can improve software quality, reduce bugs, and limit technical debt. ### Source excerpt This post is another one brought to you by the good people at InRhythm. If you're an engineer that likes writing and building strong, happy culture focused on learning and growth you should apply! I like working with smart, passionate people :). Lots of companies embrace pair programming as a way ## An Update on Integrating Zcash on Ethereum (ZoE) DevFeed: [An Update on Integrating Zcash on Ethereum (ZoE)]() Original publisher: [Read original article]() Author: Christian Reitwiessner Published: 2017-01-19T17:57:54Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Blockchain](), [zero-knowledge](), [Solidity]() Tags: [blockchain](), [blog](), [cryptographic](), [development](), [ethereum](), [implementation](), [pairing](), [post](), [research-development](), [rust](), [smart-contract](), [technical](), [update](), [verification](), [zero-knowledge]() ### AI overview Ethereum and the Zcash Company report a research collaboration to combine Ethereum's programmability with Zcash's privacy technology. The update describes a Solidity zk-SNARK verifier using Ethereum precompiled contracts and successful verification of a privacy-preserving Zcash transaction on an Ethereum testnet. ### Source excerpt Members of the Ethereum R&D team and the Zcash Company are collaborating on a research project addressing the combination of programmability and privacy in blockchains. This joint post is being concurrently posted on the Zcash blog, and is coauthored by Ariel Gabizon (Zcash) and Christian Reitwiessner (Ethereum). Ethereum's flexible smart... ## Pair Programming Interviews, Part II DevFeed: [Pair Programming Interviews, Part II]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-12-04T17:05:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Programming](), [Development](), [Code]() Tags: [command-line](), [engineering](), [how-to](), [interviews](), [pairing](), [programming](), [software-engineer]() ### AI overview This article explains how Square's pair programming interviews work for full-time and intern software engineering candidates. It describes the interview format, incremental coding challenges, available programming languages and development environments, and the skills interviewers assess. ### Source excerpt How to be prepared for a software engineer interview at Square ## Pair Programming Interviews DevFeed: [Pair Programming Interviews]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-09-11T07:00:00Z Content type: opinion Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [engineering-culture](), [Development](), [coding](), [Testing]() Tags: [apis](), [code](), [coding](), [debugging](), [development](), [engineering](), [engineering-culture](), [experience](), [intern](), [internship](), [interviews](), [pair](), [pairing](), [programming](), [review](), [team](), [testing](), [tests](), [work]() ### AI overview An intern describes Square's pair programming interview process, emphasizing development-environment setup, collaborative coding, and working code that candidates can test and debug. ### Source excerpt An Intern's Interview Experience ## Why We Pair Interview DevFeed: [Why We Pair Interview]() Original publisher: [Read original article]() Author: Square Engineering Published: 2011-10-05T16:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [engineering-culture](), [Programming](), [Code]() Tags: [code](), [engineering](), [engineering-culture](), [interview](), [pairing](), [software-engineer]() ### AI overview Square explains its pairing-based software engineering interviews, which use a shared computer and real development tools to assess practical skills such as code structure, testability, maintainability, and performance. ### Source excerpt An overview of our pairing interviews and why they're awesome.