peter_it

Monday, May 05, 2014

WASC Threat Classification

Sunday, May 04, 2014

Linda - 樂觀、人緣

陳振光 - 口才、自信

Wilson - 實力、親和

Sunday, April 13, 2014

又要供樓養家,所以要做決定呀,向左走向右走?

If you are confident that your current company still can run in future 1-2 years, you better stay with it. Why? It's because the nature of T-contract is solely determined by the funding of the government department (no matter it's recurring or project-based). No one can guarantee (don't trust the agent about 'normally you can get renewal).

And I guess your T-post on offer is something with vendor management, or technical support. Both are boring and tough jobs. 'Tough' does not mean 'long-working-hour'. But the nature of these jobs usually let you frustrated, compared to 'normal commercial firms'.

One thing you need to note. If you quit/discontinue a t-contract before the one terminates normally (maybe due to you are not happy with your agent/salary/whatsoever). You may be banned from re-application to another potential t-offer in 3 months.

So, do you still want to go for such job?

By GR193

Thursday, January 24, 2013

Assertion

An assertion is a declaration of a 'certain fact' about a subject, for example, a user or code.

Wednesday, November 07, 2012

名句

無話做唔到既，睇下你點design既遮

Wednesday, October 31, 2012

三十六計 in doing I.T. projects

From 1 Feb to now (31 Oct 2012)

勝戰計	1. 瞞天過海	2. 圍魏救趙	3. 借刀殺人	4. 以逸待勞	5. 趁火打劫	6. 聲東擊西
敵戰計	7. 無中生有	8. 暗渡陳倉	9. 隔岸觀火	10. 笑裏藏刀	11. 李代桃僵	12. 順手牽羊
攻戰計	13. 打草驚蛇	14. 借屍還魂	15. 調虎離山	16. 欲擒故縱	17. 拋磚引玉	18. 擒賊擒王
混戰計	19. 釜底抽薪	20. 渾水摸魚	21. 金蟬脫殼	22. 關門捉賊	23. 遠交近攻	24. 假道伐虢
並戰計	25. 偷梁換柱	26. 指桑罵槐	27. 假癡不癲	28. 上屋抽梯	29. 樹上開花	30. 反客為主
敗戰計	31. 美人計	32. 空城計	33 反間計	34 苦肉計	35 連環計	36 走為上計

Tuesday, October 09, 2012

Grails: The good, the bad, the ugly

http://schneide.wordpress.com/2011/04/05/grails-the-good-the-bad-the-ugly/

rails generates scaffolding source code for the groovy server pages, controller, and data access (crud). I see two issues with source code generation for teams.

1.) For production environments it is likely that you will modify these files outside of the grails generation engine, like calling java components directly.

2.) In multiple developer environments you will need a way to cause a regeneration of these scaffolding files each time a new change is checked in on a core source file. This is not automatic. You could probably handle this with your build, but you would have to manually add this to your build, and regenerate each time you changed one of the core source files.