Tuesday, June 25, 2013

Display remote Node.JS service logs on Chrome Console


In recent years, we got plenty of PaaS services which provide very simple and easy way to deploy our Node.JS services.

Usually after deploying my service, I have to use the command line tools or visit some very slow web pages to access the server logs. It's really waste my time.

But today, I want to introduce a tool, Chrome Logger, it provides a way to display server logs into Chrome Developer Tool's Console.


Install it, then visit my sample project on Heroku to see what's going on.
Update 06/25 00:40:
  • If you're using ExpressJS, you can simple log your error like following error handling middleware
Update 06/25 01:50:

Pull requests sent : chromelogger & express-chrome-logger.

Good luck to myself.


Sunday, June 9, 2013

CSS Frameworks

CSS Framework List 

  • device compatibility
  • browser compatibility
  • compiler support
  • license.

http://usablica.github.io/front-end-frameworks/compare.html

Wikipedia

Focus on grid system comparison

http://en.wikipedia.org/wiki/CSS_frameworks

Thursday, April 4, 2013

取得中華電信(Hinet)光世代Wifi基地台內的密碼

最近申辦了中華電信光世代50M/10M,並且申請了免費附贈的Wifi。

拿到的機器是D-Link 的 WBR-2200


剛剛參考一些網路上的文章,把固定IP申請好,連入基地台,卻發現裡面有一個神祕的帳號:xxxxxxxx@wifi.hinet.net

找了一下Mobile01,這一組帳號的密碼,居然要打電話自己去跟中華電信要...... orz 
礙於懶得打電話,就只好靠自己來。

我用的是谷歌(Chrome)瀏覽器,對這密碼欄位點選右鍵(Right Click) 然後選檢查元素(Inspect Element)。



然後就... 嗯


我想這個號碼應該可能大概不是那個密碼,就把它複製下來試試看,

接下來... 如有雷同純屬巧合。

謝謝。





以上僅於Hinet(中華電信)光世代附贈的家用Wi-Fi機器WBR-2200可能適用

Thursday, March 14, 2013

Google Reader will not be available ?!??!

Got this message this morning ...

"Google Reader will not be available after July 1, 2013"

http://support.google.com/reader/answer/3028851?hl=en&uls=en


The best alternative so far is Feedly... trying now
http://blog.feedly.com/2013/03/14/google-reader/

Saturday, February 23, 2013

成功的層級

今天重新拜讀了Seth Godin的成功的層級 (The hierarchy of success) 一文
其中提到的層級如下
1.態度(Attitude)
2.研擬方案(Approach)
3.設定目標(Goals)
4.策略(Strategy)
5.戰術(Tactics)
6.執行(Execution)

每一個"成功",不管是長短期或是不同的職位,都是環環相扣的,每當需要做出決定時,都應該全面去檢視自己的狀況。

常見的例子,像是因為執行上的一些困難,工程師不願意和設計師多做溝通。
或是老闆想要的目標是X,但是策略與戰術的人卻沒有良好的溝通。
這些 都會讓所謂的成功,充滿的風險。
不可不慎。

Reference:
http://sethgodin.typepad.com/seths_blog/2009/09/the-hierarchy-of-success.html