苍穹の駅

在TheServerSide上看到的文章，关于JVM的GC Tuning。
http://kirk.blog-city.com/advice_on_jvm_heap_tuning_dont_touch_that_dial.htm

作者对于这一话题的叙述比较详尽 (当然对于某个为了bt的项目死磕了一个月的人来说都是小case了)，

1. The mantra on performance tuning: Measure, don't guess
2. Tuning tools (JVM switch -verbose:gc, -Xloggc:logfile.name, tool such as HPJTune)
3. New feature in Java 1.6: GC ergonomics
4. Advanced GC Tuning: to deal with generational heap

我还是认为GC Tuning是JAVA程序优化的下下策, 在项目条件限制的时候才去使用. 很多时候通过修改设计和代码比调GC要有效率得多.

最近听多了MP3中的ACG歌曲，找了俄罗斯方块的OST听，发现Tetris的音乐果然还是经典。此外在整理M3-20的资源时发现一张不错的碟“東方クエスト完全版 Do you like famicom？”。音乐采用NES音效，模拟FC时代的音乐重新编曲的东方系列，光是封面就已经够怀旧了。

Nobody knows who I really am
I never felt this empty before
And if I ever need someone to come along,
Who's gonna comfort me, and keep me strong?
We are all rowing the boat of fate
The waves keep on coming and we can't escape
But if we ever get lost on our way
The waves would guide you through another day

As mentioned in a Blog, "any tool, technology, or information can be abused by evil people and misused by stupid ones", which I absolutely agree with. As my experiences on Trilogy Outsourcing Network for several months, some Service Types such as "Code Coverage" and "Refactoring", which only have metrics on coverage or MI, usually result in successful but useless deliveries. In one hand, the service definition doesn't give a good criteria and could be abused by the vendors; in another hand, even the project developers sometimes write useless test cases to achieve coverage metrics or waste time on doing low-quality refactoring.