In essence, most enterprise applications are adding, deleting, and modifying. However, some companies have complex and professional businesses, and some companies have many online users. There may be a great difference between your adding, deleting, and modifying and others’ adding, deleting, and modifying.
Select top 10 from news list order by reading desc; select top 10 from news list order by reading desc; select top 10 from news list order by reading desc
But if it is a website or APP equivalent to Tencent news volume, every minute 1 million people enter the home page, then can you make such a simple query? Believe that the database is certainly not carry! At this time, the seemingly simple “add, delete, check and change” is actually supported by a large number of technologies.
Reflect on your work
It is suggested that programmers who have been working for two or three years should reflect on their current work and make simple additions, deletions, checks and changes:
- Is the business professional? Can I have a long-term career in this field with this business knowledge? For example, doing core systems in a finance-related industry, or doing payment related business all the time.
- Is there a large user base? Are there high concurrency scenarios? What measures did the project take to increase the high availability of the system?
- Can you participate in process discussions and development? Can you participate in architectural or functional design? Can you touch the core code?
- If none of the above is true, then you are probably doing simple add, delete, change and check. This type of coding is “manual labor”. Or maybe you’re making a good salary, working nine to five without overtime, and you’re happy with your job, but! Get out of your comfort zone; Because you will soon hit the ceiling of your career and you will soon face the risk of losing your job.
How do programmers practice
If you’re in that comfort zone right now, here’s some personal advice:
- If you’re open to job-hopping, do it: I don’t encourage programmers to jump ship too often, but I have to say that job-hopping is the quickest way to solve this problem; [Platforms matter], you can get out of your comfort zone by choosing a higher platform: In the previous unit, our technology stack was SSH + Oracle. Now the unit is mainly Spring Boot and Spring Cloud. Both relational database and non-relational database are used, which has improved a lot.
- If you think your current company is good and worth a lifetime of hard work, first consider whether you can make your current project better and introduce more mainstream technology components to solve the problems encountered in the project. Ability to take on more important jobs;
- Programmers need to keep learning, whether they jump ship or not: Fragmented time to learn is laudable, but full time to learn is encouraged. It’s best to turn off all communication software and avoid interruptions. And the learning content through notes, blogs and other forms of record.
- As for the technical route, the suggestion is still from the work: for example, in the project relational data use more, so in addition to write SQL, also have to understand some database optimization knowledge, if can introduce some NoSQL database would be better; If the number of users increases and the project becomes more difficult to scale, it is important to understand the distributed architecture design, how to break up a large monolithic application, non-core functions can be introduced into message queues for asynchronous processing, and so on.
About the development of programmers
1. Try to be ahead of the industry
I used to like to say that if you’re in the top 30%, 40%, or even 50% of your industry, you don’t have to worry about losing your job.
But now I also want to add the premise that this works by the age of 30; After 30, the fear of losing your job should begin, and you may need to be in the top 20% of your industry.
If that’s not enough, be in the top 10%!
2. Diversify
Nowadays, the employment pressure is increasing. For many companies, they do not require programmers to be particularly good at coding. They want to hire “talents” who can solve problems in multiple roles.
So if a programmer has deep business knowledge in some business area; Or some knowledge of operations, data analysis; Or know how to communicate with requirements/products to coordinate the operation and development of the entire project; The career path will be wider and there will be more options when it comes to career bottlenecks.
3. Get a side hustle related to your main business
Income from work is a “single point,” and in software architecture, a single point of risk is high. What can bring essential change is to turn “single point” into “multi-thread” and “distributed”, to do some of their own good at “small business”, step by step accumulation, when to a certain extent, you may naturally have the courage to face unemployment; And in the process, you could be in the Top 10% of your industry without even realizing it.
- Pick up the project: that is, we usually say pick up the private work, some programmers feel this is very difficult, in fact, after the first step, the way behind is relatively easy; My previous project manager took a “big job” and quit to start his own business.
- Make products: Make products, the cycle will be relatively long, can be software, website and APP; The product is not necessarily directly profitable, the profit can depend on the flow (use more people, profit is easy);
- Technical output: you can give lectures and do consulting offline. Of course, these need contacts, otherwise no one will invite you. Online can do more things, do video, column, live and so on, of course, these are the need for “dry goods”, years of technical accumulation of programmers, you can consider these channels.
In short, since you have chosen to be a programmer, you should be prepared for lifelong learning, otherwise you will easily be eliminated by the industry.
Uncle will point code | article “original”
