The paper examines how a large embedded systems company is transitioning to an AI‑first organization, focusing on the role of autonomous AI agents in software engineering. Through a mixed‑method study involving 40 workshop participants—scrum masters, architects, managers, and product owners—the authors identify expected impacts on team structure, required competencies, organizational strategies, and developer roles. The study concludes with a concrete roadmap and discusses implications for federated AI team formation, human‑in‑the‑loop practices, and sustainable AI adoption in embedded software engineering.
arXiv:2606. 05608v1 Announce Type: cross Abstract: For over half a century, software engineering has operated on a foundational premise: human engineers decompose problems, encode decision logic into static code, and manually adapt that code as requirements evolve.
The article examines the psychological costs that software professionals face when organizations adopt artificial intelligence (AI) in software engineering workflows. Through a case study involving 21 interviews at a large software development services company, the authors identify several negative impacts—accountability anxiety, craft identity disruption, erosion of meaning and satisfaction, increased cognitive load and workload, and uncertainty distress. They also describe how practitioners cope by restoring control, adopting protective adaptations, or absorbing the costs, arguing that AI adoption should be viewed as a human transition rather than merely a technological or organizational change.
Discover how leaders can build AI-ready organizations using clear strategy, training, governance, and accelerated innovation.
arXiv:2609.24348v1 Announce Type: cross Abstract: AI coding agents increasingly support software development beyond code completion, including planning, implementation, testing, and repository-level...
The paper introduces Spec-Driven Agentic Development (SDAD), a framework that leverages large language models to ingest extensive functional requirement documents and repository context in a single workflow, turning specification quality into the engine for autonomous software delivery. SDAD blends disciplined upfront formalisation with rapid implementation, encompassing intent capture, machine‑readable specifications, agentic synthesis, and multi‑agent verification with human sign‑off. It positions AI‑code as a fourth production paradigm, compares it to traditional Waterfall and Agile approaches, and extends the model to team role evolution, quantitative governance metrics, and a staged migration blueprint for practical adoption.
The report examines how software architects view the growing use of AI development agents in their field. A focus group of 22 industry and academic participants discussed current practices, trust, validation, governance, and educational implications, concluding that decision‑making, accountability, and guardrail authoring remain human responsibilities. They introduced the concept of harness engineering—building systems that govern AI‑assisted creation—and identified criticality and cognitive debt as key factors for calibrating human oversight.
arXiv:2607. 05125v1 Announce Type: cross Abstract: This paper presents an exploratory evaluation of how increasing levels of AI autonomy affect software development productivity, requirement adherence, and developer cognitive workload.
This paper presents an exploratory evaluation of how increasing levels of AI autonomy affect software development productivity, requirement adherence, and developer cognitive workload. A team of four developers reimplemented the same full-stack web application across three sequential phases: partial AI-assisted development using GitHub Copilot, an AI-exclusive workflow using GitHub Copilot, and an AI-exclusive workflow using AWS Kiro.
AI coding agents increasingly support software development beyond code completion, including planning, implementation, testing, and repository-level task execution. Their practical use, however, often...
The paper titled "Professional Software Developers Don't Vibe, They Control: AI Agent Use for Coding in 2025" examines how experienced developers employ AI agents in software development. Through field observations and surveys, it finds that developers value agents for productivity but maintain control over design and implementation to ensure quality. They use agents as collaborative tools rather than full delegation, selecting tasks based on suitability and leveraging their expertise to guide agent behavior.
arXiv:2609.21192v1 Announce Type: new Abstract: Organizations deploying agentic artificial intelligence must determine more than whether a model is trustworthy; they must establish what to validate,...
arXiv:2607. 21495v1 Announce Type: new Abstract: AI agents are increasingly created inside organizations by non-engineering users through low-code, no-code, and conversational development environments.