2009年12月31日
欲速則不達
剛剛客戶通知我,前兩天交付的東西有誤。那個東西不難,但數量多且雜,若不專心做,很容易出錯。而… 我就是沒做到"專心做",所以出錯了… 越是簡單的事,越是不能掉以輕心!必須要求自己提高「把事做對」的能力!!
2009年11月16日
飛車(公路車)來回南港-雙溪
2009年11月3日
公路車入手記
上網作了很多功課,鎖定GIANT的產品,原因無他-單車的靈魂在車架,而我心目中最好的台灣車架品牌是GIANT。
GIANT主要有兩大公路車系統- TCR 及 OCR (2009轉為 Defy),TCR偏向競賽性質;OCR偏向舒適性質。因為已擁有雙避震登山車-GIANT NRS,公路車再怎麼舒適也比不上雙避震車,所以進一步鎖定 TCR系列。
原先的預算,只夠買全鋁車架的 TCR2,後來因為一些原因,預算提高到可買複合式車架(半鋁半碳纖)的 TCR Alliance。十月初向車行口頭下訂,到了十月底,車行告知還要等到十一月中…
這中間發生一個小插曲,對最後的結果發生很大的影響… 話說TCR Alliance的大盤是標準盤(53/39T)而非CT盤(50/34T),對肉腳和一般人來說,爬山路標準盤將會較CT盤辛苦很多,而我騎山路的機會 較多,所以預料TCR Alliance入手後將吃很多苦頭。辛苦並不是我擔心的,真正麻煩的是容易傷膝蓋這個風險,年紀一天比一天長,總是要考慮到後半生的事… 十月底去車 行關心何時TCR Alliance將到貨時,聽到還要半個月才有機會到貨,灰心的同時向老闆多訂一組105 大盤(CT),當老闆告知預估價格後,原本在旁邊哈拉聊人的財政部長說話了:你這樣換下來,總價只比更高一等級的車差一點,要不要直接考慮高一級的車(TCR Advanced 3)。 這時換我說不出話了… 治家甚嚴的財政部長竟然自動提高購買預算,這是我想都沒想過的事。此機會稍縱即逝,確定不是聽錯後趕快拉著車店人員看車去。原本 沒料到有機會買更貴的車,所以也沒作任何功課,所以看到 TCR Advance 3,完全沒有感覺… 只覺覺得是換了碳纖車架的 TCR Alliance (或 TCR1)罷了!這時,財政部長前來關心「貨況」,聰明的店員看我面無表情,沒露出欣喜之意,說了一句:其實,TCR Advance 2 更超值,全套零件換成Shimano第二級的Ultegia, 價格只多xxxx元。沒想到,財政部長竟問我「是否更划算?」原本沒什麼概念的,但突然想到過去這一個月中作功課時,曾看過網友估算TCR Advanced 2比 TCR Advanced 3更划算,所以就回答了「是啊~ 更划算!」 沒想到財政部長向店員說,那就這一台吧~ 就這樣,我的第一台公路車入手了 - GIANT TCR ADVANCED 2
以上是神奇的入手過程,看我囉嗦一大堆,最後來看一下新車的樣子吧!
入手公路車,也表示將展開另一類型的騎車經驗,「更高、更遠、更快」是我自己的期許。期待各位與我一騎追求這樣的目標!
2009年9月4日
再次參加 - Never Stop 挑戰武嶺
2009年8月18日
WinXP 預約關機DOS指令
WinXP 預約關機DOS指令
在 開始-->執行 裡打上指令就可以了
一刻鐘=900s 半小時=1800s
shutdown -s -t 3600 (一小時後)
shutdown -s -t 7200 (二小時後)
shutdown -s -t 10800 (三小時後)
shutdown -s -t 14400 (四小時後)
shutdown -s -t 18000 (五小時後)
shutdown -s -t 28800 (八小時後)
shutdown -a (取消關機)
可搭配以下DOS指令混合使用
-l ==============>登出
-s ==============>電腦關機
-r ==============>重新啟動
-t xx ==============> xx秒後關機
-c "comment" ==============>註解
-f ==============>強制關閉程式
-i ==============>關區網中的電腦 有時會存取被拒
at hh:mm ==============>在xx點mm分關機 / 每個禮拜的行程
以上乃從網路上找到的資訊,因找不到原始出處,故在此未註明!
2009年8月9日
Ubuntu 9.0.4下安裝嘸蝦米
Ubuntu 9.0.4
安裝好 SCIM 1.4.6 (預設)
1. 下載 noseeing-6
$ wget http://edt1023.sayya.org/misc/noseeing-6.tar.gz
2. 解壓縮 noseeing-6.tar.gz
$ mkdir noseeing-6;cd noseeing-6
$ tar xvz -f ../noseeing-6.tar.gz
$ ls -l
總計 1024
-rw-r--r-- 1 arthur arthur 329621 2005-06-26 16:10 noseeing.cin
-rw-r--r-- 1 arthur arthur 263709 2004-10-05 21:13 noseeing.cin.orig
-rw-r--r-- 1 arthur arthur 76075 2005-06-26 16:11 noseeing.diff
-rw-r--r-- 1 arthur arthur 349577 2005-06-26 16:11 noseeing.gtab
-rw-r--r-- 1 arthur arthur 1366 2005-06-26 09:55 README
3.編輯 noseeing.cin,將檔頭做修改(字碼表"a A"之前的全部清空), 改成如下:
### File header must not be modified
### This file must be encoded into UTF-8.
### This file comes from xcin module.
SCIM_Generic_Table_Phrase_Library_TEXT
VERSION_1_0
### Begin Table definition.
BEGIN_DEFINITION
### An unique id to distinguish this table among others.
### Use uuidgen to generate this kind of id.
UUID = 3d872a7a-760e-400c-8b23-688d38390e81
### A unique number indicates the version of this file.
### For example the last modified date of this file.
### This number must be less than 2^32.
SERIAL_NUMBER = 20040922
ICON = /usr/share/scim/icons/liu5.png
### The default name of this table
NAME = Liu5
### The local names of this table
NAME.zh_CN = 嘸蝦米
NAME.zh_TW = 嘸蝦米
NAME.zh_HK = 嘸蝦米
### Supported languages of this table
LANGUAGES = zh_TW,zh_HK,zh_CN,zh_SG
### Prompt string to be displayed in the status area.
STATUS_PROMPT = 中
### If true then the first candidate phrase
### will be selected automatically during inputing.
AUTO_SELECT = FALSE
### If true then a multi wildcard will be appended
### at the end of inputing string automatically.
AUTO_WILDCARD = TRUE
### If true then the result string will be committed to client automatically.
### This should be used with AUTO_SELECT = TRUE.
AUTO_COMMIT = FALSE
### If true then the inputed string will be automatically splitted during inputing.
AUTO_SPLIT = TRUE
### If true then the phrases' frequencies will be adjusted dynamically.
DYNAMIC_ADJUST = TRUE
### If true then the preedit area will be filled up by the current candidate phrase automatically.
AUTO_FILL = FALSE
### If true then the lookup table will always be shown if there is any candidate phrase.
### Otherwise the lookup table won't be shown unless the user requires it by moving the preedit caret left.
ALWAYS_SHOW_LOOKUP = TRUE
### Use full width punctuation by default
DEF_FULL_WIDTH_PUNCT = TRUE
### Use full width letter by default
DEF_FULL_WIDTH_LETTER = FALSE
### The maxmium length of a key.
MAX_KEY_LENGTH = 4
### Valid input chars.
VALID_INPUT_CHARS = ,.'abcdefghijklmnopqrstuvwxyz[]
### Single wildcard char, can have multiple chars.
SINGLE_WILDCARD_CHAR = ?
### Multi wildcard char.
MULTI_WILDCARD_CHAR = *
### The key strokes to split inputed string.
SPLIT_KEYS = space
### The key strokes to commit the convert result to client.
COMMIT_KEYS = space
### The key strokes to forward the inputed string to client.
FORWARD_KEYS = Return
### The key strokes to select candidiate phrases.
SELECT_KEYS = space,v,3,4,5,6,7,8,9,0
### The key strokes to page up the lookup table.
PAGE_UP_KEYS = Page_Up
### The key strokes to page down the lookup table.
PAGE_DOWN_KEYS = Page_Down,space
END_DEFINITION
### Begin Table data.
BEGIN_TABLE
4. 這檔頭下面接的就是 無蝦米的字碼對照表 => a A ... 等.
5. 對照表完後, 再補
END_TABLE
6. 將 noseeing.cin 轉成 scim 認得的 liu.bin 檔
$ scim-make-table noseeing.cin -b -o liu.bin
7. 執行 dpkg -L scim-tables-zh檢查SCIM之安裝位置;將 liu.bin 放到SCIM之正確位置
$sudo cp liu.bin /usr/share/scim/tables/Liu5.bin
8. 將嘸蝦米圖檔從這兒下載,並另存到正確位置。
9. 打開SCIM設定程式,應該可在繁體中文的輸入法中看到嘸蝦米了!
2009年5月24日
2009-05-23 烏來信賢、桶後輕鬆騎
一早在雲仙樂園往福山的路旁集合。今天共有四名參加者,照片上由右至左分別是大全、大本、Peg
往福山出發後不到3km就到了信賢吊橋,今天要過橋去走汽車無法進入的路線。
吊橋上的合影
過橋後往前騎遇到一個瀑布
這兒剛好有平台,所以用自拍模式留下4個人的合照。
陸續遇到好幾個瀑布,雖然都是小小的,但也有清雅的感覺。
以下這幾張是邊騎邊拍的照片。
後面那傢伙,您太強了吧?!低頭看地上也能騎車…
這一條步道短短的,另一端接著信賢國小,再往前則是內洞林道的入口。騎到這兒大伙才剛熱身而已,不想就此結束,因此回頭開車往桶後林道開去。
經過孝義派出所,向同行伙伴解釋無法進入內洞林道的原因,接著再往前到烏玉檢查哨處停車,開始騎車進入桶後林道。
以下這張是桶後林道爬升段往下看,桶後溪在此形成一個大彎道。
桶後林道3km路旁一個中型的瀑布,剛好在此休息一下並拍照留念。
再往上一段,路旁的攔沙壩,另一邊溪谷邊很適合遊憩!
桶後林道車行終點-桶後吊橋。汽車最遠可開到這兒,再往內是步行者及騎士專享的林區。
往內沒多遠,遇到的一個指示路牌,照片後方的方向,是往大礁溪山。
這張是大全和他的愛車。
這張是大本。
過了路牌,是我覺得最有味道的路段,高聳的杉林,地上鋪滿自然生長的低矮植被,中間是一條碎石路徑,走起來就很有感覺。
越過一條小溪後,再往前沒多遠,來到一點需小小扛車的地點,我們在此折返。
回到吊橋處後開始下大雨,我們一行人被突來的大雨淋成落湯雞,我和大本有帶雨衣,趕緊穿了起來,Peg和大全則是不得不淋雨騎車。騎到3KM處,雨沒了,趕緊繼續前行回到停車處。開車回到烏來國小附近,將車停於此,走路到烏來老街吃東西。吃完後就結束今天行程,開車回家囉!
來到烏來,當然要順道去桂山電廠買桂山冰棒囉~ 我、Peg、大全三人一人抱一箱回家,準備和家人大啖消暑聖品-冰棒。
2009年4月27日
2009年4月21日
2009年4月5日
摔車紀念日
今天騎完五指山1~3段,正要轉進第五段,在柏油路上一時興起,連續作"平跳",轉進小徑不平整的石塊路面了,看到一個小落差還想再加碼,就跳,落地時前叉稍稍側傾、打滑,就這麼人往車頭撞,然後往左前方撲倒了,當場在地上痛到動彈不得。前後的車友都很緊張的下車來關心,我則是在地上躺了好一會才站地起來,作一些動作確定身上沒大傷,只有胸腹、四肢有些挫傷。確定人沒大礙後,請其他車友繼續騎,Peg、侯爺則留下幫我善後。善什麼後?原來前輪內胎在落地一剎那爆胎了,請他倆幫忙換換胎。換完胎,繼續第五段,還是把今天的行程完成了。
為什麼想寫這篇摔車記,實在摔車的代價太高了,今天所幸沒太礙,但若經常摔,難保不會中大獎。所以,寫下這篇,警剔自己勿興奮過頭、得意忘形,而樂極生悲。
4/5日,就當作我的摔車紀念日吧!
2009年3月18日
能高越嶺西段off-road
| 出發時間 | 時距 | 目標 | 里程(KM) | 距離(KM) | 海拔(M) | 爬升高度(M) |
| 07:00 | 屯原登山口 | 0 | 2000 | |||
| 09:00 | 02:00 | 雲海保線所 | 5.2 | 5.2 | 2360 | 360 |
| 09:15 | 00:15 | 休息 | ||||
| 13:00 | 03:45 | 天池山莊 | 14.7 | 9.5 | 2890 | 530 |
| 13:45 | 00:45 | 中餐 | ||||
| 14:05 | 00:20 | 光被八表 | 17.3 | 2.6 | 2810 | -80 |
| 14:35 | 00:30 | 天池山莊 | 19.9 | 2.6 | 2890 | 80 |
| 15:45 | 01:10 | 雲海保線所 | 29.4 | 9.5 | 2360 | -530 |
| 16:00 | 00:15 | 休息 | ||||
| 16:40 | 00:40 | 屯原登山口 | 34.6 | 5.2 | 2000 | -360 |
2009年3月8日
領導等於作人
領導等於作人:
什麼都不會的時侯 - 少不多是
初階主管 - 少說多聽 =>練習說話只需講重點
中階主管 - 少我多你
高階主管 - 少舊多新
老闆 - 少會多賣
資源有限?資源豐富?
啟發這篇日誌的 blog 在此!
2009年1月19日
5 Tips on Project Reporting
As a Project Manager, now that the New Year has started you will need to report on the status of your projects. Your Project Sponsor will want to know if you're on track and when their project will be complete. To help you do this, read these...
5 Tips on Project Reporting
Project status: Create a weekly Project Status Report to show your actual vs. planned effort, percent complete and actual vs. forecast spend. Specify the number of open risks, changes and issues, and state whether action by your Sponsor is required to resolve them. Also show the forecast amount of time, effort and money required to finish the project. Always try and forecast as accurately as possible. Never forecast optimistically, always conservatively.
Task completion: You need to regularly show your Sponsor your progress against the tasks listed on your schedule. Create a summarized view of your project plan and update it to reflect the percent complete for every task. Then append this summary view to your Project Status Report. This way, your Sponsor can drill down to see further information about each task, if they want to.
By offering your Project Sponsor both summary and detailed information weekly makes them feel like your project is an "open book". They will have all of the information about your project at their finger-tips. This way, you will get more buy-in from your Sponsor and more support when it's needed.
Milestones: You need to add Milestones to your project plan to show when the major project deliverables will be produced. You then need to report on the progress of each milestone to your Sponsor. Show the percent complete of each milestone, and again, forecast the completion dates.
Here's another tip: You will get more out of your team if you motivate them to complete milestones, as opposed to tasks. That's because people are usually proud of the things that they have achieved in life (i.e. milestones), as opposed to the things they have done to achieve them (i.e. the tasks).
Getting help: Project Sponsors don't always want to hear "we're on track and under budget" in their project reports. They just want to hear the truth. So if you're behind schedule and you need help to get back on track, then tell your Sponsor about it in your project reports.
State exactly what you need from them. Show them that you're doing the best you can and that you're the best person for the job, but that you still need their help to deliver the project. If you need more time, money or resources, then ask for it. Don't be afraid. And remember, the best time to ask for help is before you really need it. This gives you contingency, because it always takes time for help to arrive.
One version of the truth: Your project reports need to depict "one version of the truth" to your team. Keep them 100% accurate and be as open as possible about real issues that are affecting your team. Remember that if you communicate an issue to your Sponsor, then it becomes their issue to fix as well. Reporting issues is a great way to share the responsibility for fixing them.