Exploring five critical questions shaping software engineering through 2026, with contrasting scenarios for each. These lenses help prepare for the evolving ...
Opinion | The A.I. Disruption Has Arrived, and It Sure Is Fun
We’re entering a new renaissance of software development. We should all be excited, despite the uncertainties that lie ahead.
Opinion | The A.I. Disruption Has Arrived, and It Sure Is Fun
We’re entering a new renaissance of software development. We should all be excited, despite the uncertainties that lie ahead.
You have to beat the models at something
In 2025, I wrote that software engineers ought to be assessed by “value over replacement”: not how much money they made for their company, but how much they…
Convivial design heuristics for software systems
The theme of this workshop is the proliferation of ideas about calling into question the cultural roots of our current programming languages, and the search for alternative paradigms with other cultural bases.
Challenges and Paths Towards AI for Software Engineering
View recent discussion. Abstract: AI for software engineering has made remarkable progress recently, becoming a notable success within generative AI. Despite this, there are still many challenges that need to be addressed before automated software engineering reaches its full potential. It should be possible to reach high levels of automation where humans can focus on the critical decisions of what to build and how to balance difficult tradeoffs while most routine development effort is automated away. Reaching this level of automation will require substantial research and engineering efforts across academia and industry. In this paper, we aim to discuss progress towards this in a threefold manner. First, we provide a structured taxonomy of concrete tasks in AI for software engineering, emphasizing the many other tasks in software engineering beyond code generation and completion. Second, we outline several key bottlenecks that limit current approaches. Finally, we provide an opinionated list of promising research directions toward making progress on these bottlenecks, hoping to inspire future research in this rapidly maturing field.
The Evolution of Software
Last week Chris Paik published a Google Doc titled, The End of Software, where he articulates the lowering cost of software development and potential implications. He ends the piece with a provocative statement: "Majoring in computer science today will be like majoring in journalism in the late...
Sustainable software manifesto
The systems we build are never neutral. They can magnify harm or support a just and sustainable society. How we build today shapes tomorrow’s possibilities.
The third golden age of software engineering – thanks to AI, with Grady Booch
The third golden age of software engineering – thanks to AI, with Grady Booch
How Cursor is building the future of AI coding with Claude
X : What are you interested in? Me : Wow, that varies constantly. Right now? There are a number of topics that I'm actively pursuing … a) When we talk about software engineering we typically think… | Simon Wardley
X : What are you interested in? Me : Wow, that varies constantly. Right now? There are a number of topics that I'm actively pursuing … a) When we talk about software engineering we typically think about the active part of creating code but software development is currently practised as a craft not an engineering discipline. The only engineering discipline in software engineering is testing. This creates a flaw in the comparison with using AI to code because development itself has never been optimised. If all we have to do is write code and we can automate that part then we can just replace those expensive typists with LLMs but development should be, and has the capability to become an engineering discipline. It's just not that for now. https://lnkd.in/eSRprhbf b) Most people talking digital sovereignty are doing so with good intentions but they literally have no idea what they are talking about. This is not because they are daft or foolish but because they cannot see the environment they are talking about. They are like generals talking about territorial sovereignty with no idea of what territory is or how you represent it. https://lnkd.in/eku2X_Ea c) Architectural decisions are made in code and not in the diagrams we create. Those architectural diagrams are more like prompts, wishes and beliefs of what a system should be but rarely reflect the actual system. This creates additional problems when the real architectural decisions are made by coders but coding itself is a craft not an engineering discipline. d) The current crop of LLMs / LMMs are driving us towards a new theocracy. We can counter this through diversity, critical thinking and open approaches but that does mean we have to get to the point of all symbolic instructions being open. That includes the training data. Copyright is a distraction from the real issue that we don't know what the systems are being trained on. Guardrails are a post event kludge. https://lnkd.in/exJVmNvD e) The medium we use in conversational programming environments such as cursor and lovable (or what we call vibe coding when not looking at the code or Software Engineering + AI when looking at the code) appear to be flawed. We are focused on text not images. The change of medium changes the conversation, the corollary is the conversation we have around the screen and the one we have around the whiteboard. Same problem, different medium, different discussion. https://lnkd.in/e_W6b6z3 f) "Value" in consulting land is mostly theatre rather than something meaningful. There are many forms of value but often we fail to identify this, quantify it or even measure it. https://lnkd.in/eeNbR_VY g) Rewilding Software Engineering. To change software development into an engineering practice, we need to introduce two wolves - one that software engineering is a decision making process and secondly that we need to build tools for problems we are facing - https://lnkd.in/epyUnqgh
R. S. Doiel, Software Engineer/Analyst — Robert's ramblings
By R. S. Doiel, 2026-02-21 (revised: 2026-03-03, epilogue added 2026-03-27)
Laws of Software Engineering
A collection of principles and patterns that shape software systems, teams, and decisions.
