# AI and Emerging Tech Published articles for AI and Emerging Tech. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## From AI Code to Trusted Software: Harness Engineering in Practice DevFeed: [From AI Code to Trusted Software: Harness Engineering in Practice]() Original publisher: [Read original article]() Author: Travis Frisinger Published: 2026-09-04T21:55:00Z Content type: opinion Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [AI-assisted coding](), [Software](), [trust](), [observability](), [Authorization]() Tags: [agent](), [ai](), [ai-and-emerging-tech](), [code](), [engineering](), [engineering-and-devops](), [observability](), [permissions](), [trust](), [verification]() ### AI overview The article presents harness engineering as a repository-centered discipline for making AI-generated software more trustworthy. It argues that prompts and written standards are insufficient, and that permissions, quality gates, evidence, and observability should enforce organizational standards and support verification. ### Source excerpt If the same reasoning path writes the system change and defines the proof of success, you may be setting yourself up for an avoidable failure in the future. Harness engineering is meant to act as an extension of your own organizational guardrails, which were always meant to reduce risk and improve quality. Travis Frisinger, Head of Agentic AI Your team is shipping more AI-written code every quarter. How do you know it is any good? Good means it meets your standards, and you have probably already tried handing your agents the standards: a context file, a style guide, the wiki pasted into the prompt. The agent reads them, agrees, and still breaks them, because instructions to a model are suggestions. What the repository permits is what actually happens. Your people absorb standards through review comments and hallway corrections, and the lessons stick. An agent apologizes and forgets by the next session. The only place its lessons can accumulate is the repository itself. That gap used to be an annoyance. With AI doing real engineering work, the quality gap is the whole game. Harness engineering is the discipline that closes it. It is the process of imbuing a repository with your standards so that the repository itself enforces them: permissions and boundaries that say what any actor may touch, quality gates that fail closed, evidence attached to every change, and observability that spans runs rather than moments. Models supply software delivery capacity. The harness supplies observable accountability: every change carries what was done, which rule allowed it, and what happened as a result, no matter which model, agent, or person did the work. Why now The industry started using the term harness engineering back in February, 2026. Since then, Thoughtworks, LangChain, and others have built serious thought leadership around the same shape. When several firms independently converge on the same word, it usually means they are trying to name the same problem. The real proble ## Teaching the Agent Our Craft: Structured Agentic Development on a Real Codebase DevFeed: [Teaching the Agent Our Craft: Structured Agentic Development on a Real Codebase]() Original publisher: [Read original article]() Author: Alex Haldeman Published: 2026-07-06T16:00:00Z Content type: article Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Agentic development](), [Claude Code](), [Development](), [AI-assisted coding](), [Test-driven development]() Tags: [agentic](), [agentic-development](), [ai-and-emerging-tech](), [claude-code](), [clean-architecture](), [structured](), [test]() ### AI overview 8th Light describes a structured agentic development workflow built around Claude Code. The approach adapts Research-Plan-Implement by separating research, planning, and implementation, adding review cycles and involving product managers and designers at each transition. It also applies test-driven development, clean architecture, and explicit project conventions to address common agent failure modes. ### Source excerpt The Mission We recently partnered with a startup that had developed a clinically proven approach to alleviating neuroplastic chronic pain. Their program worked: a coach-led model that helped patients ease chronic pain at a lower cost than conventional treatment. The problem was reach. The in-person model could not scale to the demand they were seeing, and there were not enough coaches to close the gap. We were brought in to build a digital platform that could deliver the program to every patient who needed it. Our Development Philosophy and Inspiration At 8th Light, we approach agentic development the same way we approach any software engagement: with discipline around test-driven development, clean architecture, and code that is built to embrace change. But agentic development comes with its own failure modes. An agent produces code that covers the happy path and misses critical behaviors. A context window fills with stale reasoning from earlier attempts, and the agent starts working against itself. Without explicit conventions, the output works but looks like nobody on the team wrote it. Tyler Burleigh's Research-Plan-Implement gave us a useful frame for thinking about this. His core observation: the bottleneck is not code generation, it is ensuring the model understands what to build before it starts building. RPI addresses that by separating research, planning, and implementation into distinct phases, each with a review cycle before the next begins. We adapted that structure into our Claude Code workflow, with the additional goal of keeping product managers and designers genuinely in the loop at each transition, not just developers. What follows is a description of the harness we built from a Claude Code-specific perspective. The HarnessStructure Before walking through the pieces, it helps to see how they fit together. Everything that teaches the agent our craft lives in a handful of files at the project root and inside a single .claude/ directory. None of it is ## Production is the New Prototype: Notes from LangChain Interrupt 2026 DevFeed: [Production is the New Prototype: Notes from LangChain Interrupt 2026]() Original publisher: [Read original article]() Author: Shawn DeVries Published: 2026-05-17T14:45:00Z Content type: opinion Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Artificial Intelligence](), [observability](), [Tooling](), [Demo]() Tags: [2026](), [agentic](), [ai](), [ai-and-emerging-tech](), [conference](), [enterprise](), [observability](), [production](), [technical]() ### AI overview An opinion article from 8th Light about discussions at LangChain Interrupt 2026, arguing that agent systems are moving from demonstrations toward production operations. It emphasizes reliability, governance, enterprise constraints, and observability as essential to operating these systems. ### Source excerpt 8th Light's Head of Agentic AI, Travis Frisinger, and I spent two days in San Francisco at LangChain Interrupt 2026 watching what happens when agent demos meet production traffic. The room was full of companies that have crossed that line, and a few that wish they hadn't tried. The conversation a year ago was "can agents work?" The conversation in May was "how do we operate reliable, observable, governable agent systems at scale?" In the discussions we had at the conference, we validated that the shift was real and not just product marketing. What follows is what stood out across the two days, with Travis's read on the technical patterns and what I'm hearing from clients who are trying to ship. Demos are Easy. Operating is the Job. Travis's summary of the two days: agents are moving from demos to real operational systems, with companies like Lyft, Cisco, Toyota, and LATAM already running large-scale production deployments. The keynote framed agents as different from traditional software because of an infinite input space and non-deterministic models. The successful teams ship early and iterate. The unsuccessful ones, according to MongoDB's CJ Desai in conversation with Harrison Chase, built proof-of-concepts for two years and called it strategy. He called it agent washing. 2025 was supposed to be the year of agents at scale. It didn't materialize. He thinks 2026 will, but only for teams who treat the operational work as the actual work. That matches what I hear in client conversations. The question is rarely "can we build an agent?" It is "how do we run one inside an enterprise that has compliance, vendor reviews, change management, and a board that wants to see ROI?" Observability is Not Optional. It's the Foundation. Nearly every speaker named LangSmith or an equivalent as mandatory infrastructure rather than nice-to-have tooling. LATAM Airlines made the point with the most authority. Nico Venegas and Claudio Urbina described a concierge agent on their B2C site se ## Accelerating Delivery: How AI Agents Can Own the Initial Code Draft DevFeed: [Accelerating Delivery: How AI Agents Can Own the Initial Code Draft]() Original publisher: [Read original article]() Author: Stephen Walker Published: 2026-05-05T21:58:00Z Content type: article Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Artificial Intelligence](), [Loop Engineering](), [Pull Request](), [human review](), [jira](), [coding](), [hooks](), [Script]() Tags: [agents](), [ai](), [ai-agents](), [ai-and-emerging-tech](), [code](), [hooks](), [human-review](), [jira](), [pull-request](), [review](), [sandbox]() ### AI overview The article describes a pragmatic workflow in which coordinated AI agents turn a Jira ticket into a code draft and pull request for human review. It emphasizes safety through branch permissions, scoped access, scripts and hooks, plus deterministic structures around probabilistic language models. The supplied text is truncated before the full reliability hierarchy and later conclusions. ### Source excerpt Why This Matters in the Era of Agentic Everything The gap between a Jira ticket and the first pull request (PR) is often a graveyard of productivity. Context switching, boilerplate setup, and requirement analysis can eat up hours of a senior engineer's day before they write a single line of business logic. Recently, industry leaders have showcased "Harness Engineering" [1][2] -- the practice of building autonomous agent workflows that handle end-to-end coding tasks. While their results are inspiring, the barrier to entry can feel insurmountable. The challenge for most teams is finding a starting point that balances long-term vision with immediate ROI. We recently helped a large-scale, high-traffic consumer services platform bridge this gap. Instead of an all-or-nothing architectural overhaul, we took a pragmatic first step: automating the journey from Jira ticket to PR. The Vision: "Let's work on FEAT-123" Our goal was simple. We wanted to enable a developer to provide a single prompt -- "Let's work on FEAT-123" -- and have a coordinated team of AI agents handle the planning, coding, and verification. This culminates in a PR ready for human review. To make this a reality, we focused on three strategic pillars: safety, determinism, and quality. Safety Through Pragmatic Guardrails One of the primary concerns for any engineering leader is "agent drift" -- an AI making unauthorized or hallucinated changes. While an isolated digital sandbox is an ideal long-term goal, we proved that teams can achieve significant safety and progress using existing infrastructure: Branch Permissions: Restrict agent access to specific feature branches. Scoped Access: Use scripts and hooks to define exactly what an agent can and cannot touch. Human-in-the-Loop: Ensure that while the agent proposes the change, a human must always review, approve, and merge the code. By defining the agent's scope as a specialized contributor rather than a system administrator, we mitigated risk while maximizing ou ## Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation DevFeed: [Automated Accessibility Tools Support Audits but Cannot Replace Human Evaluation]() Original publisher: [Read original article]() Author: Celeste Aronow Published: 2026-04-15T13:44:00Z Content type: opinion Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Accessibility](), [Tooling](), [Large Language Model](), [axe-core]() Tags: [accessibility](), [ai-and-emerging-tech](), [axe-core](), [llms](), [tooling]() ### AI overview The article argues that automated accessibility scanners and LLM-assisted auditing can identify many concrete issues and expand teams' coverage, but they cannot fully assess what people with disabilities experience when using a screen reader. It also warns that scan output can include false violations and requires human judgment and accessibility expertise. ### Source excerpt The Gap is Real If your accessibility process ends with a passing scan, your users with disabilities are likely encountering barriers you do not know about. Automated tools are useful. LLM-assisted auditing has raised the ceiling. Neither closes the gap between what a tool can verify and what a person actually experiences when navigating with a screen reader. The gap is real, it is measurable, and it has organizational consequences. I have spent years running every category of automated accessibility tool the industry has produced: rule-based scanners like axe-core and WAVE, visual analyzers like Lighthouse, browser extensions with built-in screen reader simulations. When LLMs entered the picture, the promise was compelling. Tools that could finally understand context, interpret user flows, and reason about accessibility the way a human specialist does. I wanted that to be true. It isn't. What Automation Does Well Let me be fair to the tools. Automated accessibility scanners like axe-core, Lighthouse, and WAVE are genuinely good at what they do. They catch heading hierarchy violations quickly and reliably. They flag color contrast failures with precision. They identify missing alt attributes on images in many cases. These are real wins. If you have run these tools on your product, you have addressed real issues, and the engineers who did that work should feel good about it. Automated tooling is a force multiplier. It speeds up the work and amplifies how much ground a team can cover. The problem is not what these tools do. It is what they cannot do, and what organizations assume they have done. What Automation Invents The same tools I praised above (SilkTide, axe-core, Lighthouse, and WAVE) are genuinely valuable parts of a real accessibility workflow. They speed up discovery, give teams a shared vocabulary, and help non-specialists see problems that would otherwise be invisible. They also generate a lot of output. A single scan on a moderately complex page can retur ## A Primer: MCP Servers and the Model Context Protocol DevFeed: [A Primer: MCP Servers and the Model Context Protocol]() Original publisher: [Read original article]() Author: Priya Patil Published: 2026-02-25T06:00:00Z Content type: tutorial Language: en Sources: [8th Light](), [8th Light Insights]() Topics: [Model Context Protocol](), [Server](), [Security](), [client](), [Authentication]() Tags: [ai](), [ai-and-emerging-tech](), [ai-assistant](), [audit](), [authentication](), [mcp](), [model-context-protocol](), [protocol](), [sandboxing](), [security](), [servers]() ### AI overview This primer explains MCP (Model Context Protocol), an open protocol that gives AI models a standard interface for connecting to external tools and data sources. It also outlines current gaps in authentication, discovery, security, sandboxing, secret management, and audit trails. ### Source excerpt Navigating Change The way we interact with software is shifting. Instead of clicking through web interfaces and learning different UIs for each system, some people are moving toward natural language as the interface - telling an AI what they want done, and it handles the task completion for them. This shift is happening now, but there's been a missing piece: how does the AI actually connect to and control those systems? MCP Defined MCP (Model Context Protocol) is an open protocol that gives AI models a standardised interface to external tools and data sources. Think of it as a USB-C for AI - before USB-C, every device needed its own connector. MCP does the same for AI-system integration. Instead of building custom integrations for every combination of AI model and external service, you implement MCP once and your AI can talk to everything it needs to. Instead of context-switching between Slack, JIRA, GitHub, and dashboards for example, we'll be able to describe what we need and have an AI assistant handle the interactions. Or as Anthropic defines it: "MCP (Model Context Protocol) is an open-source standard for connecting AI applications to external systems." Current State: A Nascent Protocol Yes, MCP has gaps. Here are a few: It's relatively new (launched November 2024) and the ecosystem is still figuring things out. Authentication and authorisation have a standard but implementation is patchy. Discovery is a work in progress, with a real need for global registry mechanics. Security is largely left to implementers - no built-in sandboxing, no secret management standard, no consistent audit trails. The community is actively working on all of these, and thing are moving very fast. But these are solvable problems and a lot of the changes are happening on the client side so building out servers feels a little more stable. These gaps shouldn't prevent you from getting value today - they just mean you'll need to handle some plumbing yourself and take an abundance of cauti ## Why Walk-Out Checkout Technology Works Better in Stadiums and Small Stores DevFeed: [Why Walk-Out Checkout Technology Works Better in Stadiums and Small Stores]() Original publisher: [Read original article]() Author: Shawn DeVries Published: 2026-02-16T19:30:00Z Content type: article Language: en Sources: [8th Light Insights]() Topics: [Computer vision](), [Artificial Intelligence](), [Cloud]() Tags: [ai-and-emerging-tech](), [computer-vision](), [edge](), [edge-ai](), [on-device](), [real-time](), [technology](), [video]() ### AI overview The article argues that walk-out checkout technology struggled in grocery stores because of complex inventories, unpredictable customer behavior, and extensive human review. It says the approach is performing better in stadiums and small-format stores, where controlled conditions, limited products, edge AI, and 3D computer vision support rapid transactions. ### Source excerpt This technology platform, called 'Just Walk Out', required over 1,000 workers in India manually reviewing video footage to verify transactions. By 2022, 700 out of every 1,000 sales needed human review. Amazon pulled the technology from their Fresh grocery stores in 2024. They paved the way. But it wasn't sustainable. The problem wasn't the concept. It was the complexity. Grocery stores carry thousands of SKUs, items without barcodes, and unpredictable customer behavior at scale. In fact, this same technology is succeeding in stadiums and small-format stores. Mashgin kiosks are deployed across 150+ sports venues and a number of airports. Guests drop items on a tray, the system scans and prices them using computer vision, and checkout finishes in under 15 seconds. No barcode scanning. No cashier. No human review loop. Over 1.4 million items sold at NFL stadiums in 2024 alone. Median transaction time sits below 15 seconds, even during halftime surges when traditional concessions collapse under volume. Walk out technology works when the context is controlled. Why Stadiums Succeed Where Grocery Failed Stadiums solve the problems that broke Amazon's model: Limited SKUs. Concessions carry hundreds of items, not tens of thousands. High margins. Premium pricing justifies the tech investment. Controlled environment. Fixed locations, predictable lighting, standardized packaging. Edge AI processing. No cloud dependency. No human review. Decisions happen on-device in real time. Mashgin removes the constraint. Throughput scales without adding headcount. The kiosk processes items as fast as fans can place them on the tray. Speed only holds if the system stays up. Any downtime, and the kiosk becomes a bottleneck worse than the line it replaced. How Mashgin Handles Volume Mashgin uses 3D computer vision and edge AI to identify items in real time: Multiple cameras capture items from different angles as they land on the tray On-device neural networks classify products without cloud d ## AI-assisted Coding is Not Doing My Dishes and Laundry DevFeed: [AI-assisted Coding is Not Doing My Dishes and Laundry]() Original publisher: [Read original article]() Author: Justyna Jurkowska Published: 2025-09-10T18:45:00Z Content type: opinion Language: en Sources: [8th Light Insights]() Topics: [AI-assisted coding](), [coding](), [Large Language Model](), [Tooling](), [ChatGPT](), [cursor]() Tags: [ai](), [ai-and-emerging-tech](), [ai-assisted-coding](), [chatgpt](), [coding](), [cursor](), [development](), [llm](), [tooling]() ### AI overview This opinion article examines the author's experience with AI-assisted coding and argues that AI has fallen short at handling mundane software-development tasks. It focuses on project setup and manual data handling, including problems encountered when using Cursor and ChatGPT to generate project setups. ### Source excerpt "I want AI to do my laundry and dishes so that I can do art and writing, not for AI to do my art and writing so that I can do my laundry and dishes." Joanna Maciejewska I'm sure you've seen this quote from Joanna Maciejewska all over social media; I'd bet some money that there are shops already selling t-shirts and mugs with it. Despite seeing it dozens of times, I never thought about it in the context of my day-to-day as a programmer! I, like the quote's author, was more focused on AI hijacking the "classical" creative work such as painting and writing, instead of helping us humans with the most boring tasks. But it's been almost a year since I've started learning more about AI and LLM, applying them to projects, and using assisted coding. And I've gained a new perspective on this quote, this time within the tech world. And it isn't all sunshine and rainbows. I had hoped AI would take over my tech "dishes and laundry" -- the most frustrating and mundane tasks -- freeing me up to focus on the more exciting parts of my job. But ironically, it has consistently fallen short in exactly those areas. In this post, I'll reflect on how AI struggles with two chores: the frustrating complexity of project setup and the dull grind of manual data handling. The Struggle of Setup Someone once asked me, "If there was one thing in software you could magically skip, what would it be?" My answer was immediate: "setup." It's rarely fun, always takes longer than expected, and involves wrangling together tooling that shifts from project to project. We're constantly tempted to try out the new, shiny thing, only to discover a new set of issues when trying to make everything run on multiple environments or deploy. Thankfully, the software community built great instruments to ease this pain, such as Phoenix, Ruby on Rails, Docker, create-react-app, or even version checker for React Native. These tools are lifesavers. I'd probably have gone mad without them. Sincere thanks to their contributors ## The Evolution of Craft - Embracing AI in Software Development DevFeed: [The Evolution of Craft - Embracing AI in Software Development]() Original publisher: [Read original article]() Author: Zuko Mgwili Published: 2025-08-21T16:21:00Z Content type: opinion Language: en Sources: [8th Light Insights]() Topics: [AI Development](), [software-development](), [Software Engineering](), [Code]() Tags: [ai](), [ai-and-emerging-tech](), [code](), [development](), [productivity](), [software-development]() ### AI overview An engineer describes moving from skepticism to using AI code assistants in everyday software development. The article discusses reported productivity claims, the author's concerns about the loss of software craftsmanship, and the use of hobby projects to explore how AI can reduce routine development work. ### Source excerpt The Evolution of Craft: How I Embraced AI in Software Development One Sunday morning after a church service I was enjoying a cup of tea, cake and warm conversations with fellow parishioners. One of the conversations with a particular individual shifted to work and I learned that he works in the energy sector. More specifically, he is an engineering manager for an organization specializing in renewables where he oversees a number of solar arrays and other supporting infrastructure crucial for operational efficiency. He told me he was actively recruiting to in-source the development of their software systems in an effort to reduce costs. I recommended that he seek individuals who have experience with AI code assistants or at least are open to working with them, citing my own significant productivity gains with such tools. I know some may find it paradoxical that someone who has earned a living writing code for years would now advocate for tools widely predicted to render such a profession obsolete in the near future. And, to be fair, I was initially quite skeptical of the tools myself. But after some time, I've grown to embrace them, and have found great value in using them in my everyday work life. My Initial Skepticism My initial skepticism stemmed from having witnessed so many technology hype cycles that delivered little to nothing, so I was easily dismissive of the resurgence of AI. There were early claims of productivity gains of up to 50%. However, reports have since challenged that claim and some tests have revealed a more realistic picture of 10-15%. I also had a deeper concern, one that went far beyond being made redundant by AI. It was a concern and, quite frankly, a fear about the potential loss of a cherished craft that I and many others have devoted their time to perfecting, only to have it suddenly taken over by a machine. Becoming Curious To work through my emotions, I began exploring hobby projects. Many software engineers engage in such endeavors for