For some reason, Mozilla works far better on Windows than it does on Linux for me. I have Mandrake 8.0 at home, and everytime I try to install on Linux, I can never get the JRE plugin to work.
As a developer who has worked with eXtreme Programming, I believe it to be a superior methodology for several reasons.
1) Paired programming facilitates extensiveknowledge transfer between senior and junior programmers.
2) Iterative development allows clients to be more involved in the process, allowing them to make critical changes earlier on in the process.
3) Only the components of the program specifically requested are encorporated into each iteration. Features not required for a particular iteration are not included at all.
4) Rigourous unit testing allows code to be consistently well-maintained.
5) Functional testing is also greatly emphasised.
6) Rigid, inflexible architectures are not allowed.
I would encourage any IT manager on Slashdot to use this methodology for any small IT project. I truly believe it to be superior as long as the project is not too large in scope.
For furher information, visit:
http://extremeprogramming.org/
-Java Cowboy
As a consultant/developer who codes in Java, I have found serlvets to be far more useful and flexible than JSP's. With servlets, it is easy to separate the HTML from the servlet code. All the front-end HTML designers need to do is add tags. The servlet can then add content to the web pages by replacing the tags as the servlet is running.
With JSP's, the code and HTML are mixed together, creating a gigantic mess. The HTML designers and the JSP coders are constantly stepping on each other's toes. Furthermore, it makes debugging an absolute nightmare. How is someone new to the JSP page going to make ANY sense whatsoever of the garbled mess of HTML and JSP code?
It would be far better to use servlets that point to special tags on the HTML pages. In this way, it makes task delegation between the web page designers and the coders all that much easier.
Slashdot Mirror
For some reason, Mozilla works far better on Windows than it does on Linux for me. I have Mandrake 8.0 at home, and everytime I try to install on Linux, I can never get the JRE plugin to work.
As a developer who has worked with eXtreme Programming, I believe it to be a superior methodology for several reasons. 1) Paired programming facilitates extensiveknowledge transfer between senior and junior programmers. 2) Iterative development allows clients to be more involved in the process, allowing them to make critical changes earlier on in the process. 3) Only the components of the program specifically requested are encorporated into each iteration. Features not required for a particular iteration are not included at all. 4) Rigourous unit testing allows code to be consistently well-maintained. 5) Functional testing is also greatly emphasised. 6) Rigid, inflexible architectures are not allowed. I would encourage any IT manager on Slashdot to use this methodology for any small IT project. I truly believe it to be superior as long as the project is not too large in scope. For furher information, visit: http://extremeprogramming.org/ -Java Cowboy
As a consultant/developer who codes in Java, I have found serlvets to be far more useful and flexible than JSP's. With servlets, it is easy to separate the HTML from the servlet code. All the front-end HTML designers need to do is add tags. The servlet can then add content to the web pages by replacing the tags as the servlet is running. With JSP's, the code and HTML are mixed together, creating a gigantic mess. The HTML designers and the JSP coders are constantly stepping on each other's toes. Furthermore, it makes debugging an absolute nightmare. How is someone new to the JSP page going to make ANY sense whatsoever of the garbled mess of HTML and JSP code? It would be far better to use servlets that point to special tags on the HTML pages. In this way, it makes task delegation between the web page designers and the coders all that much easier.