gosh.. PERL is really a hell of tuff codes... all those special patterns r killing mi..
my team (mi, upperstudy n team lead) has a meeting 2 days back. to decide how to modify a script so tat it can adjust to our new system. my lead said "dun worry, u r still new kid on the block.. dun expect u to fully understand the picture now.."
i felt re-assured.. at least i knw he understands it can b hard to understand the architecture.. n not think my progress is slow.. but i feel i'm... u know the reason..
BUT, jus now, during a training session wif client, my boss came beside mi, n ask how i was coping.. i said "ok lah.." she asked "u sure?" den i say "just the perl script is giving mi headache..." she then mentioned mi some mentors who i can look for if i got prob
after tis line, i begin to wonder.. if someone u employed is supposed to do a task (javva), but end up having to focus on another task (perl), n he's having prob wif it, is it better to find another person to take it up (bene here for almost 3 mths), or keep pushing him for the "another task"?
i wonder if, her line meant good.. ie if i got prob, i can look them up.. OR telling mi to buck up.. or else.. her tone is more to care n concern, not threatening or disappointed type
jus tat ,i can see for myself, for java stuff, i totally no prob. but for perl, i need to train real hard.. while i'm doing my asgt... sighzz
No comments:
Post a Comment