Tiada. Kosong. Nil.

Slank - Ku Tak Bisa

Johnny has been making a fool out of himself for a couple of months now. Oh, yes, he is. The story begins on a one fine day, but slightly rainy towards the end. Johnny said to himself, “What if I have long hair? What will it be like?”. An interesting question he thought. From that day, he prevented himself from going to the barber as much as he could.

It’s been like 6 or 7 month now. His hair is actually not that long. But it’s just friggin ugly! He knows that. Everybody knows that. He even knows that everybody knows that. But he’s OK with it. Some people tell it directly to his face. Okay, maybe not that direct, kind of rhetoric kind of way, but yeah, like, “Awwh, dude, cut your friggin hair dude. It’s friggin ugly dude”. Some even called him names, from M. Rajoli to Steven Seagal, to that some French football player that he doesn’t even know of (or is it Italian?).

Some people talks behind him, with intentions that he’ll hear it. Yeah, of course he heard, he’s not deaf. But he’d just pretend like he’s got too much earwax blocking the sound waves from reaching his ear drums. He’d just stare to the monitor screen like he’d get fired if he don’t finish this friggin module by tonight. He’d just ignore it, like always. And he’s getting pretty good at it. He’s not angry. Annoyed maybe, but not angry.

Sometimes he just felt that he had enough. But usually, moments after that, certain challenges just came out of no where. Like, “Ah, I’ll wait till the boss said something”. Or even, “Oh what the heck, we’ll wait till the CEO said something”. Or even better, “Ah, I’ll wait till it got stuck on some heavy machinery or something, then I’ll cut it”.

That’s Johnny. It’s all just an experiment to him. Life is. You’ll never know if you don’t try. Seeing the reaction of people around him, that’s result for him, worthy to make a report on. With graph, and pie charts, and all.

But now Johnny thinks that he can’t take it anymore. Being thought as a fool has never been Johnny’s ambition. But parting with something that he had for 6 or 7 month is not that easy to do. He began to grown attached to it. Should he or should he not cut his hair? To help Johnny decide, you can vote via SMS! Key-in POTONG, followed by a <space>, and then YES, or NO.. or IDONTFCKINGCAREMUTHAFCKR. Send to 338696, extension 506.

Totally hillarious! BBC nak interview this some Guy Kewney guy, editor dari this some Newswireless.net site, pasal this some Apple music stuff or something, tapi diorang tersalah panggil orang lain. Seorang pemandu teksi. Encik tu boleh selamba kodok je jawab. Wahaha! Watch it.

Via boingboing.

Sekarang aku jarang berblog. Sebab sibuk. Dan bingung. Tak tahu apa nak dilakukan pada hidup aku. Err, sebenarnya aku tahu. Cuma aku malas. Dan bodoh. Haha. Ha. Pergi mampos lah kau. Haha. Oops. Sorry. Aku ngantuk. Mari tidur.

Aturcara adalah suatu karya seni (at least that’s what I think). Seperti seorang pengkarya, kita berbangga dgn hasil kerja kita, dan kita mudah marah bila orang kritik hasil kerja kita tu. Janganlah begitu, sayang. Jangan ego sangat okay… Jerry Weinberg (The Psychology of Computer Programming, 1971) mengusulkan amalan “Egoless Programming”, supaya kita dapat menerima teguran, dan dpt bekerja dgn orang lain dgn lebih baik.

Di bawah adalah The Ten Commandments of Egoless Programming.

1. Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry, so we can, and should, learn, laugh, and move on.
   
2. You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don’t take it personally when one is uncovered.
   
3. No matter how much “karate” you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.
   
4. Don’t rewrite code without consultation. There’s a fine line between “fixing code” and “rewriting code.” Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.
   
5. Treat people who know less than you with respect, deference, and patience. Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don’t reinforce this stereotype with anger and impatience.
   
6. The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought.
   
7. The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect-so if you want respect in an egoless environment, cultivate knowledge.
   
8. Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don’t take revenge or say, “I told you so” more than a few times at most, and don’t make your dearly departed idea a martyr or rallying cry.
   
9. Don’t be “the guy in the room.” Don’t be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.
   
10. Critique code instead of people - be kind to the coder, not to the code.As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.