2006年4月18日 星期二

[軟體工程] 軟體超人X光眼:專案開發揭弊大爆料 (獨孤木 著)



軟體超人X光眼:專案開發揭弊大爆料

作 者:獨孤木


出版社:全球華文


出版日期:2006 年 03 月 01 日


-----------------------------------------------------------
內容簡介

  軟體界也要爆料!萬能的軟體超人有一副X光眼,專門針對軟體開發業界展開爆料大行動!為什麼軟體工程師們總是在加班,加到天昏地暗、六親不認?你以為他們願意啊??!!總是說「竹科新貴」,然而,軟體工程師真的好當嗎?藉由軟體超人的X光眼,揭發專案開發不為人知的弊病你將會知道,為什麼軟體工程師總是哀鴻遍野,為什麼總是找不到老婆!身為竹科新貴的你不可不看,身為普通人的你更該知道,這個業界,到底有多麼神奇。
  讓萬能的軟體超人告訴你,開發軟體這回事,有多麼荒謬的情節每天理所當然的上演著。


Story1 籌備專案?錯誤+人間地獄的開始
Story2 專案製造工程?超人也會死得很慘
Story3 測試階段?品質?賃北聽不懂
Story 4 Delay、Delay、Delay
Story5 結案之後?你以為完工了?哈!

作者簡介
獨孤木
  台灣大學資訊工程系畢業根據他的說法,從他開始工作以來,除了中間花了一年到南部開補習班追老婆之外,好像就一直待在軟體產業。他曾經待過銀行、網路書店、軟體公司。是個到處流浪的貧窮上班族,對於系統分析與專案管理,他有他自己的心得與看法。
  目前他自己創設了一家網路公司,專門開發一些沒有人做過的軟體。他外表看起來是個很沉默的人,不過坐在電腦前面可是無比的多話。想法很多,也很獨特,是個聯想力很豐富的軟體怪傑。連他開發出來的產品都很奇怪。第一個產品叫做幹圖王,光看這種名字就知道他是個多麼特立獨行的人。這項產品是個專門在網路上抓取資料的機器人。有興趣的人可以到
http://www.phopicking.com一探究竟。

ps : 獨孤木(Bruce) 就是我上一家公司ㄉ老大啦!


2006年4月16日 星期日

[電影]《耶穌受難記》The Passion of The Christ

梅爾吉普遜導的「The Passion of The Christ」,

台灣翻作「受難記——最後的激情」,
Start Movies 今晚播出 ...

梅爾吉勃遜的《耶穌受難記》擺明以宗教片之姿大剌剌向觀眾傳教。此片一出,馬上引來各界的關注、撻伐及褒揚。從二月底美國檔期持續延燒至復活節,至今已開出三億多美金的票房佳績;然而,這樣的票房背後到底透露出什麼訊息?紛爭不斷的電影,到底反映了什麼爭議?



... ... ... more ... ... ...

有興趣的可以參考 http://life.fhl.net/Movies/issue/taiho.htm ^^

.End.

2006年4月9日 星期日

[電影] 十面埋伏


「北方有佳人,絕世而獨立,
   一顧傾人城,再顧傾人國。
      寧不知,傾城與傾國,佳人難再得。」

2006年4月6日 星期四

[EE_CSIE] Embedded System Design Project

Embedded System Design Project 國立交通大學‧電機與資訊學院碩士班‧94-2 嵌入式系統設計

■ Problem Statement : Your company delivered a Windows-based application system to customers. Suppose that there are five tasks in the system, and three of them are more urgent than the other two. Let there be only three priority levels (i.e., H -> M -> L) available in Windows. As a compromise, you decided to give priority H to the three urgent tasks and priority M to the other two tasks. Priority L is left unused. The above arrangement seems working fine. But one day your customer complained that your system usually exhibit poor performance. After some investigation, you found that the three tasks with priority H sometimes won’t give up the CPU for a very long period of time. As a result, those two tasks with priority M have no chance to be serviced by the CPU unless those tasks with priority H voluntarily relese the CPU. Now your boss ask you to implement a resource-reservation mechanism. Under this mechanism, each application is associated with a parameter, namely, “_share”. For example, if a task is assigned to _share(100, 200) then the task requires 100 ms of CPU time every 200 ms. By adopting this concept, each application can receive its desired share of CPU, and the trouble mentaioned above could be eliminated. To reflect the urgency of different application, parameter “_ungency” is assigned to each application. Every application can be assigned to a unique urgency level. When there are two applications contending the CPU, the applications of higher-level of urgencies always win. Furthermore, it is permitted that less urgency applications are preempted by highly urgent applications. There are two implementation issues : First, there is no access to source code of a proprietary system like Windows, so everything you do must be transparent to the operating system. Second, there are only three different priority levels in your existing system and you have to emulate that each application could have their unique urgency levels. 

 ■ Check list of stuff to deliver 

 ● An application with a simple GUI, by which users can dynamically adjust parameter “_share” ans “_urgency” to applications. *Note* target applications can be any ordinary application being running in Windows, like WORD, IE, etc. 

 ● A short document (5 pages, 12pt font, single line space) on your implementation. Describe how you emulate a number of urgency levels by using only three priority levels. Also describe how you verify that your approach is correct.

[關於愛情] When a Sily boy loves a girl.....


有些女孩你如果錯過了,就再也遇不到一模一樣的了~~~再也......

影音連結 http://vn505147.spaces.live.com/blog/cns!D1746827E7E3BCB2!2231.entry