Why learn java?
First job, second job
First of all, as a java development staff, your level of ideological cognition must be engaged in, and the level of ideological cognition determines your professional skill level
JavaSE engineer B/S architecture ---- browser access server
Generally, when I first started learning, I used javase. I thought that doing java development is doing server-side, which is what everyone calls additions, deletions, revisions, and inspections, but this is only a requirement of a common code farmer.
Now there are specialized front-end engineers in the enterprise. In the early days of java development, there were no front-end engineers, and there were no so-called components and frameworks. Writing, adding, deleting, modifying and checking are all done in servlets to connect the database with the most traditional jdbc. Now with the Internet The development of technology has gradually separated the front and back ends. There are professional personnel at the front end and professional personnel at the back end.
Now the requirements for java development are getting lower and lower, because there are many mature components and plug-ins for everyone to use, and the things to learn are getting lower and lower, and even the underlying technology does not need to be mastered, just call these components and plug-ins to make them It is enough to form a complete project, so many java engineers are really good now,
I am one of them, so I have a deep understanding of it. Why do you want to learn the front-end, because the front-end does not know how to write to make the back-end development easier, and how to write to make the back-end more efficient. At this time, we need everyone to guide them, and we can guide them when we can. Others, when we want to develop to the management, to a higher level, but our thinking level is not enough, if there is an opportunity for you to lead a team, but you will only add, delete, modify and check the back-end, how to structure a complete project, how to lead A team develops a qualified product, because Java is originally based on the B/S architecture. If you are the technical director or architect of a team, you will not know this or that, and you will only call some interfaces and When building components, how to manage one of your own technical teams.
So we can't just limit ourselves to adding, deleting, modifying and checking a server, so don't position yourself as a code farmer at first, but position yourself as a project manager and a project director.