How to be a happy ASP. NET programmer

First, I want to explain the two keywords in the title: "happy", "ASP. NET programmer ".

 

Some people want to be an "Outstanding" programmer or a "senior" programmer, simply put, it is a "Daniel"-but this article does not aim at this development direction, not to say that I do not encourage everyone to go in this direction, but to me, I pay more attention to "happiness" itself. -And unless you are a genius that leads to "Outstanding" or "senior", you need a correct attitude and a long process at the same time.

 

So why do we just talk about "ASP. NET programmer "-- this is a portrayal of me and a kind of person-we are following Microsoft and choosing different regions on Microsoft's platform to build our own city pool. -- whether out of helplessness or pride. -- to a large extent, Microsoft's actions and changes will affect our development prospects.

 

I don't want to advertise my abilities. In fact, I am just a very common programmer who has no technical insights and has not created a system that I am proud. but at work, I enjoy coding and project organization. -- a friend asked me how I could be filled with such joy every day. I began to think about some long-lost questions.

 

1. Keep a humble and confident heart. What does this mean? Humble means to admit your limitations and your shortcomings. Self-confidence represents the logic and Framework Theory of human design, and you can learn it as long as you spend time.

 

During work and communication with colleagues, don't worry that you tell them that you don't understand will degrade your identity. as a programmer, the colleagues around you are actually very smart. During the conversation, do you know exactly what you think. if you can admit your limitations and consult others modestly, the other party will not only "despise" you, but also respect you and appreciate you. more importantly, your advice will give him a sense of accomplishment. This is a kind of healing and affirmation for him. In other words, this is a "win-win" good thing.

 

[Special Case: if you meet someone, you will be bullied by your humility. Be careful to protect yourself. but do not "pretend to be an ordinary person". Such a person is often hurt in this respect.]

 

2. Share your "wealth" with others. As a programmer, what is your wealth? -- "Knowledge", "experience". Sharing your wealth with the online community and in other things will make you richer.

 

I have heard of a lecture. poor people focus on themselves, the middle class squeeze others to raise themselves, and rich people influence others. please note that poverty and wealth here refer not only to money, but also to people with wealth in their hearts who do not focus only on themselves or keep others under pressure. I have seen many people who like to share their "wealth" with others. Their daily growth, continuous progress, and help more people.

 

[Special Case: I have met some people who have made a fortune and seldom feel happy.]

 

3. he holds high in pragmatism and does not pursue theoretical excellence. as an "ASP. NET "programmer. -- practicality is very important to me. from. net1.0 till now. net itself is constantly improving, and our tools, design patterns, and coding methods are changing. if you want to "understand everything" or "pursue perfection", you are done.

In. NET1.0, a lot of things are no longer needed now. It took a lot of time to learn this part. If it wasn't used, it would be a waste.

 

To meet the current needs of customers or bosses, learning the knowledge required by current projects is the essence of "pragmatism", accepting incomplete code in projects and imperfect systems.

I have read many articles advocating "excellence". For. NET projects, I think it is a misunderstanding. When Google and Apple.com are inaccessible.

We can only do our best with limited time and resources. -- don't drive yourself crazy.

For the readers who are management or boss, all of them are mixing in this pool to take a step back. in many cases, the customer may not be able to use the system that has worked hard for a long time.

When I used to work at HSBC, I heard that a programmer's code was wrong. As a result, the Bank lost 1 billion yuan, and the bank did not dismiss this guy-because this is not his fault, it also involves testers and quality checks.

 

I don't mean that software quality is not important, but that we should focus on actual needs rather than unrealistic requirements.

[Special Case: I heard that some bosses in some companies have very strict requirements on programmers. I think I can try to communicate with them and inject more "sense of humor" into the company.]

 

4. focus on new things and stay on a constant basis. never give up on new things. cnblogs is often used to subscribe to various types of feeds you like. Many times, a simple new thing will save you a few days of exploration.

However, optical newest is not enough. many basic things, such as the C # language itself and the design mode, must be learned. I don't know why some people are commenting that asp.net programmers are dragging controls ....

 

5. understand yourself and be good at using existing code. there is such a story that the customer told the programmer about his needs. A Daniel immediately knocks on the keyboard and starts programming at a speed of 80 kilometers per second. Another Daniel said, "and so on, I have done this thing ".

Whether you have done it before or you can find code online, it's your asset. Spend a little time organizing your assets.

[Special case: it takes a week for someone to find the code they need on the Internet and finally write it on their own. -- don't be too persistent. Ask the programmers around you. Maybe they can tell you the answer soon.]

 

If you disagree with my point of view, you can discuss it. If you agree, you can recommend it so that everyone can pay attention to the joy of programmers.