[INFO] RouteOptimizer: Using ModernRouteOptimizer [INFO] Delivery ETA: 6.2 hours (previous: 8.7 hours) Leo leaned back. The trial still had three days left, but he didn’t need them. He opened the company credit card form and typed: .NET Reflector Professional v11.1.0.2169 – 1 license – perpetual with one year maintenance.
Later that night, he sent a Slack message to the team: “Found Gerald’s hidden Euclidean bug. Also, never trust a TODO comment from 2016.”
The tree view exploded: namespaces, classes, methods. He clicked on the OptimizeDeliverySequence method. In the right pane, the decompiled source code materialized like a ghost writing itself. .NET Reflector Professional v11.1.0.2169 -Win- ...
He right-clicked. . v11.1.0.2169 opened a new tab showing a call graph—red lines for missing references, green for internal. A blue node glowed: LegacyGPSBridge.GetApproximateRoadDistance . No implementation. Just a P/Invoke to a 32-bit unmanaged DLL.
He dragged RouteOptimizer.Core.dll into the workspace. Later that night, he sent a Slack message
That was the bottleneck.
It was a gray Tuesday morning when the email arrived in Leo’s inbox. In the right pane, the decompiled source code
All they had were the compiled DLLs. Thirty-seven of them, baked in mystery.
public List<DeliveryStop> OptimizeDeliverySequence(List<DeliveryStop> rawStops) { // TODO: Replace with actual A* implementation // Gerald's note: Use Manhattan distance for city grid if (rawStops.Count < 3) return rawStops; var optimized = new List<DeliveryStop>(); // ... 200 lines of cryptic logic ... return optimized; } Leo squinted. Manhattan distance? Their trucks ran across rural Montana, not New York. That explained the bizarre fuel overages last quarter.
He spent the afternoon rewriting the decompiled logic into a new class, ModernRouteOptimizer , using actual road data from a REST API. Then he used (new in v11) to compare his version with Gerald’s original. The side-by-side view highlighted changes in green—refactored loops, removed hacks, added caching.