Programmer's Development project is always halfway through Many programmers ' projects often give up halfway. They have so many good ideas, but many of them are in the dream. Almost every software developer has one such folder, many of which are unfinished projects, and many of these programs are really great ideas at the beginning of the birth. Like these people, I also have a lot of good ideas, some even now some enterprises are using. For example, it is decided to make e-commerce profit on ebay or Amazon, make a business-based social network (plumbing, electronics, software development, etc.), Bitcoin search engine, develop a CSS framework to replace Bootstrap, Find the most attractive people from Instagram and develop a real-time access statistics engine, such as the example endless. I've done almost every project, but I haven't seen one that's finished. When I talk to my colleagues and friends about this topic, they also generally reflect, and so do they. Lots and lots of good ideas died in their folders. Why is that? Because of the success of the lack of motivation first of all to talk about our profession, has the envy of the high employment rate. In fact, the unemployment rate in the country is about 6.7%, and the unemployment rate for web developers is less than 1%. And our wage levels are higher than average. The average annual revenue for software developers in 2012 was more than $90,000. Of course, if you are good enough now, you can go far beyond this number. Looking at the novice who followed me to learn to become an entry-level programmer, the heart has a great sense of personal accomplishment. And the pay of the job also made them happy: Starting salary from $45,000 to $70,000. So, compared with most of the other people, especially those who are mediocre in the job clock, because the job salary is not high and constantly job-hopping, software developers are still relatively successful. Here, allow me to take the liberty of making a generalization, if there is a similarity purely coincidental. It can be said that halfway decent programmers are relatively successful with these people. That is, the superiority of success paralyzed our nerves, so that we lack the motivation to accomplish the goal. The knowledge category is different from our extensive knowledge. We can be very talkative about how convenient travel is between several cities. We know how to break down a complex problem into small sub-problems. We are the true "world pass" because we can say "Hello worlds" in any language, and we do not frown, even when we need thousands of calculations, because we know how to push. We know a lot, but is it enough? The great scientist Albert Einstein once said: A dangerous astray, so dangerous, learned conceited, more dangerous. Newton, as we all know, hailed as one of the smartest people of the time, to accurately predict the movement of celestial bodies far from our million km. He said he was standing on the shoulders of giants to see farther. And physics is not his only interest, he also left us with calculus and so on valuable knowledge wealth。 So he should know more about capital and the workings of the market. 1-J6CUVYBQSCHXK-JLYLMALW haha, then you are wrong! At the peak of the 1720 South China Sea stock bubble, all the cash he put in was wiped out and then went bankrupt. Because he does not know the market, so even if his knowledge more profound, also can not help him a little busy. Because his field of knowledge is independent and irrelevant-he has discovered the laws of the movement of objects, but these laws do not help him to master investor psychology. We are also in this situation. We can spend a whole day explaining algorithms, studying data structures, but we don't know what users want. When Twitters first appeared, I took it for granted that it was just a fad. It turns out that I was wrong. When we are solving problems, we tend to pursue only the attraction of the solution, but ignore the secular view of connecting to the problem. Constant job-hopping I can assure you that this is true of any other major city, but here I represent only my own experience in working with my colleagues and friends in New York. We are constantly changing jobs. But not everyone is like that. I see some people have been working in the same position for 19 years in the comments on an article online. I also found that people who are easily attracted to other projects tend not to stay in the same position for too long. That's why many projects have to be interrupted. There are many reasons for interrupting a project. For example, just enter a new job, and need to concentrate on the project there, you have to put aside the original first. Another example, because this project and we have done before the possibility of similar, so suddenly lost interest. Distance is also one of the reasons, especially if you have to jump a few years to move, insist on more difficult. Here, I need to mention that changing mindset is important. If you are going to resign after three years, then why can't you take care of your project in 3 months? If you can keep this passion, when you helpless on the project, a good idea will come. To give birth to a premature project. For such a reason, I did not make my good idea "born". First we admit it, and then we find out why. Now the third step is to fix them. This is not overnight can be done, and probably my many projects will still be this half-dead state, and I thought for a long time, finally came up with a number of steps to avoid these items will always be the folder of the device. You're the best. First, understand that every project can make you a little--or, in some cases, a big one--to become a better developer. Technology needs to be built on time, so the more projects you develop, the better you will be. To learn new technology, new programming language, new framework for the power to develop a project, so even if you can not finish, you will be able to learn a lot of knowledge. And if you have other important things to do, you can immediately suspend the project. Building project components you have developed a lot of projects and become more and moreSkilled, do not know whether you know this little trick--code reuse? Build modules and libraries instead of having to write them again every time you need to use them. If the project you are working on is not the last one, then I would advise you to build some project components instead of writing the code that can only be used in this project. Write yourself a note in the document so it's convenient to use it next time. And we're working together. Now that we have a good way to regenerate those projects that have died, is it a temptation? Your idea may be subtle, like your baby, and maybe $ billions of, but so far-it's worthless. You need to share your ideas with others, and the more the better. This spontaneous excitement will motivate you to continue to work on this project and promote its development. You can even open the door and invite people to participate. This collaborative approach will give you a sense of mission, focus on it, and don't give up easily. Solve your problems don't be too ambitious, don't above his business, try to do something really useful to you. If you are a program developer, that solves the problem of the program, if you work in the company, that the production of the company need to use the program or whatever, even if you personally, there will be some technology to solve the problem. So why not start with a strong hand? Don't wait for the problem to accumulate, then to solve, step by step, at the same time you can also get some useful programs or something, why not? Do not be small but not for a saying, do not want to create a time limit of 8 months to run the company, the time can be in 4 weeks or even less can do things. No matter how simple, a fixed day of the month to release your latest results. Doing so will have a strong psychological implication and can motivate your work. On the contrary, if you sit in front of a notebook for 8 months to do an earth-shattering event, but there is no progress, how frustrating is conceivable. Quantitative change will lead to qualitative change, a small thing to do well may have great success. Because the journey of life is a marathon, not a sprint. Bragging is also a technology live social pressure is real, and instead of sneaking work, it's better to tell everyone about your work. The feedback you get will probably help you improve your product. Maybe you're worried that someone else will take your idea for yourself, but I can assure you it won't happen. Because even the very simple idea that other people want to carry out, it is also very difficult thing. So there's no need to be secretive. Speaking out, you can also extract meaningful improvements from your suggestions, and more importantly, this will motivate you to implement it. Otherwise the cowhide blows the face not to know where to put, haha. Writing here, to the finish, do not know if you have learned any tricks to help your project? Remember: Action is the most important. Free to receive the lamp brother even original PHP video tutorial CD/"Detailed PHP" Essentials version, details of the website customer service: http://www.Lampbrother.net
|