News for hackers. Stuff that matters.

rshetty

Thoughtworks recently launched a new agentic development platform called AI/works™. The marketing claims are quite bold, specifically targeting the "legacy modernization" problem space (which we all know is usually a nightmare).

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.

This is an amazing piece of software and thanks for creating this. We heavily use Tile38 for all our Geospatial needs in production.
It is totally possible to implement these patterns without Akka. The blog post highlights the way be implemented some of these patterns.

Ask HN: Common Patterns for Resiliency in Distributed Systems

I am collating ideas on bringing resiliency in distributed systems at scale. I had previously written a article on this here: https://blog.gojekengineering.com/resiliency-in-distributed-systems-efd30f74baf4Above article includes:1) Timeouts2) Retries3) Circuit breakers4) Fallbacks5) Resiliency TestingMore patterns I can think of include6) Rate limiting and Throttling7) Bulkheading8) Queuing to...

( Read More... | 2 comments | 2 points | on HN )
Re:One year of cycling to work on Tuesday February 20, 2018 @12:06PM (#16421866)
I also have been cycling for 2 years now everyday. 100kms average every week. Never have felt more enthusiastic and energetic at workplace. Helps concentrate on the work, beats bad traffic and gives a very good exercise overall
Re:Micro – a microservice toolkit on Friday February 09, 2018 @10:02AM (#16340616)
Would like to hear the experiences from people who have used this in production

Golang HTTP Client – Heimdall

A try at writing HTTP client with some default timeouts, a Hystrix client. Would appreciate constructive feedback on the same.https://github.com/gojek-engineering/heimdallThanks

( Read More... | 1 comment | 2 points | on HN )
Indonesia: Gojek Tech, It does have a very fascinating story to tell

Older »