From Pair Programming to Empowering the Entire Team: How Gate is Adopting the AI Development Paradigm

Not many people know this, but I come from a technical background. Twenty years ago, at an investment bank in the Asia-Pacific region, there were probably about fifty people who truly understood algorithmic trading, and I was one of them; at that time, the core of the system was not just "functional," but had to be reliable in the long term under constraints such as latency, stability, monitoring, and risk control.
Therefore, I was initially very opposed to "Vibe Coding," because it could easily lead people to misunderstand that programming could be done by "giving instructions based on feelings."
Later, I personally used Claude Code, Codex, Copilot to create some small software and internal tools, and only then realized that the issue was not with AI writing code, but with the misleading nature of this term: when AI is integrated into the engineering process, it is more like an extension of Pair Programming, combining "production" and "review" into a single cycle, allowing people to shift their focus from repetitive work back to decision-making.