355 reputation
110
bio website
location Manila, Philippines
age
visits member for 3 years, 4 months
seen Nov 20 at 1:48

8 years working as a Java Developer in Manila, Philippines; recently working secondarily as Ext JS Developer as well

linkedin

profile for Carlos Jaime C. De Leon on Stack Exchange, a network of free, community-driven Q&A sites


Apr
26
comment When is 'cloning', rather than reusing, a module acceptable design solution?
Both will reside in the same application release and CVS project unfortunately. Thanks for the suggestion though, it did not cross my mind, however its not applicable in our case sadly.
Apr
26
comment When is 'cloning', rather than reusing, a module acceptable design solution?
Unfortunately, I'm referring to cloning, because that would mean copy-pasting in order to decouple the new engine from the current engine. Decouple, because we do not want the current engine to be affected by any changes related to this new engine
Mar
19
comment Should devs, testers and business users have one unified test script?
When you say you use UAT test script from the start, does that mean it should come from the business user? I mean to say, the user has already created a test plan early at this stage and that this plan is accessible to the developer to use as part of his dev testing?
Mar
13
comment Is the 'Law of Demeter' applicable to public/API method signatures?
Thanks for your input. I agree about the encapsulating primitives in domain objects. However, just your point in Edit 2, you say its not disastrous to add a new 2nd signature, but that would mean code change to client code that now should pass 2 parameters instead of one. That 2nd point, I'm abit hesitant to agreed on...
Sep
7
comment When conducting a code review, should the focus be on the completeness of the requirement?
I agree with the redundancy being introduced!
Sep
7
comment Should you refactor existing code that is not broken in a project focused on new features?
You've read my mind! I was thinking exactly of that famous rule "don't fix it if it is not broken" to justify deferring the refactoring!
Sep
7
comment When conducting a code review, should the focus be on the completeness of the requirement?
I meant that the reviewer was chosen to conduct review due to his past involvement in the application at hand. He is not actively participating in the project other than code review.
Sep
7
comment When conducting a code review, should the focus be on the completeness of the requirement?
This is my sentiments exactly, committing more time to code review, which would mean adding more time to the project schedule. In turn the project will be lengthier if code review includes requirements completeness. Is it a normal practice then to not include requirements completeness in code review?