I have a been a java developer for over 10 years. Which I think is 3 life times in silicon valley. During that time I have worked on J2EE, EJB 1, 2, and 3. Spring Frameworks. Struts 1.0, 2.0. JSP. JMS. JMX, etc. etc. All the acronyms at some point.
At the beginning of 2015 I found that there are still a lot of java positions. Many of which want people with core java skills. Those skills are tied to:
1. core java
3. algorithms
If you know these 5 things, you can get any java programming job. And I think someone graduating from college that has actually learned what was in the classes taught by computer science departments, should do just fine. BUT! And there is a big BUT, actually having the knowledge, and being able to communicate that knowledge to an interviewer at Google is something different.
practice, practice, practice
The interview books that have 100’s of java examples is amazing. They really help. Also the new websites that teach you programming skills and have test areas on their sites is also very good.
javascript
Now knowing java, and knowing javascript I consider two totally different beasts. There is very little ‘java’ in javascript. The runtime environments are very different. The life cycle of objects in client and server are different. They have different design patterns. They have different ways of implementing OOAD, etc. From someone who has been paid for 10 years to write java, switching to javascript has a learning curve. Many enterprise developers may feel that it is a waste since only a small amount of code is being used.
But with node.js and angularJS becoming performant and fully supported by Google. You can have all your usual enterprise stack re-written using NoSQL (MongoDB), nodes, and AngularJS at the front end. And now with complete packaging such as meteor. You can go enter the next hackathon and kick ass over others attempting to use Spring boot, etc.
No comments:
Post a Comment