Ernest Talks

How to create EC2 snapshots with multiple AWS accounts by CLI?

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQaHqYLe5-e6MJErYYbPnJgbDkjBfrQRN_8JNoe9x8460Dj7XgFdrvLWLmNRZV6BaYfDfdpDmvVat-0cYgXw29oy3eDdo4ZxjRuc8i7HQFzV6Rl-yBSB4TiTVP1Q6nh5G23XxtLadO8WM/s1600/aws_logo_web_194px_2.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQaHqYLe5-e6MJErYYbPnJgbDkjBfrQRN_8JNoe9x8460Dj7XgFdrvLWLmNRZV6BaYfDfdpDmvVat-0cYgXw29oy3eDdo4ZxjRuc8i7HQFzV6Rl-yBSB4TiTVP1Q6nh5G23XxtLadO8WM/s1600/aws_logo_web_194px_2.png" /></a></div>
 
The new 2013 <a href="http://aws.amazon.com/cli/" target="_blank">AWS CLI (python-based)</a> tool is really awesome!! 
 
I plan to have a script to have snapshots for all my friends' instances 
which work with EBS (volumes). First of all, I use IAM to create a user 
who have limited permissions so that I don't need all of their root 
account access/secret keys. Here are my steps. 
<h2>
1. Install AWS CLI</h2>
You can setup the new CLI on Windows, Mac, and Linux very easily (than previous versions). On my ubuntu server, I just need to install: 
 
<pre class="brush: bash">apt-get install python-pip
pip install awscli</pre>
 
More details, please refer to <a href="http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-set-up.html" target="_blank">here</a>. 
 
<h2>
2. Create a AWS CLI config file</h2>
You will put all your access/secret keys and assigned regions at this config file: ~/.aws/config 
Please do remember to assign your region. "Region" is also important for almost all AWS CLI and AWS API calls. Also, make sure you keep this file in a save location, and 'chmod 600' may be a good idea. 
 
Here is an example one: 
 
<pre class="brush: bash">[default]
aws_access_key_id={your access key}
aws_secret_access_key={your secret key}
region={your region}
output=text

[profile server01]
aws_access_key_id={your access key}
aws_secret_access_key={your secret key}
region={your region}
output=text

[profile server02]
aws_access_key_id={your access key}
aws_secret_access_key={your secret key}
region={your region}
output=text</pre>
 
If you're interested in "<a href="http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-multiple-profiles" target="_blank">Multiple Configuration Profiles</a>" please refer to the AWS CLI document. 
 
<h2>
3. Create a profile list file</h2>
As you seen in the ~/.aws/config that we create multiple configuration profiles there, then we can choose all or some of these profiles in our snapshot script. 
 
You can create a file to list all your profiles named "profile_list" at the same folder of <a href="https://gist.github.com/dwchiang/7261458/">snapshot-multiple.sh</a> (or you can modify the path by updating "profile_list"). If you want to use this for just one AWS account, there's no problem, you can just list one profile name in this file. 
 
Here is one example: 
 
<pre class="brush: shell">server01
server02</pre>
 
<h2>
4. Create a script for snapshot </h2>
I may update this <a href="https://gist.github.com/dwchiang/7261458/">snapshot-multiple.sh</a> script in the future so I put it at gist. 
 
<script src="https://gist.github.com/dwchiang/7261458.js"></script> 
 
 
<h2>
5. Test it & modify it</h2>
I choose the tag name of the running instances, and current date as the description of snapshots. You can mark the command "aws ec2 create-snapshot --volume-id $volume --description $description" with a "#" in front of this line for your testing. You will see how's going about the naming and you can modify to be the right naming format you want. 
 
<h2>
6. Run it</h2>
Once you like the description of snapshot naming rules, you can remove the "#" in front of "aws ec2 create-snapshot" and run this script. (You may need to 'chmod u+x snapshot-multiple.sh' to run it.) 
 
If you like it, you can put it in your crontab. Also, you may want to reference this AWS whitepaper "<a href="http://media.amazonwebservices.com/AWS_Backup_Recovery.pdf">Backup and Recovery Approaches Using AWS</a>" (page. 7~9) to know more about snapshots and hot backups.

How to create EC2 snapshots with multiple AWS accounts by CLI?

The new 2013 AWS CLI (python-based) tool is really awesome!! I plan to have a script to have snapshots for all my friends' instanc...

體驗提升，Amazon CloudFront 支援檔案上傳

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQaHqYLe5-e6MJErYYbPnJgbDkjBfrQRN_8JNoe9x8460Dj7XgFdrvLWLmNRZV6BaYfDfdpDmvVat-0cYgXw29oy3eDdo4ZxjRuc8i7HQFzV6Rl-yBSB4TiTVP1Q6nh5G23XxtLadO8WM/s1600/aws_logo_web_194px_2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgQaHqYLe5-e6MJErYYbPnJgbDkjBfrQRN_8JNoe9x8460Dj7XgFdrvLWLmNRZV6BaYfDfdpDmvVat-0cYgXw29oy3eDdo4ZxjRuc8i7HQFzV6Rl-yBSB4TiTVP1Q6nh5G23XxtLadO8WM/s1600/aws_logo_web_194px_2.png" /></a></div>
 
AWS Blog <<a href="http://aws.typepad.com/aws/2013/10/amazon-cloudfront-content-uploads-post-put-other-methods.html" target="_blank">Amazon CloudFront - Content Uploads Via POST, PUT, other HTTP Methods</a>> 最新消息（嗯嗯是有延遲幾天才看到啦XD），但真的是個不錯的功能，可以為使用者體驗作一些提升（減少使用者跨地理洲上傳檔案的時間、提升上傳效率），因為現在也可以（幾乎無痛地）透過 CloudFront 的 Edge Server 讓使用者上傳檔案、上傳內容，然後 Edge Server 會幫忙再送進原本這組 CloudFront 設定對應的 origin（例如 Amazon S3）。 
 
依照不同的應用，可以減少某種程度對於前端服務主機的負載。（當然，越是 decouple 到很乾淨） 
 
流量費用收費，以 AWS 的角色應該會希望大家盡量把檔案、內容往裡面送，所以通常送進去會比拿出來還要便宜（許多）。以美國地區來看， 
<ul>
<li>這次的「送進去 （Regional Data Transfer Out to Origin (per GB)）」是 US$ 0.02，</li>
<li>第一階段（First 10 TB / month）的「拿出來（Regional Data Transfer Out to Internet (per GB)）」則是 US$ 0.12。(Oct/22, 2013 的資訊)</li>
</ul>
完整且最新的價目表，請參考：<a href="http://aws.amazon.com/cloudfront/pricing/">http://aws.amazon.com/cloudfront/pricing/</a>

體驗提升，Amazon CloudFront 支援檔案上傳

AWS Blog < Amazon CloudFront - Content Uploads Via POST, PUT, other HTTP Methods > 最新消息（嗯嗯是有延遲幾天才看到啦XD），但真的是個不錯的功能，可以為使用者體驗作一些提升（減少...

Participation of Mozilla Summit, facilitator of supporting session

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWBGio_50TpR101fp6eCCYIuY7pm_5hxfDrdk7jXsVgfkVfri5HAWzbCyWLd4gxyYhUQbvAR7dVP-RfdP7BLMfrrjUOTOCnC7Aj3cbV3poQhkvZuYLkvm-7GkUOyBYSYizFPPSQ_kAnbI/s1600/DSC01742.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWBGio_50TpR101fp6eCCYIuY7pm_5hxfDrdk7jXsVgfkVfri5HAWzbCyWLd4gxyYhUQbvAR7dVP-RfdP7BLMfrrjUOTOCnC7Aj3cbV3poQhkvZuYLkvm-7GkUOyBYSYizFPPSQ_kAnbI/s640/DSC01742.JPG" width="640" /></a></div>
 
 
<a href="https://wiki.mozilla.org/Summit2013" target="_blank">Mozilla Summit 2013</a> (Oct 3-6) is my first Mozilla Summit in my volunteer life of Mozilla Community. It's really great to have an opportunity to be a facilitator of <a href="https://wiki.mozilla.org/Summit2013/Sessions" target="_blank">support session</a> in Summit. 
 
Refer to "<a href="https://wiki.mozilla.org/Summit2013" target="_blank">Five Ways to Have a Great Summit</a>" at Wiki page of Mozilla Summit 2013. The first one is "Participate" which is the most important key that I want to demonstrate to all Mozillians especially young talents that there's no limitation when we are challenging our visions and dreams. 
 
This post will write about how I participate to be a facilitator before Summit, at Summit and after Summit. Hope it will not too boring and may be sort of useful for someone who plan to be a speaker/facilitator of any Mozillian events in the future. :-) 
 
One Month Before Summit: Sign-up 
 
Sep/8 -- inception 
 
Happen to read the information about signing-up to be a facilitator of Summit supporting sessions. I leave a post on my Facebook wall: "Plan to be a facilitator of "ideas into action" session in Santa Clara....<a href="https://etherpad.mozilla.org/summit-sessions-sunday-ideasintoaction">https://etherpad.mozilla.org/summit-sessions-sunday-ideasintoaction</a>". 
 
Sep/10 or Sep/11 -- Summit reminder & sign-up 
 
I guess I done my sign-up when I got this Summit reminder that maintained about "Facilitators needed (sign up by 11 September)". In my brain (based on my previous experience), there's usually a speaker will stand on the stage and there are some facilitators stand or sit around the classroom to help the session process smoothly. Also I think that I have some sort of solid speech and on-stage training experience in my AIESEC age, there should be no problem even "facilitator" really means "speaker" :p 
 
It's simple. Just leave my name on the <a href="https://etherpad.mozilla.org/summit-sessions-sunday-ideasintoaction" target="_blank">session etherpad</a> (by session). 
 
2 Weeks Before Summit: Training  
 
Sep/12 --Receive a training invitation by Katherine via google calendar 
 
I received one calendar invitation titled "[Summit Supporting Sessions] Facilitator Training". Don't remember the exactly date but I was in Montreal, Canada attending Bluetooth Working Group Summit that week and flying back Taiwan on Friday or Saturday that means I will miss the Summit Facilitator Training. 
 
(I received the video of this training on Sep/18 email titled "[Please Read] Summit Facilitator Training Video + Meeting Notes" which is also a good way for me to know more about Summit. I'm still trying to find anything and everything about the attend characteristics to form and design the session.) 
 
Sep/12 -- Group emailing 
 
Then I found Lawrence's (who is the Track Owner of this session) email titled "Summit Session Confirmation and Next Steps" which is a long but very useful email described in details and also connected all 3 facilitators of this session. Therefore we can brainstorm and discuss together. :-) 
 
There is also one clear and useful "Facilitator Guide" at Summit Wiki -- <a href="https://wiki.mozilla.org/Summit2013/Sessionfacilitators">https://wiki.mozilla.org/Summit2013/Sessionfacilitators</a> , where I can find contact, schedule, date, planning there by myself without interrupting anyone who should be very busy couple weeks before Summit. 
 
An interesting thing for me is "special technical equipment or supplies form" that says supporting session encourage facilitators not to use projectors and wish to have more discussion, more face-to-face information exchange. 
 
1 Week Before Summit: Cooking 
 
Kate keeps kindly remind all facilitators to prepare session framework and provide to Track Owners. There are also two "Summit Session Facilitator Support Calls" can be attended. Also get presentation slide template (keynote format), but I'm thinking maybe I don't need the template due to supporting session keeps reminder about "it doesn't need to be slides!". 
 
Sep/27 -- Group Meeting 
 
Thanks for all facilitators' of this session help to host a Vidyo conference call. Thanks to Larissa's hosting and Karen, Selena's help (due to our timezone difference). We had some preparation / brainstorming and structure our ideas and plans on the <a href="https://etherpad.mozilla.org/summit-sessions-sunday-ideasintoaction" target="_blank">session etherpad</a>. 
 
Sep/30 -- Everyone's help 
 
Karen drafted v1 slide outline. Larissa drafted a worksheet. These all become great materials for me to cook slides. 
 
Oct 2 -- Fly to Santa Clara 
 
I start to cook slides and publish the drafting version on <a href="http://www.slideshare.net/dwchiang/ideas-into-action-v11-santa-clara" target="_blank">slideshare</a>, and update it day by day. 
 
 
 
At Summit 
 
The first question is there's the other same name session "Ideas into Action" on the Day 3 morning time, but all of us (facilitators of the name name session in the afternoon) don't know the exact content of the session in the morning. Though there's still some difference between these two same name sessions: the one in the morning is more like for global Mozilla, the one in the afternoon is more like for one person and for a team. 
 
In Santa Clara, we totally have 6 people in this session. It's kind of tiny session but it's great for every attendees to have more practicing time and opportunity to participate. :-) 
 
I got projector and a white board due to 2-day observation of the same session room. 
 
<iframe allowfullscreen="" frameborder="0" height="486" marginheight="0" marginwidth="0" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/26884934?rel=0" style="border-width: 1px 1px 0; border: 1px solid #CCC; margin-bottom: 5px;" width="597"> </iframe> 
<div style="margin-bottom: 5px;">
 <a href="https://www.slideshare.net/dwchiang/ideas-into-action-v11-santa-clara" target="_blank" title="Ideas into Action (Santa Clara Edition)">Ideas into Action (Santa Clara Edition)</a> from <a href="http://www.slideshare.net/dwchiang" target="_blank">Ernest Chiang</a> </div>
 
 
Here are some more pictures of our session in Santa Clara: 
 
<a href="http://photo.ernestchiang.com/mozsummit-sun/e7c86a213"><img alt="Ernest Chiang Photography: MozSummit, SUN &emdash; " height="435" src="http://photo.ernestchiang.com/img/s5/v117/p2089198099-3.jpg" width="580" /></a> 
 
<a href="http://photo.ernestchiang.com/mozsummit-sun/e77a586a3"><img alt="Ernest Chiang Photography: MozSummit, SUN &emdash; " height="435" src="http://photo.ernestchiang.com/img/s5/v129/p2007336611-3.jpg" width="580" /></a> 
 
<a href="http://photo.ernestchiang.com/mozsummit-sun/e7df9b289"><img alt="Ernest Chiang Photography: MozSummit, SUN &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v94/p2113516169-3.jpg" width="580" /></a> 
 
<a href="http://photo.ernestchiang.com/mozsummit-sun/e7cd71e92"><img alt="Ernest Chiang Photography: MozSummit, SUN &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v114/p2094472850-3.jpg" width="580" /></a> 
 
(Special thanks to <a href="https://blog.othree.net/" target="_blank">othree</a> and <a href="http://irvin.sto.tw/" target="_blank">Irvin</a> who took pictures for this session.) 
 
 
 
 
After Summit 
 
It's a great supporting session to support everyone's dreams and ideas, with Nature of Mozilla, Mozilla Four Pillars, and some tools (SMART, 7S). All attendees enjoy it. Here are some feedbacks of them. Thank you everyone :-) 
 
<blockquote class="tr_bq">
"It was an intimate session with the Taiwan community and I have to say this was my favorite session ever! Ernest introduced some tools we can use in brainstorming for our strategic plans and events that we can organize. I will really apply the useful stuff we have learned to our team!" 
 
-- <<a href="http://fayetandog.wordpress.com/2013/10/13/mozilla-summit-2013-santa-clara/#more-949" target="_blank">Mozilla Summit 2013 Santa Clara</a>>, Faye's Book</blockquote>
 
<blockquote class="tr_bq">
"Just finished with Ideas into Actions session! Even though we're only few, we had a fun session! 😁👍… http://instagram.com/p/fJBqu2qHcM/" -- Marcucu Ang ‏<a href="https://twitter.com/heyitsmarcucu/statuses/386966437598076929" target="_blank">@heyitsmarcucu</a></blockquote>
 
 
Update, Feb/23, 2014: 
 
<blockquote class="tr_bq">
This is an awesome work about documentation about an event. Thanks to Faye's sharing about "<a href="http://www.mozillaphilippines.org/first-fsa-leaders-camp/" target="_blank">Very First FSA Leaders Camp</a>" of Mozilla Philippines. You can find the manual of this event at this <a href="https://db.tt/d3RW54r" target="_blank">Dropbox</a> link: <a href="https://www.dropbox.com/s/u6ffgtf8c3o3ryd/FSALeadersCampManual.pdf" target="_blank">https://www.dropbox.com/s/u6ffgtf8c3o3ryd/FSALeadersCampManual.pdf</a></blockquote>
<blockquote class="tr_bq">
This manual described about "Goals", "Manpower", "Logistics" and more all the detailed summaries about the event. Good reference for Mozillians to hold next great event.</blockquote>
 
 
 
 
If you are interested in "Ideas into Action" session or in having more participation as a Mozillian, please feel free to email me <<a href="mailto:dwchiang@mail.moztw.org">dwchiang@mail.moztw.org</a>> or find MozTW community at <a href="https://groups.google.com/forum/#!forum/moztw-general" target="_blank">moztw-general mailing list</a>. 
 
If you are interested in being a Mozilla speaker, you may like this program "<a href="https://wiki.mozilla.org/ReMo/SIGs/Evangelism_Reps" target="_blank">Evangelism Reps</a>". :-)

Participation of Mozilla Summit, facilitator of supporting session

Mozilla Summit 2013 (Oct 3-6) is my first Mozilla Summit in my volunteer life of Mozilla Community. It's really great to have an op...

Heading to Mozilla Summit 2013

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHomAaD9hKA8t-VBBKHJK0pGfx25YpQC5XGuqe0tmjJbBSGPCsBCkw6RCqUmLPjrcKD2qliFUJVQFSsby_WebL8rwAAJxf7JW_g9GamObm9dMiYHzc9AKtQZyFi9y1Xrbjd5iFEMH9oAg/s1600/DSC01367.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHomAaD9hKA8t-VBBKHJK0pGfx25YpQC5XGuqe0tmjJbBSGPCsBCkw6RCqUmLPjrcKD2qliFUJVQFSsby_WebL8rwAAJxf7JW_g9GamObm9dMiYHzc9AKtQZyFi9y1Xrbjd5iFEMH9oAg/s640/DSC01367.JPG" width="480" /></a></div>
 
準備出發去參加 <a href="https://wiki.mozilla.org/Summit2013" target="_blank">Mozilla Summit 2013</a> 囉！ 
 
今年總共在全球三個城市 Brussels, Belgium / Santa Clara, USA / Toronto, Canada 同時舉辦，連續三天的活動！ 將有連續 72 小時 / 4,320 分鐘 / 259,200 秒鐘將創造各種新的未來。期待這個精彩的週末，會有許多志工、貢獻者、社群夥伴、員工，統稱 <a href="https://mozillians.org/" target="_blank">Mozillians</a> 分享會議資訊或討論。 
 
此行，我也擔任星期天下午一場 Supporting Session 的 Facilitator (Santa Clara 場次，場地在 Grand Ballroom Salon E)，討論主題是「<a href="https://wiki.mozilla.org/Summit2013/Sessions/Sunday" target="_blank">Ideas into Action: Next steps for me and my team</a>」，屬於「Purpose and Strategy 」Track，敬請期待 :-) 有任何關於「實現點子」、「整理行動方案」、「訂計畫」方面的討論，都歡迎在 Summit 時找我一起聊。週五的時候我可能會穿 Beta 4 Team 的 T-shirt，週六的時候我會穿 Mozilla Reps 的黑色 Polo 衫。（看吧，是個很有計畫、很有組織的一個人吧 XDD） 
 
更多資訊，歡迎參考 <a href="https://wiki.mozilla.org/Summit2013" target="_blank">Summit 的 Wiki page</a> 或是可以在 IRC #mozsummit (global) 或 #mozilla-taiwan (MozTW 社群與台北辦公室夥伴) 找到我們。 
 
如果在找這次的大會議程，可以參考「<a href="https://wiki.mozilla.org/Summit2013/AgendaAllDays" target="_blank">AgendaAllDays</a>」，但隨時會修改更新，跑下一場 session 之前記得再檢查一下議程表。 
 
Summit 見囉！

Heading to Mozilla Summit 2013

準備出發去參加 Mozilla Summit 2013 囉！今年總共在全球三個城市 Brussels, Belgium / Santa Clara, USA / Toronto, Canada 同時舉辦，連續三天的活動！將有連續 72 小時 / 4,320 分鐘 ...

Meet Pebble - Part 1

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8xDd2hi7X4rXsEmDtgdu_j_gv0OxY0uWO4v9jPzQ-cjXg4XIrBP26DEQQJu7vqfvJ662drozQyuws8H1CBPCFKQnNG9G9d58rqdNaVGHnIykA8dXWyEBPOsbXIu3W2lBIO3ADvRsVovU/s1600/DSC01281.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="480" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8xDd2hi7X4rXsEmDtgdu_j_gv0OxY0uWO4v9jPzQ-cjXg4XIrBP26DEQQJu7vqfvJ662drozQyuws8H1CBPCFKQnNG9G9d58rqdNaVGHnIykA8dXWyEBPOsbXIu3W2lBIO3ADvRsVovU/s640/DSC01281.JPG" width="640" /></a></div>
 
來一張側面圖作為這篇開箱文的序曲吧，<a href="http://www.amazon.com/gp/product/B00AYDNRNA/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B00AYDNRNA&linkCode=as2&tag=ernesttalk-20" target="_blank">Pebble</a> （應該、可能、也許）是個許多人伴隨著其他相關關鍵字（<a href="http://en.wikipedia.org/wiki/Crowdfunding" target="_blank">Crowdfunding</a>, <a href="http://www.kickstarter.com/" target="_blank">kickstarter</a>）而耳熟能詳的一項創新產品，但（應該、可能、也許）有些朋友還未聽聞，選這張側面圖，試著想從一個 *** 的角度來看 Pebble，這隻手錶，這個顯示螢幕，這個能夠透過藍芽無線通訊介面接收訊息顯示在螢幕上的手錶，藉由這個裝置，能否帶出其他生活、運動、健康、互動的更多可能性呢？ 
 
在這篇文章形成哲學之前，還是先來看幾眼開箱的過程，以及 Pebble 的產品包裝吧 :-) 
 
<a href="http://photo.ernestchiang.com/p468785422/e7ca5a43e"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s1/v55/p2091230270-3.jpg" width="580" /></a>
 
 
Let's meet pebble! :-) 外包裝的底部。 
 
簡單列出目前支援的行動作業系統 iOS 和 Android。從這些機型與 Android 作業系統版本號碼可以看出 Pebble 可以支援傳統的藍芽 (2.1 + EDR)，但我們在公司實驗室也有掃到有 Bluetooth Low Energy (BLE, LE) 的訊號。等 Android 4.3/4.4+ 之後有開放支援 LE 即可為電池能源消耗效率帶來相當大的助益。對於 EDR 與 LE 世代交替（應該說雙雙出擊搞得人仰馬翻）之際，先採用共模藍芽模組是個明智且明確之舉。 
 
<a href="http://photo.ernestchiang.com/p468785422/e708175ab"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s11/v30/p1887532459-3.jpg" width="580" /></a>
 
 
外箱正面。「it's time」。非常漂亮的雙關語。很適合我這種南極人 :p 
 
這次我排到的 preorder 價錢是 USD 150 含運費。台灣地區收貨，但可以看到貨是從新加坡寄出。剛收到貨物通知的前兩天，在新加坡郵遞的網站上使用 Tracking number 是查詢不到這批貨的，但是貨進到台灣之後可以在台灣郵局快遞網站上查到這批貨。在出貨與收貨的資訊通知上面，算是還滿讓消費者（我）放心的。 
 
 
<a href="http://photo.ernestchiang.com/p468785422/e7df8fc48"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v97/p2113469512-3.jpg" width="580" /></a>
 
 
外箱側邊用來放了兩個作業系統的識別圖示。也因為這項產品有透過 Bluetooth EDR 通訊，因此想必也是有通過 MFi 審查，才得以使用盒上圖示。Bluetooth 圖示也代表著 Pebble 在藍芽協會是有登記在案的 EPL (End Product Listing)。 
 
<a href="http://photo.ernestchiang.com/p468785422/e74415e66"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v98/p1950441062-3.jpg" width="580" /></a>
 
 
外箱的另一側，就是準備開箱的意思囉 :p 
 
<a href="http://photo.ernestchiang.com/p468785422/e73f1c931"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s1/v48/p1945225521-3.jpg" width="580" /></a>
 
 
開箱中！ 
 
<a href="http://photo.ernestchiang.com/p468785422/e7e871953"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v104/p2122783059-3.jpg" width="580" /></a>
 
 
噹噹！Pebble 現身！ 
 
簡單的說明要去「go.getpebble.com」進行下一步。硬體只有 Pebble 產品本身以及一條 USB-to-custom 充電線。Pebble 與 <a href="http://talk.ernestchiang.com/2013/05/kindle-whitepaper.html" target="_blank">Amazon Kindle Paperwhite</a> 的包裝內置一樣走簡單風格。 
 
<a href="http://photo.ernestchiang.com/p468785422/e781df6b0"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s11/v29/p2015229616-3.jpg" width="580" /></a>
 
 
<a href="http://photo.ernestchiang.com/p468785422/e7f5052a8"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v99/p2135970472-3.jpg" width="580" /></a>
 
 
手錶表面貼上一張黏膜保護錶面，作一些（工廠中運送堆疊時的）基本防護。 
 
<a href="http://photo.ernestchiang.com/p468785422/e706d9bac"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s1/v48/p1886231468-3.jpg" width="580" /></a>
 
 
翻過來看背面還滿訝異的，之前看比較早期的樣品時，質感有顯著的提升。標示了產品名稱 pebble、生產地點、序號（末四碼待會會在藍芽連線名稱中看到，用以區別近距離內的藍芽產品）、CE/FCC/IC 認證圖示與編號、基本防水。 
 
<a href="http://photo.ernestchiang.com/p468785422/e77a87780"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s1/v47/p2007529344-3.jpg" width="580" /></a>
 
 
<a href="http://photo.ernestchiang.com/p468785422/e74ed81bf"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v17/p1961722303-3.jpg" width="580" /></a>
 
 
感覺內裝的白色固定材質與 <a href="http://talk.ernestchiang.com/2013/05/kindle-whitepaper.html" target="_blank">Amazon Kindle Paperwhite</a> 滿類似的材質或風格。 
 
<a href="http://photo.ernestchiang.com/p468785422/e77c14c68"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s1/v49/p2009156712-3.jpg" width="580" /></a>
 
 
這是 pebble 手錶的另一個側面照片，看起來工廠內的粉塵可能滿嚴重的。 
從這一側可以看到手錶的充電接頭以及方向性防呆孔洞（半弧形）。加上磁性設計，接上 USB-to-pebble 充電線不是一件困難的事。 
 
<a href="http://photo.ernestchiang.com/p468785422/e74870df0"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s4/v64/p1955007984-3.jpg" width="580" /></a>
 
 
正面錶面。撕掉保護膜之前。 
 
<a href="http://photo.ernestchiang.com/p468785422/e762f4217"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v100/p1982808599-3.jpg" width="580" /></a>
 
 
正面錶面。撕掉保護膜之後，露出光滑明亮有質感的表面。電子紙搭配這樣的表面應該是會吸引不少人被勸敗 XDD 
 
<a href="http://photo.ernestchiang.com/p468785422/e76f42402"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s11/v35/p1995711490-3.jpg" width="580" /></a>
 
 
pebble 側面，與充電接頭合照。 
 
<a href="http://photo.ernestchiang.com/p468785422/e74ac7163"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s4/v63/p1957458275-3.jpg" width="580" /></a>
 
 
按下任何按鍵之後可以看到 pebble 手錶的初始畫面。但沒有採用像 <a href="http://talk.ernestchiang.com/2013/05/kindle-whitepaper.html" target="_blank">Amazon Kindle Paperwhite</a> 那樣直接用電子紙的特性顯示說明內容，不過還是很簡潔易懂。手錶的顯示面積比起 Kindle 都小很多，因此引導使用者透過手機或其他行動裝置造訪 go.getpebble.com 來取得資訊是滿合理的作法。（而且這個時候尚未與任何行動裝置完成藍芽配對，因此也無法直接從手錶這一頭通知附近的行動裝置直接前往 go.getpebble.com 取得資訊。也許未來 Bluetooth SIG 可以創造一個這種應用的 profile。） 
 
<a href="http://photo.ernestchiang.com/p468785422/e74bef5a4"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="435" src="http://photo.ernestchiang.com/img/s4/v68/p1958671780-3.jpg" width="580" /></a>
 
 
期待下一篇 <Meet Pebble - Part 2>，下一步就準備要來和手機玩藍芽配對連線囉 :-) 
 
<a href="http://photo.ernestchiang.com/p468785422/e71925627"><img alt="Ernest Chiang Photography: Pebble Watch &emdash; " height="450" src="http://photo.ernestchiang.com/img/s10/v107/p1905415719-3.jpg" width="253" /></a>

Meet Pebble - Part 1

來一張側面圖作為這篇開箱文的序曲吧， Pebble （應該、可能、也許）是個許多人伴隨著其他相關關鍵字（ Crowdfunding , kickstarter ）而耳熟能詳的一項創新產品，但（應該、可能、也許）有些朋友還未聽聞，選這張側面圖，試著想從一個 *** 的角度來...

AWS IAM 讀書會筆記 -- User Guide Doc Version 20130403

AWS IAM 讀書會筆記 -- User Guide Doc Version 20130403

AWS IAM -- Notes of 20130403 Doc Version from Ernest Chiang 分享 Sep/25/2013 我們一群 (預計)考照團組成的讀書會 <AWS 八人壯士團> 的筆記投影片。這天除了 AWS IA...

Chateau de Callac 1993, Graves, France

<div class="separator" style="clear: both; text-align: center;">
<a href="http://blog.ernestchiang.com/2009/10/travel-in-bordeaux-2009.html"><img border="0" src="http://ernestchiang.com/image/bordeaux_title.jpg" /></a></div>
 
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<img src="http://ernestchiang.com/image/blog_wine_words.png" /></div>
 
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4QOPA4TzkCDXpFagBKiOzsqmZlWoBxEcJSwDoxBY1RFsLR2Dkn6b0LJFSDXd2vZTXGN1RlcHzksflH_oMCniTFlqlRWejoQe_dhyphenhyphenWOX6AdoRYDRD0-qyk2TRVx2lObJAW8Ge_BTXGjFc/s1600/2013-09-18+20.19.49.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="640" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi4QOPA4TzkCDXpFagBKiOzsqmZlWoBxEcJSwDoxBY1RFsLR2Dkn6b0LJFSDXd2vZTXGN1RlcHzksflH_oMCniTFlqlRWejoQe_dhyphenhyphenWOX6AdoRYDRD0-qyk2TRVx2lObJAW8Ge_BTXGjFc/s640/2013-09-18+20.19.49.jpg" width="480" /></a></div>
 
機緣遇到這支 Chateau de Callac 1993，發現之前一直沒有仔細留意的地名「<a href="http://en.wikipedia.org/wiki/Graves" target="_blank">Graves</a>」。整個酒標與瓶身有著濃濃的波爾多氣息，但在享用之時卻怎麼都想不起來 Graves 在哪兒。整支酒感覺不到太厚重的波爾多，但有著淡淡的順口，當下推測可能是 Merlot，加上一些些的 Ca 
bernet Sauvignon。我的功力只到這邊，但至少學長和 Yannick 教的葡萄品種沒有忘記太多 :p 
 
品嘗過後總想長點知識，回家翻書、翻 Google Maps 之後還是很納悶，加上查了 Wikipedia -- <a href="http://en.wikipedia.org/wiki/Graves" target="_blank">Graves</a> 這才發現原來在波爾多市的東南方處。(34 = Graves) 
 
<div class="separator" style="clear: both; text-align: center;">
<a href="http://upload.wikimedia.org/wikipedia/commons/thumb/c/cf/Weinbaugebiete-frankreich-bordeaux.png/687px-Weinbaugebiete-frankreich-bordeaux.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://upload.wikimedia.org/wikipedia/commons/thumb/c/cf/Weinbaugebiete-frankreich-bordeaux.png/687px-Weinbaugebiete-frankreich-bordeaux.png" /></a></div>
 
Graves 時常被翻譯成「格拉夫」， 這一區常見的紅葡萄品種包括Merlot、Cabernet Sauvignon、Cabernet Franc；白葡萄品種包括Semillon、Sauvignon Blanc、Muscadelle。 感覺是個很不起眼的小區，但還是暗藏了有列級酒莊 Château Haut-Brion。 
 
查了 <a href="http://www.exoc-international.com/images/stories/pdf/ownedproperties/rdcallac" target="_blank">EXOC</a> (PDF) 2006 的 Chateau de Callac 是 60% Merlot, 25% Cabernet Sauvignon, 15% Cabernet Franc。猜測 1993 年份應該也相差不遠吧。 
 
歡迎參觀我多年前的<a href="http://blog.ernestchiang.com/2009/10/travel-in-bordeaux-2009.html" target="_blank">法國波爾多酒莊遊記</a> :)

Chateau de Callac 1993, Graves, France

機緣遇到這支 Chateau de Callac 1993，發現之前一直沒有仔細留意的地名「 Graves 」。整個酒標與瓶身有著濃濃的波爾多氣息，但在享用之時卻怎麼都想不起來 Graves 在哪兒。整支酒感覺不到太厚重的波爾多，但有著淡淡的順口，當下推...

筆記：The Four Steps to the Epiphany (前言/第一章)

<div class="separator" style="clear: both; text-align: center;">
<a href="http://www.amazon.com/gp/product/0989200507/ref=as_li_tf_il?ie=UTF8&camp=1789&creative=9325&creativeASIN=0989200507&linkCode=as2&tag=ernesttalk-20"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-yiRBLWiKOT4CGy2qcszhOQJ0irUPkyEmppHsDDGzFQotrhDBPpAk97Wbgi6T7KLQB26e8Jreu82vL0rUdXpYFRcyX-6Ld9tsC9NaVZVdEZgb0l2zDJomh76ElZJP3KYBKWDC7L0tMeY/s320/book-the-four-steps-to-the-epiphany.jpg" width="237" /></a></div>
 
感謝強哥推薦這本書，我們即將開始一些<a href="https://bizlepro.hackpad.com/Reading-Notes-The-Four-Steps-to-the-Epiphany-BKFWdAZ7pGX" target="_blank">讀書分享</a>的聚會，因為我自己有訂一些閱讀進度目標（九月底前看完第一章）（第一章真的滿短的 XD），所以想說趁剛看完進度，記憶猶新，趕緊來整理讀書筆記。更多資訊，歡迎追蹤 <a href="https://bizlepro.hackpad.com/Reading-Notes-The-Four-Steps-to-the-Epiphany-BKFWdAZ7pGX" target="_blank">BizLePro 的讀書聚會</a>。 
 
這本書在 <a href="http://www.amazon.com/gp/product/0989200507/ref=as_li_tf_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0989200507&linkCode=as2&tag=ernesttalk-20">Amazon</a> 上面是排名前 10000 名的書籍。發表於 2005 年，最近 2013 年七月再版。更多資訊可以在 Amazon - <a href="http://www.amazon.com/gp/product/0989200507/ref=as_li_tf_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=0989200507&linkCode=as2&tag=ernesttalk-20">The Four Steps to the Epiphany</a><img alt="" border="0" height="1" src="http://ir-na.amazon-adsystem.com/e/ir?t=ernesttalk-20&l=as2&o=1&a=0989200507" style="border: none !important; margin: 0px !important;" width="1" />
 找到。這本書後來也影響了 <<a href="http://www.amazon.com/gp/product/B004J4XGN6/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B004J4XGN6&linkCode=as2&tag=ernesttalk-20" target="_blank">The Lean Startup</a>> 以及後來的 <<a href="http://www.amazon.com/gp/product/B006UKFFE0/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B006UKFFE0&linkCode=as2&tag=ernesttalk-20" target="_blank">Running Lean</a>> 這兩本書的發表。 
 
閱讀這本書從前言開始就很令我興奮， 
<ul>
<li>一來書中所題很多舉例和歸納都與這幾年的經歷互可對照，這幾年在腦中想的概念被作者的文字和圖表一點，一整個就通了，這種感覺非常像是幾年前腦袋塞了整個圖書館各種領域的資訊而透過 PMP 老師的一些大架構案例疏通腦袋一般、</li>
<li>二來作者舉例的方式非常著重具體事例的搭配，不會流於文字行書傳教，而是透過實際案例（可以從案例關鍵字中再另外自行搜尋查證擴充學習）來作說明，對於工程出身的我非常有說服力。</li>
</ul>
以下是筆記的部份，筆記會節錄一些我在書上畫的重點，加上一些我自己想到的想法。更多想法預計會在 BizLePro 小聚或讀書會上跟大家分享 :-) 筆記會加上英文版書籍中的頁碼，方便未來自己搜尋。 
 
前言「The Hero's Journey」 
<ul>
<li>(page iv) big company managers versus entrepreneurs, founders versus professional managers, engineering versus marketing, marketing versus sales, missed schedule issues, sales missing the plan, running out of money, raising new money.</li>
<li>(page iv) startups that survive the first few tough years do not follow the traditional product-centric launch model espoused by product managers or the venture capital community. Through trial and error, hiring and firing, successful startups all invent a parallel process to Product Development. In particular, the winners invent and live by a process of customer learning and discovery. I call this process "Customer Development," a sibling to "Product Development," and each and every startup that succeeds recapitulates it, knowingly or not.</li>
</ul>
 
簡介「Winners and Losers」 
<ul>
<li>(page viii) The difference between the winners and losers is simple. Products developed with senior management out in front of customers early and often - win. Products handed off to a sales and marketing organization that has only been tangentially involved in the new Product Development process lose. It's that simple.</li>
<li>I thought its audience would be small and its applicability would be narrow. I first believed that my readers would be startup entrepreneurs.</li>
</ul>
 
第一章「The Path to Disaster: The Product Development Model」 
<ul>
<li>開頭第一章先講：第一次把產品作爛就上手。從產品開發模型說起。</li>
<li>先舉了個例子「Webvan」作為範例，稍候的產品開發模型各個步驟都會以這個案例作解說。Webvan 在當年網路剛要開始累積泡沫的很早期，就擘畫出很遠大的願景，並且募得許多資金。（還沒賣出東西）</li>
<li>(page 1) Webvan stood out as one of the most electrifying new startups, with an idea that would potentially touch every household.</li>
<li>(page 1) What's more, most of their initial customers actually liked their service. Barely 24 months after the initial public offering, Webvan was bankrupt and out ofbusiness. What happened?</li>
<li>(page 1) Its failure to ask "Where Are the Customers?" illuminates how a tried-and-true model can lead even the best-funded, best-managed startup to disaster.</li>
<li>(page 2)  The Product Development Diagram</li>
<ul>
<li>這個模型我在閱讀時第一個想法是喔我知道啊，但作者先對這個模型做出說明，然後後面舉出十個點來挑戰這個模型對於新創公司、開發產品（或說把產品賣出去）所造成的困難。 </li>
<li>1. Concept/Seed</li>
<li>2. Product Development</li>
<li>3. Alpha/Beta Test</li>
<li>4. Launch/1st Ship</li>
</ul>
<li>(page 2) 1. Concept/Seed</li>
<li>(page 3) 2. Product Development</li>
<ul>
<li>prepare a Marketing Requirements Document (MRD) for Engineering. </li>
<li>我也在藍芽協會的工作組中看到 MRD 這個文件名稱。很認同，對於產品開發、工程開發來說，先盡可能定義市場的各種需求資訊，帶領接下來的開發人員試著去理解市場想要什麼的產品可以長得什麼模樣。 </li>
</ul>
<li>(page 4) 3. Alpha/Beta Test</li>
<li>(page 4) 4. Product Launch and 1st Customer Ship</li>
<li>(page 5) 那所以這樣的模型出了什麼問題？</li>
<ul>
<li>The first hint lies in its name; this is a Product Development model. Not a marketing model, not a sales hiring model, not a customer acquisition model, not even a financing model. Yet startup companies have traditionally used a Product Development model to manage and pace all these non-engineering activities. </li>
<li>嗯哈，這個模型的名稱就說明了一切。這是個「產品開發」模型，不是一個行銷模型、不是一個產品銷售模型、不是一個客戶獲取模型、更不是一個財務模型。然後我們新創公司現在試著使用這個產品開發模型來管理所有這些非工程的事務？</li>
<li>作者對這個模型提出了十個問題點，並在稍候提出解決方案。</li>
</ul>
<li>(page 5) 1. 客戶在哪裡？</li>
<ul>
<li>The greatest risk—and hence the greatest cause of failure—in startups is not in the development of the new product but in the development of customers and markets.</li>
</ul>
<li>(page 5) 2. 太過於關注首次客戶出貨時程</li>
<ul>
<li>"first customer ship" is only the date when Product Development thinks they are "finished" building the product. The first customer ship date does not mean the company understands its customers or how to market or sell to them. </li>
</ul>
<li>(page 6) 3. 強調「執行」，但不重視「學習」和「探索」</li>
<ul>
<li>Before we can sell a product, we have to ask and answer some very basic questions: What are the problems our product solves? Do customers perceive these problems as important or "must have?" If we're selling to businesses, who in a company has a problem our product could solve? If we are selling to consumers how do we reach them? How big is this problem? Who do we make the first sales call on? Who else has to approve the purchase? How many customers do we need to be profitable? What's the average order size?</li>
<li>For startups in a new market, these are not merely execution activities; they are learning and discovery activities critical to the company's success or failure.</li>
</ul>
<li>(page 7) 4. 缺少有意義的銷售、行銷、商業發展里程碑</li>
<ul>
<li>Simply put, a startup should focus on reaching a deep understanding of customers and their problems, discovering a repeatable road map of how they buy, and building a financial model that results in profitability.</li>
<li>The appropriate milestones measuring a startup's progress answers these questions: How well do we understand what problems customers have? How much will they pay to solve those problems? Do our product features solve these problems? Do we understand our customers' business? Do we understand the hierarchy of customer needs? Have we found visionary customers, ones who will buy our product early? Is our product a must-have for these customers? Do we understand the sales road map well enough to consistently sell the product? Do we understand what we need to be profitable? Are the sales and business plans realistic, scalable, and achievable? What do we do if our model turns out to be wrong?</li>
</ul>
<li>(page 8) 5. 使用產品開發模型應用在業務上</li>
<ul>
<li>"Build and they will come,"is not a strategy, it's a prayer.</li>
</ul>
<li>(page 9) 6. 使用產品開發模型應用在行銷上</li>
<li>(page 10) 7. 草率地擴張</li>
<li>(page 10) 8. 死亡螺旋：錯誤推出產品的代價</li>
<li>(page 12) 9. 不是所有新創組織、新創公司是相同的</li>
<ul>
<li>從市場與產品來看，作者粗分了以下四種基本的分類：</li>
<li>they are not all alike. One of the radical insights guiding this book is that startups fall into one of four basic categories:</li>
<ul>
<li>Bringing a new product into an existing market</li>
<li>Bringing a new product into a new market</li>
<li>Bringing a new product into an existing market and trying to resegment that market as a low-cost entrant</li>
<li>Bringing a new product into an existing market and trying to resegment that market as a niche entrant </li>
</ul>
</ul>
<li>(page 12) 10. 不真實的期待</li>
<li>所以除了產品開發模型之外，有別的替代方案嗎？</li>
<li>(page 13) 科技導入生命週期曲線 </li>
<ul>
<li>(page 14) 圖 1.4</li>
</ul>
<li>(page 15) 客戶開發模型：Common Sense Meets the Product Development Model</li>
<ul>
<li>(page 16) 對照 Webvan 公司的另一個範例公司是「Tesco」，Tesco 走的路和 Webvan 不同，不是一開始拿到很多的資金來啟動線上交易的機制，但藉由訂單實際</li>
<li>從第二章開始作者開始介紹客戶開發模型。</li>
<li>很慶幸的是，作者不是反對「產品開發模型」然後希望大家來支持他提出的「客戶開發模型」。作者讓我覺得是在提醒讀者多從不同的角度去同時思考每個面向的考量與作法。基於他的公平處理，讓我增加了想繼續閱讀這本書的想法 ...</li>
</ul>
</ul>
 期待繼續分享第二章的筆記和想法 :-) 
 
 
<a href="http://www.amazon.com/gp/product/0989200507/ref=as_li_tf_il?ie=UTF8&camp=1789&creative=9325&creativeASIN=0989200507&linkCode=as2&tag=ernesttalk-20"><img border="0" src="http://ws-na.amazon-adsystem.com/widgets/q?_encoding=UTF8&ASIN=0989200507&Format=_SL160_&ID=AsinImage&MarketPlace=US&ServiceVersion=20070822&WS=1&tag=ernesttalk-20" /></a><img alt="" border="0" height="1" src="http://ir-na.amazon-adsystem.com/e/ir?t=ernesttalk-20&l=as2&o=1&a=0989200507" style="border: none !important; margin: 0px !important;" width="1" />

筆記：The Four Steps to the Epiphany (前言/第一章)

感謝強哥推薦這本書，我們即將開始一些讀書分享的聚會，因為我自己有訂一些閱讀進度目標（九月底前看完第一章）（第一章真的滿短的 XD），所以想說趁剛看完進度，記憶猶新，趕緊來整理讀書筆記。更多資訊，歡迎追蹤 BizLePro 的讀書聚會。這本書在 Amazon 上...

Wikidata 初體驗筆記

<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyuvDz_SAnygmI7tAApSqo1Vc6cMkJqwYti7vx_egMDBX9nNKiphbgfIJVMKOmAVzsvJARveSA_frwxzLd_lbhlWOnuzgAYjUJn817LBPpx_Qb-pnHJj1zKQhw0VAM9nt6PbF1uMFRXk4/s1600/wikidata2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjyuvDz_SAnygmI7tAApSqo1Vc6cMkJqwYti7vx_egMDBX9nNKiphbgfIJVMKOmAVzsvJARveSA_frwxzLd_lbhlWOnuzgAYjUJn817LBPpx_Qb-pnHJj1zKQhw0VAM9nt6PbF1uMFRXk4/s1600/wikidata2.png" /></a></div>
 
 
（本篇文章，整理自我們在 <a href="http://coscup.org/2013/zh-tw/" target="_blank">COSCUP 2013</a> 之後一群人於 <a href="https://bizlepro.hackpad.com/About-BizLePro-5nhbpAtNve1" target="_blank">BizLePro</a> 聚會分享的內容。） 
 
今年在 <a href="http://coscup.org/2013/zh-tw/" target="_blank">COSCUP 2013</a> 聽到一場分享是關於 Wikidata，由來自德國 Wikidata 的 Nightrose (Lydia Pintscher) 所分享。這幾年也一直在構思如何整理一些瑣碎、片段的資訊並且從中萃取出資訊不對稱的資料（或資訊、或行動方案），也許未來可以做成「創業題目產生器」之類的玩意兒，或是給投資人使用的新創公司分析報告產生器之類的東西。（先暫停嘴砲模式，進入 Wikidata 的介紹吧） 
 
滿愛這種開放式資訊分享的架構跟想法，從 Wikipedia 到 Wikidata，在收集到越來越多的資料後，通常會遇到過往（開頭時）設計的資料庫結構不敷使用或是有新的應用需求而需要作調整。Wikidata 也是基於多年的 Wikipedia 運作經驗累積得到的經驗值之後轉化的產物之一。 
 
我之前還沒找到 Lydia 在網路上的投影片。後來有找到了：<a href="https://docs.google.com/presentation/d/1UIwjt09frZoBVYFPidF0dRNrGWZFqzpHVKhnRMNSuyw/edit#slide=id.p" target="_blank">在這裡</a>。下面則是她同事在 slideshare 上面類似內容的投影片（因為可以嵌入，所以，哈）。 
 
有趣的是投影片中有一些世界地圖的照片，是各個語系在世界各地使用者取用該語系的地理位置分布狀況。可以看出來英文的分布最廣泛，然後看到的法文也滿廣的，但是其他語系就越來越侷限存取位置（也許也有關於存取量）。但如果知識或資訊的取用，不會被語言所隔閡，那也許可以創造其他的可能性。 
 
<iframe allowfullscreen="" frameborder="0" height="356" marginheight="0" marginwidth="0" mozallowfullscreen="" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/21900009" style="border-width: 1px 1px 0; border: 1px solid #CCC; margin-bottom: 5px;" webkitallowfullscreen="" width="427"> </iframe> 
<div style="margin-bottom: 5px;">
 <a href="https://www.slideshare.net/anjeve/2013-0523-wikidata" target="_blank" title="Wikidata - The free knowledge base that anyone can edit (1st Linked Data Meetup Malmö)">Wikidata - The free knowledge base that anyone can edit (1st Linked Data Meetup Malmö)</a> from <a href="http://www.slideshare.net/anjeve" target="_blank">anjeve</a> </div>
 
我自己的理解是：Wikidata 的開始就是想要作些改變，讓資料與資料之間的關係作個整理，從「關係」中可以取得「資訊」，進而使用這些資訊再做處理，例如翻譯成各種語系，或是取用現成的翻譯可以直接整理 (render) 出資訊呈現結果。（我延伸想到的專案是 <a href="https://popcorn.webmaker.org/" target="_blank">Mozilla Popcorn</a> 專案。） 
 
現場 Lydia 以「台北」作為示範：<a href="http://www.wikidata.org/wiki/Q1867">http://www.wikidata.org/wiki/Q1867</a> 
<ul>
<li>Q1867 是這個條目（或稱項目）的一個編號。數字大小本身應該是依照建議的順序排列。應該會把重點放在項目與項目之間的關聯性。</li>
<li>可以從中看出來跟「台北」有關的姊妹市 (twin city) 有哪些等等關聯資訊。（現場 Lydia 還直呼，哇！這麼多姊妹市！XD）</li>
</ul>
Wikidata 保持跟 Wikipedia 一樣的開放精神，大家都可以新增、編輯。 
 
這裡有一張動態的圖，以世界地圖的亮點，紀錄了 Wikidata 的成長：<a href="https://commons.wikimedia.org/wiki/User:Denny/Wikidata_growth">https://commons.wikimedia.org/wiki/User:Denny/Wikidata_growth</a> 
 
藉由 Wikidata API query 可以整理出一些有趣的資訊，例如： 
<ul>
<li><a href="http://simia.net/treeoflife/">http://simia.net/treeoflife/</a></li>
<li><a href="http://toolserver.org/~magnus/">http://toolserver.org/~magnus/</a>  (很多 query 範例)</li>
<li><a href="http://tools.wmflabs.org/reasonator/?q=Q42">http://tools.wmflabs.org/reasonator/?q=Q42</a>  (重新排版呈現 Q42 這個條目)</li>
<li><a href="http://toolserver.org/~magnus/thetalkpage/">http://toolserver.org/~magnus/thetalkpage/</a>  (我覺得這個最有趣，可以用對話的方式問問題，然後機器人會去查 wikidata 的資料作互動。想不到要問什麼問題的話，也有現成的範例問題在頁面上可以直接玩。)</li>
</ul>
其他延伸閱讀，可以直接參觀 <a href="http://www.wikidata.org/" target="_blank">Wikidata</a> 資料，或是 Graph 資料庫作為延伸閱讀。

Wikidata 初體驗筆記

（本篇文章，整理自我們在 COSCUP 2013 之後一群人於 BizLePro 聚會分享的內容。）今年在 COSCUP 2013 聽到一場分享是關於 Wikidata，由來自德國 Wikidata 的 Nightrose (Lydia Pintscher) ...

Raspberry Pi 在家動手玩

<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjt7TwRxvQZmUiV1OPGUj9f-sSYZnGoVB4vGec34xOXetYdNej5YRaUy-4-uMHSyGbEUHiYr_nb2fgE0JEJ6LIKK4KXj6rpmduOkdULNFuLwg2LwKsiWuTH7nDHlXKNNLohDr_vemNYQAU/s1600/p1752049898-3.jpg" imageanchor="1"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjt7TwRxvQZmUiV1OPGUj9f-sSYZnGoVB4vGec34xOXetYdNej5YRaUy-4-uMHSyGbEUHiYr_nb2fgE0JEJ6LIKK4KXj6rpmduOkdULNFuLwg2LwKsiWuTH7nDHlXKNNLohDr_vemNYQAU/s320/p1752049898-3.jpg" /></a> 
 
每年 COSCUP 之後都可以引發很多熱血（甚至沸騰）的事情，今年的贊助商攤位都非常精彩，身為今年銷售組的一員，也跑去支持了一下現場的贊助商們 :-) 在其中幾攤找到了關於 Raspberry Pi 以及其他電路板子的有趣內容，也該來把之前就擱在家裡的 Raspberry Pi (model B) 挖出來玩一下。 
 
先是花了兩天晚上把 <a href="http://en.wikipedia.org/wiki/Eben_Upton" target="_blank">Eben Upton</a> 與 Gareth Halfacree 合著的 <Raspberry Pi 使用者手冊> 大略翻過一次，擬定採買計畫，計畫總是趕不上變化，在路過 Costco 的時候就帶了兩張 SanDisk 的 SD 卡回家，準備上工。其他的線和鍵盤滑鼠，應該家裡湊一湊可以組得起來，來玩玩看吧 :) 
 
之前和同事以及家人團購時，有選購塑膠外殼（也可以找厚紙板製作，更有味道！） 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e686e28ea"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v90/p1752049898-3.jpg" width="580" /></a> 
SD Card 有個清單可以作為購買或借用時的參考，有許多人將測試過的結果回報到這裡 - <a href="http://elinux.org/RPi_SD_cards">http://elinux.org/RPi_SD_cards</a> （往下找「Working / Non-working SD cards」段落，會看到一個很長的表格，有紅色和綠色說 ok 不 ok），如果你有發現新的卡可以用或不能用，都歡迎在這一頁作回報喔！取之於社群，回饋於社群，人人都可以做出一點點貢獻 :-) 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e6cafc7b8"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v97/p1823459256-3.jpg" width="580" /></a> 
 
有了 SD card 之後（或是之前或同時），需要下載一個影像檔案 (image file) 準備放進去（寫入）SD card 裡頭，然後就可準備插電、插網路線、接上螢幕和鍵盤來玩開機囉。 
 
剛起步的影像檔可以在 Raspberry Pi 官方網站上找「Downloads」專頁來下載。我想從頭玩看看，所以選擇了「Raw Images」裡頭的「Raspbian “wheezy”」來試試看。另一個我覺得滿有趣的、可以作為多媒體中心的是「<a href="http://www.raspbmc.com/wiki/user/os-x-linux-installation/" target="_blank">Raspbmc</a>」，大家也許也會想試試看。（我是因為這樣所以原本就有打算準備兩張 SD cards。目標是讓大朋友小朋友都能簡單上手這台小電腦 :） 
 
大家一起合體之後： 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e6564a820"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v93/p1701095456-3.jpg" width="580" /></a> 
 
照片中右上角的那條白色線頭，就是電源線。準備接上囉！ 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e6f2630f4"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s9/v87/p1864773876-3.jpg" width="580" /></a> 
 
這種樂趣真的是當年無法想像的！（當年跟著我爸用慢慢的電話線 modem 把 Linux 抓下來後分裝到很多片小磁碟片中，然後慢慢安裝，過程中藥一直翻書找資料解決問題。今天這台 Pi 只要燒好影像檔，接上四條線和一張 SD 卡，噗，開機了！） 
 
出門前多準備了一張 SD card 燒錄了「<a href="http://www.raspbmc.com/wiki/user/os-x-linux-installation/" target="_blank">Raspbmc</a>」這個多媒體中心。以下先貼一些「<a href="http://www.raspbmc.com/wiki/user/os-x-linux-installation/" target="_blank">Raspbmc</a>」的圖片分享吧！可以還算方便地在大螢幕看 TED 或 Youtube。還在測試 AirPlay 要怎麼跑起來。 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e67c4c238"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v110/p1740948024-3.jpg" width="580" /></a> 
 
第一次啟動需要花一些時間，泡杯咖啡來喝吧 :) 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e660a7bd1"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v108/p1711963089-3.jpg" width="580" /></a> 
 
首次啟動可以選擇介面語言。 
 
<a href="http://photo.ernestchiang.com/raspberry-pi/e6f790497"><img alt="Ernest Chiang Photography: Raspberry Pi &emdash; " height="435" src="http://photo.ernestchiang.com/img/s10/v112/p1870202007-3.jpg" width="580" /></a> 
 
四處逛逛，玩一下設定囉 :-) 
 
「Raspbian “wheezy”」再來另外找時間測試看看 :-) 
 
Enjoy your Raspberry Pi!

Raspberry Pi 在家動手玩

每年 COSCUP 之後都可以引發很多熱血（甚至沸騰）的事情，今年的贊助商攤位都非常精彩，身為今年銷售組的一員，也跑去支持了一下現場的贊助商們 :-) 在其中幾攤找到了關於 Raspberry Pi 以及其他電路板子的有趣內容，也該來把之前就擱在家裡的 Raspberry P...