4 ms·

Overtime, its not the language you code that matters. Application architecture, design, database skills etc do. All this comes from experience, building large a

by arunitc 13y ago

Overtime, its not the language you code that matters. Application architecture, design, database skills etc do. All this comes from experience, building large applications. I understand you may not have the opportunity in your current company to build those. You can start building small projects in your personal time. You are just 1.5 years in the industry. Taking such risks early is not advisable. Don't be impatient, keep learning. For example, you can redesign and build the 10 year old sites in a new language or in Java itself.

GeorgeMac 13y ago
It's interesting you say that! I have considered at least re building our demo product in Rails. Maybe this is a chance to at least show off to my own company that RoR would provide us with less headaches. I also completely agree about the patience side of things. I think my patience wore a bit thin today. I think I just thought I would use HN to vent my anger! haha. Thank you for the advice! Cheers
- tostitos1979 13y ago
  You may also want to consider newer web dev technology on the JVM. My background ... did Java EE when it first came out. Went to grad school. Did lots of python and rapid web dev for projects. Was forced to use Java in current gig. First, I hated it. Then, I realized it is a bit complicated. Some parts of Java are crap. If you use Java 7, some of those headaches go away. Also, I learned about different web dev frameworks on top of Java (Spring MVC, Play! framework). These make a big difference in my opinion. Finally, there are JVM-based technologies that get you into the "modern" era: Scala and Groovy. My team used groovy like Java and it was a mess. We ended up giving up on a large code base that we developed in Groovy because it was declared as unmaintainable. I came in on this team towards the tail end of the end of groovy days and am glad. Anyways ... long story short, Java is not going away any day soon.

by arunitc 13y ago

GeorgeMac 13y ago

It's interesting you say that! I have considered at least re building our demo product in Rails. Maybe this is a chance to at least show off to my own company that RoR would provide us with less headaches. I also completely agree about the patience side of things. I think my patience wore a bit thin today. I think I just thought I would use HN to vent my anger! haha. Thank you for the advice! Cheers

tostitos1979 13y ago
You may also want to consider newer web dev technology on the JVM. My background ... did Java EE when it first came out. Went to grad school. Did lots of python and rapid web dev for projects. Was forced to use Java in current gig. First, I hated it. Then, I realized it is a bit complicated. Some parts of Java are crap. If you use Java 7, some of those headaches go away. Also, I learned about different web dev frameworks on top of Java (Spring MVC, Play! framework). These make a big difference in my opinion. Finally, there are JVM-based technologies that get you into the "modern" era: Scala and Groovy. My team used groovy like Java and it was a mess. We ended up giving up on a large code base that we developed in Groovy because it was declared as unmaintainable. I came in on this team towards the tail end of the end of groovy days and am glad. Anyways ... long story short, Java is not going away any day soon.