From programmer to CEO

Because of my work, I often meet a range of people from programmers to CEOs. And sometimes my job is to assess the capabilities and knowledge structure of these people. In this process, I have found that from ordinary programmers to CTOs, the general abilities and knowledge structures are very similar. And if a CTO is promoted to CEO, then he may not really need to know some new knowledge or must have any new capabilities.

Undoubtedly my findings did not exceed my expectations. And I also secretly secretly rejoiced, because the world shows a real law everywhere, that is, being in a high position is not because they do more, but because they do better.

Sadly, it seems that people don't know this, and the lower the position, the less they know it. And I suspect that a lot of people, especially those in high positions, are consciously or not letting people know about this. Of course they have reasons for doing so, and motives for doing so.

And what's really sad and contemptible is that some people are taking advantage of this for profit. For example, some people write books specifically for CTOs, and how to write about how to get from programmers to CTOs.

However, do you really know that the CTO really knows something that programmers don't know? Or can a programmer be a CTO if he knows something? They won't ask such questions, and they won't let you ask them. So further, does CTO really have more capabilities than programmers? In fact, this is not to say.

But you look around, what those people are saying, what they are feeding you. It can be said that from the workshop, to the knowledge system, and then to java, all aspects are telling you how much you need.

In fact, this is also a kind of success study, a kind of success study that has no benefit to people and can only make you waste a lot of time.