2009.02.04 New Words

involuntary adj. 不受意志控制的, 不由自主的

blush v. 臉紅

disclose v. 透露, 揭露

wrongdoing n. 做錯事, 罪行

conceal v. 隱藏, 隱瞞

immerse v. 使浸沒

disapprove v. 不贊成, 不同意

spontaneous adj. 自發的

indispensable adj. 必需的, 不可缺少的

mainly focus on 主要集中於

except for 除了 ... 之外

rather than 並非

inclusive of 包括

face the music 認錯受罰; 勇於面對現實

make believe 假裝

know the ropes 知道 ... 的訣竅

plat it cool 故作鎮定

    play it safe    謹慎行事, 穩紮穩打

    play dead    裝死

    play dumb    裝笨

self-conscious adj. 不自然的; 怕難為情的

    subconscious    潛意識的

    fashion-conscious    講究時髦的

    health-conscious    有健康意識的

    environmentally-conscious    有環保意識的

cool

    (as) cool as a cucumber    十分鎮靜

    keep a cool head    保持頭腦冷靜

    cool down    冷靜下來; 冷卻下來

    lose sb's cool    失去自制而激動起來

around 大約

    over    超過

    amid    在 ... 當中

    among    在 ... 之間, 在 ... 之中

Comments

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 ...

Aventurine Yao

Search This Blog