{
  "id": 8228884,
  "title": "Presentation: Complexity and Creativity in Software Engineering",
  "url": "https://urgent.news/2026/09/18/presentation-complexity-and-creativity-in-software-engineering",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-18T11:00:00.000Z",
  "source": {
    "name": "InfoQ",
    "slug": "infoq",
    "url": "https://www.infoq.com/presentations/ai-software-engineering-complexity/"
  },
  "original_language": "en",
  "account": "Phillip Mortimer, a Senior Staff Machine Learning Engineer at Carta, delivered a presentation at QCon London discussing the intersection of complexity and creativity in software engineering. He began by introducing Arthur Whitney, a Canadian computer scientist and mathematician who wrote the J Incunabulum, a legendary piece of code that serves as the foundation for the J programming language. Despite its brevity, the J Incunabulum includes an object model, memory management, a standard library, a parser, a lexer, and a read-eval-print loop, all within a single working interpreter. Whitney's code exemplifies the concept of write-only software, which is code so complex and arcane that only its author can understand it. Eric S. Raymond, an American software developer and open-source advocate, defined write-only code as code that cannot be comprehended or modified by anyone other than its creator. Mortimer argued that, in the era of AI code generation, all software is inherently write-only, but this is not necessarily a bad thing. He provided two examples of write-only languages: APL, a language designed for rapid development in financial institutions, and regular expressions, which are powerful yet unreadable tools used for pattern matching and string manipulation. Despite their complexity, these write-only tools enable developers to accomplish tasks more efficiently. Mortimer concluded by emphasizing that write-only code can actually foster creativity and innovation among software engineers, as it challenges them to think critically and find alternative solutions.",
  "summary": "Phillip Mortimer discusses the shift toward write-only software driven by AI code generation. He explains why traditional pull requests are broken and shares how engineering leaders can manage complexity by decoupling intent from implementation, automating code reviews, and building self-healing architecture to unleash developer creativity across senior engineering and architecture teams. By…",
  "key_points": [
    "Eric S. Raymond coined the term \"write-only code\" for software only its creator can understand.",
    "Write-only languages like APL and regexes enhance developer efficiency despite their complexity."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}