Vertyanov+successor+programmer [2021] File

The Last Czar of the Compiler: In Search of the Vertyanov Successor

In the annals of programming folklore, certain names are not merely code poets; they are architectural prophets. The name “Vertyanov” carries a phantom weight. It suggests a figure who did not just write functions, but built cathedrals of logic in the brief, unforgiving language of assembly or the cryptic elegance of Forth. But every empire, digital or otherwise, needs a successor. To be the "Vertyanov Successor" is not a job title; it is a curse, a privilege, and a philosophical paradox wrapped in a stack overflow.

Path A: The Apprenticeship (Overlap)

The ideal scenario. The current Vertyanov is still employed, and you are hired as their shadow. vertyanov+successor+programmer

• Action: Demand 3-6 months of overlap. Do not accept a handover document.
• Technique: "Pair programming in reverse." You type nothing. Vertyanov types. You ask "Why?" for every line. Record every session.
• Outcome: You become the documented successor. The company announces: "[Your Name] is the Vertyanov successor programmer."

What a “Successor Programmer” Must Deliver

2. Modernization

• Migrate from MQL4 → MQL5 or a broker-agnostic platform (Python + API).
• Fix execution latency issues (original had slippage on fast markets).
• Add risk management features (position sizing, max drawdown, time filters).