I am finishing with my current company in two weeks time, and heading back to a company I worked at before. Things just did not work out where I currently am, the company is a little too small, and seem reluctant to change their processes more towards those of a software house. My obsessive compulsive tendencies towards quality, are not shared by anyone else in the company it seems. They are a little too obsessed with what is shiny in the world...
I am looking forward to working with the new team, several of whom I know well, and to the challenges in the department. I will be taking with me several tools from my tool box, including Wicket, Brix, Maven, but hope to leave behind in large part Java, which I am becoming increasingly disillusioned with. I feel the JVM is still the way forward, but in order to compete with trends and the evolution of other languages I need to ditch Java.
Currently it seems that Scala does much of what I need to do, and my next step may even be to use the features of the language itself to enable me to drop all of those frameworks that the inadequacies of Java forced me to use.
More information sometime soon...
Subscribe to:
Post Comments (Atom)
1 comment:
I agree. It will take several years and someone with a less academic mindset to come up with a simpler, easier to grasp, easier to read (i.e., linguistic versus notational) version of pretty much exactly what Scala does today. It's kindof sad because Scala is so good in so many ways, but from my perspective it is very much where SmallTalk was in the 1990s. Cool and incredibly effective... if only people would use it broadly (which they won't).
Post a Comment