/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

How Morgan Stanley is using its DevGen.AI tool, built in-house on OpenAI's AI models, to translate legacy code into English specs for developers to then rewrite

Morgan Stanley is now aiming artificial intelligence …

Wall Street Journal Isabelle Bousquette

Context & Ripple Effects

Morgan Stanley’s use of an internal tool built on OpenAI models turns legacy-code interpretation into a structured handoff: the model produces English specifications, while developers retain responsibility for the rewrite. That places AI first in the documentation and comprehension layer of software modernization rather than presenting it as an autonomous coding replacement.

The story extends the shift from broad employee experimentation with generative AI to institution-specific workflows; related coverage also shows a peer bank planning to augment its workforce with an AI software engineer.

First-order effects

  • Morgan Stanley developers can use DevGen.AI to extract readable specifications from hard-to-interpret legacy code before rewriting it, changing the starting point of modernization work.
  • OpenAI’s models become a component inside a bank-controlled development workflow, while human developers remain the implementation and validation layer.

Second-order effects

  • Other financial firms pursuing comparable legacy-system work face added pressure to test AI-assisted code understanding, especially as Goldman Sachs moves toward AI augmentation for software-engineering work.
  • The near-term value shifts toward workflow design, review controls, and the quality of generated specifications—not merely access to a general-purpose model.

Third-order effects

  • If this pattern holds, enterprise AI adoption will increasingly be measured by whether firms can embed models in bounded, auditable processes around their proprietary systems, rather than by standalone chatbot usage.
  • Legacy-code modernization may become an early proving ground for a broader division of labor: models translate and summarize system knowledge, while accountable staff make production changes.

The trend: Frontier models are being institutionalized as controlled workflow components that help enterprises convert accumulated internal knowledge into operational change.

Discussion

  • @triangulator.org Kevin Webb on bluesky
    For a lot of orgs accelerating code maintenance is even more significant, as the WSJ notes in this piece today.  These are systems with astronomical switching costs that are often holding back all kinds strategic/org-level progress.