I am currently developing PHP. Although this is the best language in the world, I recently like Python. Is it worthwhile in the long run? Thank you for analyzing the learning curve and employment! I am currently developing PHP. Although this is the best language in the world, I recently like Python. Is it worthwhile in the long run? Thank you for analyzing the learning curve and employment! Reply content: To be honest, I cannot understand every time I see similar questions. Why does a programmer use language as the division or boundary of his profession? Shouldn't programmers be classified by technology? You can say that you are an Android programmer and an iOS programmer. you can say that you are a background programmer, a front-end programmer, and you can say that you are an AI programmer and a graphics programmer. However, I can't imagine C ++ programmers or Java programmers in any way? Language is just a tool. changing a language is nothing that needs to be learned. If you think it is difficult to switch a language, it only means that your programming language has not been learned yet, or it is hard to remember when you are too old. = You need to add basic knowledge.
Here
There was a senior who began to write programs in 1997, and the 40-year-old middle-aged and elderly programmers started to develop programs. Let's look at his career: his first job was to write ASP on a Pentium II server. The first programming language is VBScript (many new users may have never heard of it ). The front end will also write a little JavaScript. In the next 6776 days, the "technology" that this predecessor used included VBScript, JavaScript, Linux, SQL, HTML, Makefiles, and Node. js, CSS, XML ,. NET, YAML, Podfiles, JSON, Markdown, PHP, Windows, Doxygen, C #, Visual Basic, Visual Basic. NET, Java, Socket. io, Ruby, unit tests, Python, shell scripts, C ++, Objective-C, batch files, and the latest Swift. Over the past 20 years, there have been countless technological trends 」:
In 1997 it was CORBA& RUP.
In 2000 it was SOAP& XML.
In 2003 it was Model Driven ArchitectureAnd Software Factories.
In 2006 it was Semantic WebAnd OLPC.
In 2009 it was Augmented Reality. (Yes, you are not mistaken. it will be more realistic in)
In 2012 it was Big Data.
In 2015... Virtual Reality? Bots?
What are employment prospects? Can you eat it? At this time, you might as well look at the Technical history. At the same time, what programmers do you think this predecessor is? VBScript program ape? Or a Python program? He spent 10 years in the Microsoft technology stack and 9 years in the Apple technology stack. It is roughly the route from Internet front-end to mobile development. If every time he comes into contact with new technologies, he will spend the same time as you do. it is estimated that his career has long ended when VBScript notebook is gone. There is something called a technical reserve. it may take some time to study if you are interested, but in the long run, there is no harm. It's just a language. it's nothing to worry about when the game front-end suddenly needs to be changed to distributed server-side development for 10 years. From the perspective of short-term economic benefits, if you give up the PHP job and switch to Python, although the starting salary may be higher, it is even harder to find a job. Second, Python is widely used in China, basically not relying on Python itself to earn money. PHP is more inclined to rely on PHP itself for code work.
In fact, the simple syntax and self-consistency logic of Python allow you to work with it in just a few days on the premise of any OO language, based on the features that we mentioned earlier, most Python jobs do not rely on Python knowledge, which makes it easy to ignore the time cost of converting a basic person to Python.
So it's good to learn Python. "Give Up" to learn Python ...... Not at all.
----------------------------------
Then again, I 've written too much Py, but I really don't want to touch PHP; I 've written too much PHP, and I really want to resign ...... If you can ask such a question, don't turn it around.
-- How hard is it to learn more languages?
1. I have seen many programmers who claim to be Java programmers, C ++, and PHP programmers. The only reason is that programming has not been learned (the solution to the problem has not been learned ). I learned a lot of syntax.
2. the language is just a tool and focus on solving the problem.
3. programmers always need to learn and master multiple programming syntaxes. Learning is certainly beneficial.
4. many people pay special attention to the results rather than the process. The process has worked hard, and the result will naturally come.
I started to learn python at the age of 41. I gave up using C and C # for more than a decade #
Because I started my own business, I cannot afford a large team. Language is only a tool for the vast majority of programmers. Unfortunately, many programmers regard it as a belief... 27 years old asked this question... Don't turn the language. just try whatever you like. you will find that it's almost the same in the end.
The core of programming is never in syntax.
Just like what language do you want to write as a writer in? It may be a little important, but it is definitely not the most important. a good writer asks him to write in a foreign language. he has studied for a while, turning the dictionary is better than writing a word that is familiar with this language but has poor literary accomplishment (although it may be a little grammar-free)
The essence of programming is similar to composing. As for whether you use piano or guitar (of course, guitar is easier than piano but less expressive), it is not the talent market for so important programmers for some reason, A large part is divided by programming languages, and even the price is high or low. The programmer group itself is the supply side and is not yet powerful enough to change this situation.
However, there is no reference for the programmer's career planning. what matters more to the programmer is basic skills, domain knowledge, and further soft power. You cannot bind yourself to a certain programming language-even if you improve your programming language capabilities, it is actually in the three directions I mentioned.
Of course, if you are a beginner, you should first be familiar with a programming language.
In the end, we also hope that the market will become more mature and have more appropriate division rules for the programmer group, so that there will be less senior "a language" senior engineer with eight years of experience. All languages must be mastered in the 21st century.
A superior programmer should not be familiar with a new language for more than three days.
This is the instinct in the programmer's genes.
