Jop's Work - All Comments

re: Slow Start - Testaments and Books

cruizer — Fri, 05 Dec 2008 09:11:01 GMT

I am reminded of one article in Uncle Bob (Robert Martin)'s "The Craftsman" series, in which he said that it takes an abstraction leap to think in terms of objects and not primitive data types :)

re: Slow Start - Testaments and Books

lamia — Sat, 29 Nov 2008 02:40:18 GMT

Wow! Very professional ang approach!

Nahiya ako bigla sa sarili ko. Why wasn't I able to think of Testaments as objects? Galing, elibs ako! (applause)

re: Markdown Viewer

jop — Thu, 27 Nov 2008 21:06:13 GMT

hehe.. no pressure Keith. Happy Thanksgiving!

re: Markdown Viewer

keithrull — Thu, 27 Nov 2008 15:26:52 GMT

Hahah! Pasensiya na. Been busy the past few weeks. I'm going to do it over this Thanksgiving weekend mga bossing. ;)

re: Slow Start - Testaments and Books

keithrull — Thu, 27 Nov 2008 15:24:03 GMT

oo nga, nabitin ako! hehehe! keep it coming jop! :)

re: Slow Start - Testaments and Books

cruizer — Thu, 27 Nov 2008 10:08:41 GMT

ang bitin naman!!! he he...go go go master jop...

re: Markdown Viewer

cruizer — Thu, 27 Nov 2008 06:54:46 GMT

let's put the pressure on Keith! ha ha :P joke

re: I told you so.

jop — Tue, 11 Nov 2008 05:14:03 GMT

Great! Post your problems in the forums and I'll see how I can help.

re: I told you so.

lamia — Tue, 11 Nov 2008 02:51:01 GMT

Yeah, I'm thinking of putting it in practice on the next pet project that I would make.

re: I told you so.

cruizer — Thu, 06 Nov 2008 23:43:20 GMT

lamia may tawag dyan sa too much print/logging..."scroll-blindness" especially pag sobrang dami nang naka-log/print na entries.

better to move those things into an automated unit test ;)

re: I told you so.

jop — Thu, 06 Nov 2008 10:59:23 GMT

Lamia,

Unit testing shouldn't be as hard as writing those print statements - except that you are putting it out of the production code and into a separate method or procedure. Instead of visually checking the results of an operation by reading the output logs, you are writing your expectaions in code and letting the computer compare it to the actual results. I would have to say that testing is just like any other skill, it has to be practiced so you become good at it.

You also have to ask your team what really is the problem - is it the writing of the tests or understanding of the specs? If the tests are wrong, then I would bet that those who wrote the test did not really understand the specs.

re: I told you so.

Lamia — Thu, 06 Nov 2008 10:09:09 GMT

Hi Jop, Lamia here

Maybe I'm still in your old situation. Still inexperienced about the said topic.

I have this TL who writes unit tests for his data access codes and sometimes would boast I already tested this and that using my unit tests.

But then, when we use his code we find out that there are things missing and some of them still not working. We are in very critical stage of development and I always thought that if he had time writing those unit tests, he had time to write what we really needed instead. He spent so much time on those tests but we didn't really move forward.

I guess what I'm saying here is that it's not only important to see that your unit test returned a pass status(sorry for the noob statement), you have to make sure it behaves correctly.

I'm still finding my plain old print on the standard out or log, testing in debug mode more effective than my TL'S unit testing strategy. Atleast during this time.

re: I told you so.

giniedpooh — Wed, 05 Nov 2008 22:47:03 GMT

Yes, it's truely beneficial having a Unit Test. ^_^ From my previous experience as System Admin to Business Analyst and now I'm into Testing which I have to find valid bugs or defects from the system before deployment haha 'BUGS' lagot kayo..

re: How to use Patterns

lamia — Tue, 31 Jul 2007 05:05:41 GMT

When I was starting with Design Patterns I was quick to indentify which I'm gonna need and which is not. Refactoring to patterns is a nice idea I learned from cruizer (I'm referring to the idea, not the book). However, you could use Design Patterns in situations that seem very familiar to you(and assuming you've done something ugly to solve this situation before).

re: How to use Patterns

cruizer — Mon, 30 Jul 2007 21:04:09 GMT

i agree. refactor to patterns. otherwise you might end up with YAGNI.