The Spider of Doom

If you develop web application, how do you perform validations? Most developers I know will use client side JavaScript to do it and assume that the data will be correct when it reach the server. If you are doing that, have a look at this article from TheDailyWTF which explains the horror that happens when you take things for granted. Client side JavaScript is not reliable and will never be reliable. It only allow more conveniences to the user. However, there might still be some people who will argue and state that their application is not web application but is intranet application, so they can be assured that the users will be enabling their JavaScript. I immediately gave up debating when I hear this.

Brokeback Mountain - Christian Edition

Spoon Fit test drive in Japan

Test drives of Spoon Fit and modified Aria sedan.

Gangguan bekalan air akan berlaku di beberapa kawasan di wilayah Kuala Lumpur dan Selangor 1/3/2006-9/3/2006

Kuala Lumpur - Gangguan bekalan air akan berlaku di kawasan-kawasan di wilayah Kuala Lumpur dan Selangor yang disebabkan oleh kerja-kerja pembersihan kolam/tangki air seperti berikut:- 1) Tarikh gangguan : 2 Mac 2006 (Khamis), dari jam 9.30 pagi - 9.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan seksyen 5,6,7,8,9,10 dan 52 (PJ State), Vista Angkasa, Perumahan Rumah Pangsa PKNS Kg. Kerinchi, Mid Valley dan Petaling Height 2) Tarikh gangguan : 2 Mac 2006 (Khamis), dari jam 9.30 pagi - 12.30 tengah malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan Perumahan Taman Sri Putra 3) Tarikh gangguan : 2 Mac 2006 (Khamis), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Taman Halaman Kesuma 4) Tarikh gangguan : 3 Mac 2006 (Jumaat), dari jam 9.00 malam - 5.00 pagi (4 Mac). Wilayah : Hulu Selangor Kawasan yang terlibat : Keseluruhan Bandar Rawang Jaya, Sungai Choh 5) Tarikh gangguan : 3 Mac 2006 (Jumaat), dari jam 9.30 pagi - 11.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan kawasan Taman Bukit Subang 6) Tarikh gangguan : 3 Mac 2006 (Jumaat), dari jam 9.30 pagi - 9.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan kawasan Bandar Puchong Utama 7) Tarikh gangguan : 4 Mac 2006 (Sabtu), dari jam 10.00 malam - 10.00 pagi (5 Mac). Wilayah : Klang Kawasan yang terlibat : Keseluruhan Jalan Kebun, Taman Berjaya, Jalan Istana, Istana Alam Shah, Pejabat Daerah Klang, Pejabat MPK, Pejabat SYABAS, Bukit Tinggi, Taman Botanic, Kampung Pulau Indah, Kawasan Perindustrian Pulau Indah Fasa 1&2, West Port Terminal, Star Cruise, Telok Gong dan Kota Permai. Wilayah : Kuala Langat Kawasan yang terlibat : Sijangkang, Batu 9 kebun Baru, Batu 10 Kebun Baru, Telok Panglima Garang (termasuk kawasan industri) Bukit Komandol dan Pulau Carey 8) Tarikh gangguan : 5 Mac 2006 (Ahad), dari jam 9.30 pagi - 9.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan kawasan Perindustrian S.B Jaya, Sg Buluh 9) Tarikh gangguan : 6 Mac 2006 (Isnin), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Sri Rampai, Setapak Jaya, Setapak Permai, Kg. Pasir Wardiburn, Kg. Loke Yew dan Flat DBKL 10) Tarikh gangguan : 6 Mac 2006 (Isnin), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Taman Setiawangsa 11) Tarikh gangguan : 7 Mac 2006 (Selasa), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan kawasan Kondo Rustika 12) Tarikh gangguan : 7 Mac 2006 (Selasa), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Sri Gombak Fasa 8,9,10,11,12 dan Kampung Melayu Sri Gombak 13) Tarikh gangguan : 8 Mac 2006 (Rabu), dari jam 9.30 pagi - 9.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan kawasan Bukit Serdang (Permata). 14) Tarikh gangguan : 8 Mac 2006 (Rabu), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Desa Aman Puri dan Wangsa Permai. 15) Tarikh gangguan : 8 Mac 2006 (Rabu), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan Taman Wangsa Ukay, Bukit Utama, Taman Bukit Jaya, Super Home, Jalan Wangsa 5A, Apartment Atheneum, Bukit Antarabangsa dan Kampung Sungai Sering. 16) Tarikh gangguan : 9 Mac 2006 (Khamis), dari jam 9.30 pagi - 12.30 malam. Wilayah : Petaling Kawasan yang terlibat : Keseluruhan kawasan Damansara Damai 17) Tarikh gangguan : 9 Mac 2006 (Khamis), dari jam 9.00 pagi - 9.00 malam. Wilayah : Gombak Kawasan yang terlibat : Keseluruhan sepanjang Jalan Hulu Klang Segala kesulitan amatlah dikesali. Para pengguna dinasihatkan agar menyimpan bekalan air secukupnya serta menggunakan air secara berhemah sepanjang tempoh gangguan tersebut. Sebarang pertanyaan atau aduan sila hubungi Pusat Perkhidmatan Pelanggan (PUSPEL) menerusi talian bebas tol 1-800-88-5252 atau melalui sistem pesanan ringkas, s-m-s dengan menaip PUSPEL jarak taipkan aduan atau pertanyaan hantar ke 39222 atau lawati laman web SYABAS di www.syabas.com.my untuk maklumat lanjut. Sekian, harap maklum. NAEMUDDIN ABDULLAH Pengarah Eksekutif, Komunikasi Korporat & Perkhidmatan Pelanggan Sumber Berita Dari : Shima, Eksekutif Perhubungan Media

Google Video

Google Video launched a new feature which allows us to embed video on our sites. So, here's a test to see how the video is embedded. Enjoy the teaser.

Would You Take A Paycut for More Interesting Work?

There is an interesting debate on whether would you take a paycut for more interesting work? in slashdot. There is one funny guy who replied he would take a paycut for a more knowledgeable manager. I wonder how many of us would want to do that too sometimes during work. Anyway, I think it is not worth it to take a paycut for more interesting work, unless the compensation at the end of the day is worth it. If you feel your work is not interesting enough, why? Speak to your manager, collegues and try to make it more interesting. However, this is easier said than done.

Atomic transaction in J2EE

As budding developers, most of us tend to debate on certain technologies out there and comment on which is better than which and why. dotNet developers will argue that J2EE is so hard to use while the latter will comment that dotNet does not scale and is not as reliable. Even within the J2EE environment, some developers does not see EJB as a useful feature of J2EE and comment that it is difficult to develop and the same results can be achieved merely by using JDBC. There are even others who said that using stored procedures will result in most efficient code. Efficient here means fastest to execute and return desired results. As I am also one of the budding developers, I also face this type of debates most of the time. I still does not know which one is most efficient and which one should I use in which type of situation. However, I does realize the fact that session beans and entity beans removed a lot of the headache of maintaining transactions in JDBC environment. Container managed transaction is a blessing for Java developers. Anyway, the point is, I actually like to find out WHAT IF the transaction that is guaranteed by the container fails. I mean, say the task A and task B must occur as one atomic transaction but actually only task A managed to run but the transaction is unable to roll it back or worst, does not even realized it. Who would be responsible for this behavior? Most of the time it would be developers fault for not understanding the J2EE spec correctly and made mistakes while developing, however one cannot simply rule out that the application server vendor is not at fault. What if this funny behavior is randomly appearing at production systems and the developers are sure that their application are coded correctly. Who are liable for financial lost that occurred because of application servers funny inconsistent behavior?