Official Google Blog: "This site may harm your computer" on every search result?!?!
http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html

If you did a Google search between 6:30 a.m. PST and 7:25 a.m. PST this morning, you likely saw that the message "This site may harm your computer" accompanied each and every search result. This was clearly an error, and we are very sorry for the inconvenience caused to our users.

Well that explains that...

"If you did a Google search between 6:30 a.m. PST and 7:25 a.m. PST this morning, you likely saw that the message "This site may harm your computer" accompanied each and every search result. This was clearly an error, and we are very sorry for the inconvenience caused to our users. What happened? Very simply, human error" bit worrying really

A web application or a software development process always has bugs which is very normal in a hundreds of lines of code. The important part is tracking & fixing them. Whether you are a one-person-army or have teammates, it is a big time-saver to use a bug tracking software. Besides having the bugs listed in a comprehensive way, most bug/issue tracking applications let end-users to submit bug-feature requests that will end up in a better product. Here are 9 free & open source bug tracking softwares, both desktop & web-based, for a better development process:

ありがとうございます。

The best strategy for dealing with Internet Explorer 6 is not to support it. Stop. Ok, I feel your frustration. You're a web developer and you're ready to tear your hair out because you have to support Internet Explorer 6, but, to put it tactfully, IE6 doesn't support you. You've spent hours on it, but you just can't seem to get your layout right. I can empathize. I can also help.

Most Common IE Bugs and How to Fix Them

Internet Explorer - the bane of most web developers' existence. Up to 60% of your development can be wasted just trying to squash out IE specific bugs which

9 Most Common IE Bugs and How to Fix Them - Nettuts+

Could not reproduce

"Can't and shouldn't."

Bug resolution. Hilarious!

アジャイルではない。チケットの粒度は一週間というのは大きく感じる。もちろん案件の規模間に左右されるのだろうけど。フリーのJIRA。エンタープライズにはもういくばくかの機能が足

James Hopkins’ compiled list of IE8 bugs and test cases. This should be something which Microsoft itself keeps public track on.

There aren't many articles covering incompatibilities, or CSS differences in Firefox alone — and for good reason. Firefox has always done an excellent

By http://bit.ly/Tweets2Delicious

Good article on Firefox CSS bugs

(This is old, just saving it for later.)

execute *every* SMS as root... so handy

"when the phone booted it started up a command shell as root and sent every keystroke you ever typed on the keyboard from then on to that shell."

Content Type: text/html; charset=UTF-8

interesting gphone bug

Don't tell me they thought of that as being a feature...

Interesting hack around the secrecy surrounding Apple's bug tracking system. Allows developers to log bugs publicly where other developers can see them, vote them up etc, yet still interact with Radar as needed.

Community bug reports on OS X and iPhone

A while back, I was hoping someone would create a quasi bug report system for closed proprietary products, and have input from the external community to centralize all issues. I've found it.

Tracks bugs reported to Apple by the development community in an open fashion.

An open version of Apple's bug tracking system.

そんなころころ新しいバグ見つかるもんなんかなあ。mozillaには何度かバグ報告した記憶があるけど、印刷周りとかだったような

開発版を使ってバグレポートもちゃんとしましょうという話。

Web 開発者の圧倒的多数は、一度もブラウザベンダにバグ報告を登録したことがないばかりか、ブラウザのナイトリー版を使ったことさえありません。これは恥じるべきことです。考えてみれば、ブラウザの何が異常かを評価するのに、ブラウザでの開発に日々を費やす人ほどその資格がある人というのはほとんどいないのです。 ブラウザのバグを登録せず、ナイトリーでのテストもしないプロの開発者を見たとき、私は特に驚きました。ほとんどの開発者の主な仕事のひとつに、クロスブラウザの問題を取り繕うことがあります。よって、バグの数を減らす (そして仕事を劇的に単純化する) ことは最優先事項になります。 私は個人的に全主要ブラウザベンダにバグ報告を登録してきて、良い報告を生み出すいくつかの特徴に気づきました。

被害を被るのだから積極的にバグ報告しましょうという話。

You've got to hand it to Facebook. They certainly know how to do security -- not. Today I was tipped off that there ...