## Sources

1. [The World Needs More Software Engineers](https://www.oreilly.com/radar/the-world-needs-more-software-engineers/)
2. [Radar Trends to Watch: April 2026](https://www.oreilly.com/radar/radar-trends-to-watch-april-2026/)

---

### Radar Trends to Watch: April 2026 – O’Reilly by Mike Loukides

*   **The Evolution of AI Models:** AI has transitioned from an add-on capability to a foundational infrastructure layer embedded throughout the computing stack [1]. The economics of AI are also shifting, as **laptop-class models now match last year's cloud frontiers**, dramatically reducing costs [1, 2]. There is growing diversity in architectures and vendors, moving beyond predicting tokens to explore new structures, such as Yann LeCun's stable JEPA model (designed to understand how the world works) and NVIDIA's Nemotron 3 Super, which combines Mamba and Transformer layers [1-3]. 
*   **The Changing Role of Software Developers:** The developer's primary role is shifting **away from writing code toward reviewing, directing, and evaluating AI-generated output** [4]. The toolchain is rapidly adapting, with new ecosystem additions like OpenAI's Codex plugins, open-source coding agents like Opencode, and tools like Plumb and git-memento which help keep specifications in sync and log AI coding sessions [5].
*   **Infrastructure, Operations, and Governance:** The industry is moving from asking "Can we build this?" to operational questions about how to run and govern AI safely [6]. There is a rising focus on agent governance, coordinating agents from multiple vendors via platforms like OpenAI's Frontier, and deploying local orchestration tools (like Qwen-3-coder and Ollama) rather than relying exclusively on cloud-based models [6, 7]. 
*   **Critical Security Vulnerabilities:** Security is a massive concern, highlighted by the news that **a researcher is close to breaking the SHA-256 hashing algorithm**, which could lead to hash collisions and threaten the core of web security and cryptocurrencies [8-10]. Additionally, AI expands the attack surface, leading to new threats such as AI "recommendation poisoning," deepfakes attacking identity systems, and LLMs being used to de-anonymize authors at scale [9, 10].
*   **Workforce Restructuring and Cognitive Load:** Despite fears of AI job replacement, demand for software engineers is recovering, while product management and AI roles are experiencing massive growth [11, 12]. However, there is a human cost: **cognitive overload is increasing** due to imprecise AI prompting, and traditional collaborative work patterns are eroding as developers spend more time on individual coding with tools like GitHub Copilot [11, 12].

### The World Needs More Software Engineers – O’Reilly by Tim O’Reilly

*   **The Engineering Demand Paradox:** In a conversation with Box CEO Aaron Levie, the authors explore a real-time "Jevons paradox"—because AI agents make engineers 2 to 10 times more productive, the cost of software development drops drastically [13, 14]. As a result, **previously unviable software projects become economically justified**, leading to a massive expansion in the total addressable role of engineers across all corporate functions, including marketing, legal, and accounting [14, 15].
*   **The Problem is Context, Not Connectivity:** While systems are becoming more interoperable, getting data structured appropriately for AI agents remains incredibly difficult [16]. Levie predicts a **decade of infrastructure modernization** is required because if data is scattered across 50 different legacy systems, agents will struggle to find the context they need and will end up "rolling the dice" on their tasks [16, 17]. 
*   **Bridging Deterministic and Probabilistic Computing:** Engineers are now programming two types of computers simultaneously: deterministic (repeatable, hard-coded software) and probabilistic (LLMs) [18]. Determining when to lock a process into strict code versus when to leave it fluid and adaptive is **the "trillion-dollar question"** that makes software engineering more technical and complex, not less [18]. 
*   **Humans vs. Agents:** Humans operate with decades of ambient context and domain knowledge that they get for free, whereas **agents are like expert new employees who arrive with zero context** [19, 20]. To make agents productive, enterprises must provide highly precise, surgical context (like AGENTS.md files) without overwhelming the AI, which requires reengineering workflows from the ground up [20]. 
*   **Startups vs. Incumbents:** AI-native startups possess a significant advantage in areas of **unstructured, messy, and collaborative work** (such as legal review, tax preparation, and audits) where there is no existing software incumbent, only professional service firms [21, 22]. Conversely, existing enterprises risk failing if they attempt to merely stuff AI into legacy org charts and workflows rather than fundamentally reinventing them [22].