Skip to main content

2008/09/01

今天

根據  新學期、新希望  的內容來評分:

早餐吃麥當勞,午晚餐的內容綜合來說是太陽餅,算是省錢的。不過,這樣應該不算均衡。

早上 7:30 有起來一次,後來又小睡了一下,晚上有望 1:40 睡覺。

時間利用還滿充實的,沒有明顯自覺的浪費時間(這點才是最危險的吧???)。

有運動,但是沒有念英、日文。

沒唸 CS、Technique、課外書。

特別

今天第一次自己搭公車,成功的從公館搭到台大醫院站,算是個大突破 ^-^。

晚上去照了護照需要的相片,也買了一件有領子的上衣,以及運動衣褲,花費不少。

去金石堂買了 CNN 互動英語雜誌,希望明天開始可以步上正軌,天天聽英文。另外也買了一本簡單的筆記本,開始練習自己動筆寫日記,訓練文思,也順便練字。

今天有看著鏡中的自己對「他」精神喊話:「加油!加油!加油!」。

感動

把 2002 年台中一中暑期巡迴音樂會「對話」中的 Noah's Ark 轉成 mp3 放在電腦裡聽,重新找回當時的寂靜、瘋狂、寧靜、可愛、壯闊、安祥。

對明天的期望

早睡早起,三餐正常,閱讀正常(今天幾乎沒有讀書)。

Comments

Popular posts from this blog

Setting MySQL to Use UTF-8 on MAMP (MySQL 5.5.9, or 5+)

I wanted to setup MySQL to use utf-8 on the MAMP installation on my Mac. I tried the instructions from this article: http://cameronyule.com/2008/07/configuring-mysql-to-use-utf-8/ However, I kept getting error messages that are similar to this one [ERROR] /Applications/MAMP/Library/bin/mysqld: unknown variable 'default-collation=utf8_general_ci' I did some search and realized that several variables are deprecated. Reference: http://dev.mysql.com/doc/refman/5.1/en/server-options.html Therefore, I added the following lines into /Applications/MAMP/conf/my.cnf [mysql] character-set-server=utf8 [client] character-set-server=utf8 [mysqld] character-set-server=utf8 collation-server=utf8_general_ci init-connect='SET NAMES utf8' I restarted the server and mysql run successfully with relevant variables being set correctly. In the "Variables" tab under phpMyAdmin interface (ex. http://localhost:8888/MAMP/?language=English) character set c...

ngrok, a service to help you get a public URL for your local webserver

If you are looking for options to test your web app hosted on your own machine (e.g., laptop) remotely with someone, I recommend using a service called ngrok. https://ngrok.com/ It has many usages, but in the context of testing an app hosted on your own machine, the most important part is giving you a public URL that will redirect all the requests to your local webserver (e.g., Apache, Nginx, or whatever server you are running). You can give this URL to a testing participant without the need to host the app on a remote server. For instance, if you are testing your app using a sever on your machine, typically you can access your app in a URL like:  http://localhost:3000/?study=11 Using ngrok, you will have a dynamically generated URL like the following: https://3ebe3c019867.ngrok.io/ The service will redirect requests to https://3ebe3c019867.ngrok.io to http://localhost:3000 You can then share the following link with your testing participant for the participant to use your app. http...

Use NVM to handle Angular-Node.js incompatibility (e.g., Uncaught SyntaxError: Unexpected token 'export')

Overview If you are a fullstack developer, the chances are that you will be creating multiple frontend or Node.js projects along the way. When you are creating new projects using the newest version of the cli (command-line interface) of a particular framework, you might be asked to install the most updated version of Node.js in order to utilize the newest feature. This might involve upgrading your Node.js version, which might not be compatible with other existing projects (e.g., using Angular) you have created before. A potential solution is to use nvm (Node Version Manager) to install multiple versions of Node.js and use a particular version of the Node.js to install the proper version of the cli (e.g., Angular-CLI) that can be used to manage a particular project. Here I will use a problem I run into to explain how to solve it. Problem There is a compatibility issue between Node.js and angular.js. For instance, I run into an error when I was using an incompatible version of Node.js ...