老車夫的熱情

前面老車夫一臉風霜，汗流浹背，手上仍然使勁地拉著，車上一夥年輕新貴，手裡數著花花的鈔票，直嚷嚷，久了還真沒意思，找一站我們下車，別再那麼辛苦啦，一定要好好地玩一玩。

「一定得完成這趟任務啊!」老車夫心裡盤算著，幾年的辛勞不能毀於一旦，車上那幾個小夥子，運氣是比自己好，早早地入行，也攢了一桶金。

老車夫想著「照眼下的狀況，即使小夥子走了，這活我還得幹個幾年，等待好時機，好好地賺一筆，自己也可以清閒。」

老車夫近來老覺得這活辛苦，也不是說力不從心，只是當年的同伴紛紛走人，如今這世道是連眼前這幫小夥子也想下車了，儘管一路上給大夥帶路的老師傅也還在岡位上。

想起剛入行時的熱情，老車夫看著身邊默默工作著的老師傅，搖搖頭，罷了罷了。

九陰真經與The Zen of Python

先說金庸小說射鵰英雄傳裡一段故事，黃蓉使詐，騙歐陽鋒逆練九陰真經走火入魔的情節，有一段黃蓉故意胡謅一通，直令西毒先生抓破頭，仍是不知所云。

這可跟The Zen of Python對比：

• Beautiful is better than ugly.
• Explicit is better than implicit.
• Simple is better than complex.
• Complex is better than complicated.
• Flat is better than nested.
• Sparse is better than dense.
• Readability counts.
• Special cases aren't special enough to break the rules.
• Although practicality beats purity.
• Errors should never pass silently.
• Unless explicitly silenced.
• In the face of ambiguity, refuse the temptation to guess.
• There should be one-- and preferably only one --obvious way to do it.
• Although that way may not be obvious at first unless you're Dutch.
• Now is better than never.
• Although never is often better than *right* now.
• If the implementation is hard to explain, it's a bad idea.
• If the implementation is easy to explain, it may be a good idea.
• Namespaces are one honking great idea -- let's do more of those!

工程師可以做出晦澀、難解、糾結的ugly design or implementation，或是像Assembly code，甚而不留comment，弄到後來只有他自己才能看懂。

這樣一來，老闆大概就是西毒了，恐怕沒死也剩半條命。

【讀書筆記】師父，那些我在課堂外學會的本事，Case Study

====================================

Case Study: L公司

====================================

CEO，特助【文化，授權，管理】

• 引進外部CEO，雖然業務創新高，文化、管理面沒有改變
• 管理團隊變動，互信建立不易
• 特助功能：信任、授權、尊重不夠
• 缺乏急迫感驅力
• 組織化、流程化  <---> 新事業，混亂，解決問題
• 過早上市規劃 ?

MIS People Skill Sets

At the very beginning, when I engaged with the MIS department, the assumption was that the senior people must be matured enough about the professional since they had been staying in the field for many years. Unfortunately, I was wrong.

Then I tried to get more understanding about their background and experience.

The first thing, most of their major were "information management" from school like university of scientific and technology that provided vocational curriculum in business like accounting, economics, e-commerce, marketing, database, ERP, business operation...etc.

Basically, technology courses played a very slight weight in the plan, ex lack of OS and networking concept, not to mention open source SW like Linux.

From my view, course for marketing, business are more like “street, or hands-on knowledge” which can't be taught efficiently in classroom especially for those young kids w/o the knowledge of what really business company are doing.

Furthermore, MIS people, seemingly lack of capability or even motivation to learn something new, didn't know how to evaluate the solution that vendors proposed. They might totally rely on vendors' support w/o knowing what risk they brought in or even what they really did.

For sure, to capture the new trend is really a huge challenge in such a rapid changing environment today. So the best policy is to get some ready-to-run black boxes and change it by try-error if necessary.

Or even it was worse or sad that they had no idea when they were running into the grey boundary between the vendor and company.

In such way, after taking the job for many years, their professional maturity didn't go beyond the apprentice level.

REF

讀蟲小聚 你以為自己強，其實只是圈子弱、平臺低、對手矬