Some time ago a segment appeared on the Internet, comparing staying up late to cultivating immortality, divided into these levels of body refinement, qi cultivation, foundation building, jindan and yuanying (does it have the feel of a cultivation novel... ) The later you go to bed the higher your immortal cultivation rank is. This topic came up and caused a lot of buzz on the internet. I have a friend who is a developer saw a contemptuous laugh: for program apes, staying up late and working overtime is a common occurrence, no technical content at all, what kind of immortality is this? I'll tell you about the hierarchy of immortal cultivation among our developers.

training period

typist

Most developers at this stage are rookies who have just left school and the classroom without much work or project experience.

At this time, their understanding of the program is limited to regular character entry from a book or from memory, and some of them are not even sure what instructions the characters they enter represent, so they often appear to be at a loss when errors occur, doubting the software, doubting the system, and even beginning to doubt their lives, only to find out that they have only entered a semicolon less.

The stage, while seemingly simple, is indeed also the threshold that most easily stops amateurs from the developer hall of fame.

For the whites located on that level, the Remember not to get hooked on martial arts secrets like "30 Days to Mastery , which could easily turn into Two Weeks to Getting Started to Giving Up for those who aren't starting out. There's not really no shortcut to getting started, just find a real-life master to bring you in.

the stage when one is practicing qi

development engineer

Developers at this stage are basically within three years of joining the industry, have some work experience, and have their own understanding and perspective on development programming. Knew the meaning of variables, logic and functions.

At the same time can also be skilled in the use of CV method (Control + C, Control + V) to imitate the previous case or network examples for functional implementation, but only to achieve the logic of the requirements only. Also because there is no understanding of what this code really means, this pile of code that is implemented is usually a headache and a high source of bugs.

For rookies located in that tier, remember not to get hooked on the Thinking In XX series of books. The best way to practice is to read more open source engineering code, participate in more projects, and complete a metamorphosis from quantity to quality, thus moving to the next level.

foundation building stage

Research and Development Engineer

Developers at this stage then typically have 3-5 years of industry experience. Can take on the role of technical director of a company and the backbone of a team.

At the same time, this level is also the most dangerous and easy to lose in all the levels, the danger is that because of indulging in comfort zone and blind confidence and stagnation, eventually due to the decline of energy and be replaced by fresh meat; its lost in the project is only good at solving the project is responsible for or previously touched a piece of the problem, for the system architecture lack of overall awareness, do not have the ability to build a new system.

For the "attacking lions" at this level, it is important not to get caught up in the surface of the code, nor to limit yourself to APIs or source code collections. The best way to practice is to constantly think and refine your own understanding of best practice , thus laying a solid foundation for moving on to the next stage.

at the JinDan stage

architects

Developers at this level basically have 5+ years of experience and are well known in the industry, and are the gods that many people admire.

They prefer to describe themselves as“ artists” rather than architects， They even drink a pound“ Guan Gong Fang+ sour plum soup” All can accurately draw you a diagram of the system architecture they have designed、 Functional Structure Diagram、 database model， and can perform architecture-based system architecture optimization based on actual system usage、 Performance optimization, etc.。

Engineers entering this stage have moved away from the obsession with moves and into the art of practicing the ways of design and programming.

yuan baby stage (metamorphosis)

consultant

consultant It's a special presence.， if anything architects An ascetic who pursues the way of design and art， that consultant It's the preacher on the path。

He may not have developed a classic architecture, but after a short observation he can point out the optimization of the current architecture; he may not be able to write a complex source code, but can usually solve technical problems with the simplest solution; he may not understand the business background and expertise of your problem, but can enlighten you through cross-disciplinary knowledge to solve the problem.

In fact, if you look at it this way, you can see that development is similar to immortality cultivation, it's all about day-to-day "cultivation" and a long period of experience in the field to gain leveling up. So where do developers go from here after these five stages? And how should grades be classified? Everyone can come and give your opinion.

Recommended>>
1、Microservices SpringBoot Development MongoDB Application Practice
2、Theres this software Your document management efficiency increases by at least200
3、Just now XCMG Information was successfully selected as the second batch of manufacturing innovation center cultivation list in Jiangsu Province
4、Industry 40 change the leap from automation to smart factories
5、Frontend practice you gotta be able to use it

已发送

发送中