Komen kepada: Juru-Rancangan

Entry asal:

nih hape ke jadah la substring nih susah sangat nak compile. penat dah aku nak declare object tu function nih. run je laaa!!! selesai keje aku. demmit. sape nak keje mencabar wei? sila la email aku CV korang. aku dgn rela hati akan bagi experience yg bagus untuk korang.


read more...



Salam Cik Ururu,

As much as I would like to comment your whole web-log, or the Melayu-Islamic related entry dated Nov 23rd, or the contradicting entries between the one dated Nov 26th with Nov 30th, I picked the one that bored me most: this one. It's lame, it's degrading, and it's sure bring alot of memories, personally.

Some people like obstacles. They see it as challenges that makes them better at what they do. Obstacles gives them that special 'energy' after they get through it. It gives them the fix and kicks that keeps them ticking in the company. This kind of people are usually the muscle of a company. They rarely think but when they do, they couldn't stop until the problem is solved.

In the wonderful world of working life, we need to understand what we are being paid for, our strength and weaknesses, and the right moments to raise the white flag quickly if the work is beyond our capability or capacity. If the work is easy, our boss would get an intern to do it for them. If it's too hard, they'd hire a vendor and learn from it. Either ways, it's up to us the cooleee, to move the load and turn the task's status from red to yellow to green. One way or another.

From my limited experience in programming, the solution to your problem could be as simple as a 'misplaced commas' or 'unclosed brackets' or improperly defined objects in your subroutines. I couldn't give a specific solution as your entry did not describe specifically the 'error' found. I'd propose you try to understand the program flow by debugging it row by row until the point where the compiler found the error.


And no. Being an engineer is not as simple as you say it is. We have bigger things to solve than to entertain lazy, whiny programmers who are not detail enough while reading the manual. So we just give them short retorts like the one in your example to save OUR time.

Dahla kerja dok atas kerusi ajer, suruh baca buku manual pun pemalas, nak siapkan program pun nak mencarut-carut. Mai la dok bawah keta ni cari kat mana punca bacaan meter tu tak tepat kalau hero sangat.