It's my first online course and I'm so excited to get the certificate!
Wednesday, July 18, 2007
Sunday, July 15, 2007
Saturday, July 14, 2007
Free "Web Services and SOA Programming" online course
The 3rd session of the "Web Services and SOA Programming" online course
starts from August 24th. The topics of the course can be seen from the
following link:
http://www.javapassion.com/webservices/index.html#Topics
This new session will have heavy emphasis on the following 4 technology
areas.
* New Java APIs for Web Services (JAX-WS, JAXB, REST)
* WSIT (Project Tango)
* SOA Technologies (BPEL, JBI, Open ESB)
* GlassFish (Java EE 5, JBI runtime, Service Engines)
For the Hands-on labs, the "out of the box" support of above
technologies by NetBeans 6.0
(both in terms of designer tool and runtime) will be heavily leveraged.
* XML Schema editor
* WSDL editor
* BPEL designer
* CASA
If you know anybody who might be interested in taking this free course,
please let them know. In order to register for this course, all you
have to do
is sending a blank email to the following course subscription alias.
webservicesprogramming-subscribe@googlegroups.com
starts from August 24th. The topics of the course can be seen from the
following link:
http://www.javapassion.com
This new session will have heavy emphasis on the following 4 technology
areas.
* New Java APIs for Web Services (JAX-WS, JAXB, REST)
* WSIT (Project Tango)
* SOA Technologies (BPEL, JBI, Open ESB)
* GlassFish (Java EE 5, JBI runtime, Service Engines)
For the Hands-on labs, the "out of the box" support of above
technologies by NetBeans 6.0
(both in terms of designer tool and runtime) will be heavily leveraged.
* XML Schema editor
* WSDL editor
* BPEL designer
* CASA
If you know anybody who might be interested in taking this free course,
please let them know. In order to register for this course, all you
have to do
is sending a blank email to the following course subscription alias.
webservicesprogramming-subscri
Sunday, July 8, 2007
Minimart project: Lessons learnt
After doing the minimart project, I've compiled lessons learnt:
-Be precise about the scope of the project.
Make sure the customer understand what will the result of the project. This serve as the checklist to determine that you have completed the project. If you miss this, customers can suggest more features and your project grows. You will feel that the project has no end.
-Use prototype
What you have done especially user interfaces may be different from what customers expected. Making prototypes for customers to review can reveal the different and can save you lots of time. You can further understand customers' need or capture details customers missed at analysis phase. It can also satisfy customers to a larger extend.
-Backing up
Before making changes, make sure you have backed up everything including database.
-Fixing bugs
When customers find bugs in your program, they will call you. Instead of fixing it at customers' place, note down bugs' information, go back to the company and analyze the dependency of what you change. This is to ensure that what you change will not break other codes. If you have used Unit Test in your program, it'll tell you whether your change will break other codes.
-Be precise about the scope of the project.
Make sure the customer understand what will the result of the project. This serve as the checklist to determine that you have completed the project. If you miss this, customers can suggest more features and your project grows. You will feel that the project has no end.
-Use prototype
What you have done especially user interfaces may be different from what customers expected. Making prototypes for customers to review can reveal the different and can save you lots of time. You can further understand customers' need or capture details customers missed at analysis phase. It can also satisfy customers to a larger extend.
-Backing up
Before making changes, make sure you have backed up everything including database.
-Fixing bugs
When customers find bugs in your program, they will call you. Instead of fixing it at customers' place, note down bugs' information, go back to the company and analyze the dependency of what you change. This is to ensure that what you change will not break other codes. If you have used Unit Test in your program, it'll tell you whether your change will break other codes.
Monday, July 2, 2007
The pain of a wrong decision
Here I'm proudly present to you my pain of a wrong decision, MS.Access.
It's the "Focus"!
Most VB or Access programmers would know what I mean here. If you use Got_Focus and Lost_Focus a lot, you will end up losing control of the flow as the code grows larger. The most painful headache we had was in the receipt form where we were trying to sync between Riel and US Dollar.
No OO.
If you are happy with the benefit of Object Oriented, you will cry with Access(2003). No encapsulation, no code reduce, no inheritance, no polymorphisms, and the list goes on. When our project grows to a certain point, we started to feel the beginning of the hell where code disorders is the curse.
We wished we had chosen the OO language such as VB.Net or Java.
It's the "Focus"!
Most VB or Access programmers would know what I mean here. If you use Got_Focus and Lost_Focus a lot, you will end up losing control of the flow as the code grows larger. The most painful headache we had was in the receipt form where we were trying to sync between Riel and US Dollar.
No OO.
If you are happy with the benefit of Object Oriented, you will cry with Access(2003). No encapsulation, no code reduce, no inheritance, no polymorphisms, and the list goes on. When our project grows to a certain point, we started to feel the beginning of the hell where code disorders is the curse.
We wished we had chosen the OO language such as VB.Net or Java.
Subscribe to:
Posts (Atom)
