aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZhiming Wang <zmwangx@gmail.com>2015-05-29 20:54:06 -0700
committerZhiming Wang <zmwangx@gmail.com>2015-05-29 20:54:06 -0700
commitdb1d86416a33a0fc4fc0363def99b094b14a29e3 (patch)
treea0a48dec2c3c2e6af6d72ecb1468d622eeb9d90b
parentfe7bf5bf629064886724027d499c5b04fb69afe2 (diff)
downloadmy_new_personal_website-db1d86416a33a0fc4fc0363def99b094b14a29e3.tar.xz
my_new_personal_website-db1d86416a33a0fc4fc0363def99b094b14a29e3.zip
update about me
-rw-r--r--source/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/source/index.md b/source/index.md
index 411dd2e6..5c93a54b 100644
--- a/source/index.md
+++ b/source/index.md
@@ -5,6 +5,6 @@ title: dl? cmplnts?
I am an undergrad at Stanford (junior as of May 2015) studying mathematics and theoretical physics. I enjoy coding in my spare time, for fun and profit (getting things done). I am lazy in general so I try to automate things as much as possible.
-My first programming language was Pascal and I consider C my mother tongue, but recently I write my code in Python or Bash (non-interactive) most of the time. My operating system is OS X, my text editor is Emacs, my interactive shell is Zsh, my package manager is Homebrew, and my default browser (at the moment — it changes a lot) is Google Chrome. I use four-space indents. My public key is [here](/key.html). What else is there to tell?
+My first programming language was Pascal and I consider C my mother tongue, but recently I write most of my stuff in Python or non-interactive Bash, and I'm slowly moving to Zsh even for non-interactive shell scripting. My operating system is OS X, my text editor is Emacs, my interactive shell is Zsh, my package manager is Homebrew, and my default browser (at the moment — it changes a lot) is Google Chrome. I use four-space indents when the target language has no highly established convention that says otherwise. My public key is [here](/key.html). What else is there to tell?
This blog could be about anything, but most of the stuff should be technical. Oh yes, this blog is fully open source, down to how image assets were generated. All tools necessary for reproducing this blog are either in or documented in [the source branch](https://github.com/zmwangx/zmwangx.github.io/tree/source) of [zmwangx/zmwangx.github.io](https://github.com/zmwangx/zmwangx.github.io).