why / how
this article attempts to encourage programmers to go into management, but neglects to offer any enticements that programmers can understand.
perhaps one benefit of management from a programmer's perspective is that in the end, the jobs are similar: to carve structure from chaos, making variables constant, making constants configurable. a beautiful program runs well (and hopefully looks good to the programmer and to posterity). similarly, a beautiful team works well, looks good to management, and makes a name for itself. the manager is largely responsible for this; teams rarely evolve discipline naturally. a manager who has a programming background is better equipped to understand both static and dynamic forces (assuming this manager is a good programmer!), than someone who does not have experience creating bugs.
having said this, however, i would encourage programmers to NOT become managers in one step. learn to manage yourself first, including the grotty stuff like testing and documentation. find joy in excellence at all levels, not just code. try extreme programming (pair up w/ another programmer and be hyper critical) or other non-solo methods. management is meta-programming and frustratingly satisfying.