Working Surfacelink · 17 Nov 2026
04
A street of small garden sheds built in many odd shapes by different hands, while one caretaker seen from behind walks along the row carrying a single large ring of keys and a toolbox, the whole scene drawn with wide empty margins on every side.
LeadDev

Everyone’s a software engineer now

Chris Stokel-Walker · 16 November 2026

Company story · roles · collaboration · Changing roles

Read the original
Takeaway

Staff outside engineering now build their own software with AI, a LeadDev report finds, and engineering teams inherit tools they did not design.

Summary

Chris Stokel-Walker, a freelance journalist, wrote in LeadDev, a publication for engineering leaders, about employees who are not software engineers building applications with AI tools. The finance company Ramp and the payments company Stripe encourage staff to do so. Christina Troy, senior IT manager at the automation company Tines, and Edona Elshan, an assistant professor at the Vrije University of Amsterdam, describe the oversight problems that follow.

Key points
  • Retool, a maker of software for building internal tools, surveyed 817 people who build software. Of those, 60% had created something outside IT oversight in the previous year.
  • Troy says IT teams often learn about employee-built software, and the systems it connects to, only when something breaks.
  • Tines built a platform called Tines 3B. Employees build software there, and IT and security teams see which applications reach which tools and data.
  • When an employee who built a tool leaves, the tool often passes to an engineering team that had no part in building it.
Implication

An engineering leader can give staff a place to build where IT sees each application's access to tools and data from the start, as Troy advises. Troy describes her own employer's product, and the article reports no results from it.

Plays
Engineering

Give employees who build their own software with AI one shared platform where IT and security teams can see which applications reach which tools and data.

Derived by Working Surface from the article; more in the Playbook. Source line: Employees need guardrails and frameworks within which to build, and IT teams need to have visibility from the outset of these builds.

Source issue

17 November 2026: as AI agents and staff outside engineering produce the stories, specifications and tools that others build on, a team must name who checks them and who looks after them.