theJavaJar.com

I have been a web developer for about 5 years now and I think I have been fighting the same problem over and over again. The problem isn’t with a technology or it isn’t a server or code issue that has been keeping me up at night. The problem that I have been running into is poor planning and management. I have worked with a few people, you know who you are, who truly know what is going on and how to get things done.

People expect that the terms “build a web site” or “build a web application” translates into a plan to complete a multi-tiered web application that integrates with their legacy environment. Some clients have asked for a simple web site with a newsletter maintenance application, content management system, and e-commerce piece that are branded and tailored to their unique business model that can be completed in about two weeks and cost under $2000 US.

I love what I do. Really I do. I just wish I could hurdle this problem every time I start a new project.

Well, maturity is something that comes with time and experience but I fear that JSF may not reach a mature status before the technology, as we know it, is dwarfed by something new. I have been working with JSF for over a year now and I like a lot about what it has or what it is trying to offer. There are a few things that stand out when T think of JSF but one things rings in my ears; binding. We are in a world where things are asynchronous, detached, and service oriented, yet JSF is still tied to the server for simple things that have been solved in the browser, or client, years ago. I think that JSF’s saving grace will come from a technology that extends what is there and makes a lot of the issues transparent to developers. I hear NetBeans is very helpful when it comes to JSF development and I have seen a presentation at the Tampa JUG showing how “nice” things can be. Well, maybe something will come along to make things better…Flex? JavaFX? GWT? Pick your poision.