rshetty | 2 months ago | on: Anyone tried Thoughtworks' new AI/works legacy modernization platform
rshetty's comments
rshetty | 7 years ago | on: Show HN: Tile38 – Realtime geofencing and geospatial index
rshetty | 8 years ago | on: Ask HN: Common Patterns for Resiliency in Distributed Systems
rshetty | 8 years ago | on: One year of cycling to work
rshetty | 8 years ago | on: Micro – a microservice toolkit
rshetty | 9 years ago | on: Ask HN: Which developing nations have interesting tech stories at the moment?
rshetty | 10 years ago | on: Ask HN: What's the hardest problem you've ever solved?
rshetty | 11 years ago | on: Ask HN: What OS do you run?
Hardware: Retina Mac Book Pro 16GB
Tools: Vim, Ruby, Rails, Git, Haskell, Javascript, RubyMine.
rshetty | 14 years ago | on: Yahoo’s Thompson Out; Levinsohn In; Board Settlement With Loeb Nears Completion
rshetty | 14 years ago | on: How Linux Shell saved my Day?
rshetty | 14 years ago | on: What sites can I use for programming problems?
rshetty | 14 years ago | on: What are the best ways to learn Python if you are a beginner?
According to the announcement and their technical guide, the workflow is:
Ingestion: "Blackbox" reverse-engineering of legacy binaries/code (even without full source access in some cases).
Specification: It generates a "SuperSpec" — a machine-readable functional specification enriched with regulatory/security context.
Forward Engineering: Agents use the Spec to generate new code, tests, and pipelines.
Lifecycle: It claims to support a "3-3-3 delivery model" (Idea to Production in 90 days) and includes self-healing/regenerative capabilities for maintenance.
This sounds like the "Holy Grail" of software engineering, but I am skeptical about how well this works on actual enterprise spaghetti code versus carefully curated demos. "Reverse engineering into a perfect spec" is historically where these tools fail.
I’m looking for insights from anyone who has piloted this or works at TW:
How does the "Code-to-Spec" reverse engineering actually handle heavy technical debt or undocumented business logic?
Is the "SuperSpec" truly editable/maintainable by humans, or does it become a new black box?
How much "human in the loop" is actually required for the 3-3-3 model?
Is this built on public LLMs (Claude/GPT-4) or proprietary models trained on legacy patterns (like COBOL/Mainframe data via their Mechanical Orchard partnership)?
Any details on the reality behind the marketing would be appreciated.