Just for fun.

Count and show keyboard strokes.

Keyboard Strokes

Hope you enjoy it.

For anyone who already had some programming experience and wants to play with Ruby but somehow impeded by, or just fail to find any logics but coarse information in the so called Ruby Handbook, Koans may be a amazing alternative for you to try.

I’m always wandering that, as a dynamic and reflective programming language, Ruby is fully capable to explains itself clearly, without any chunky handbook. Ruby is designed for programmer productivity and fun, and with this purpose it’s syntaxs and method names are meticulously considered to be intuitive, showing the similar form of nature language, which thousands of elegant Ruby one liners assured. I’m gonna show you an example.

1 # to make every word in a paragraph capitalized
2 @paragraph.split.map!(&:capitalize).join(' ')
3 
4 # a shorter and more skillful approach
5 @paragraph.gsub!(/\S+/,&:capitalize)

From my perspective, instigating somebody to reading the alleged Ruby Handbook is ruining the language, as Jim Weirich and Joe O’Brien, the author of Koans, may agree with. However, they didn’t just hold this point of view, but ultimately build up this helper, which earned my respect spontaneously.

So, if I’ve already attracted your attending, and you are ready for this journey. Then follow me, I’ll point out a path to enlightenment that leading you to cross the Gate of Ruby and witness it’s inner beauty.

前言

搭好博客之后,才觉得腾出时间来写点博客有多不容易。说好的对GTD的第二次总结迟迟没有结果,VisualMath的计划还根本就看不到影子,而自己的精力感觉已经油尽灯枯了。请容我惯例掀一下桌子。

( ╯#-_-)╯┻━┻

好了,言归正传。

很早就想写一点关于VIM的文章,也算是整理一下自己的使用心得。由于沉迷VIM邪教已久,现在早已不能自拔,丧心病狂的把各种IDE,甚至Chrome上都装上了VIM插件,偶尔用Pages写个报告都会习惯性打几个 :w 。有时候想想,因为接触到了VIM,在磕磕碰碰的使用的过程中,莫名其妙的了解到了最初的计算机文化,了解到了一群神人所创造的,隐藏在黑底白字中的典藏,岂不美哉。

接触VIM还是学习ICS的时候,为了避免一遍又一遍的上传代码到远端服务器,狠下心来直接在上面打开了VIM。然后对照着网上的各种教程,以大概每十秒钟一个误操作的速度,写好了第一个ICS的Lab。而现在,前前后后用VIM也大概有一年半了,现在渐渐对非VIM的编辑方式感到了不习惯。感觉隐隐约约触碰到了VIM哲学的本质,斗胆一试,希望能够通过文字表达出来。

Makefile 规则

首先推荐一个非常好的资源GNU make中文手册,上面的讲解非常详细,已经超出了理解Nachos系统Makefile的需求。

make是构建和管理工程的非常便利的工具,使用Makefile作为自己的配置文件,在合理配置的条件下,能够实现自动化编译,因此,也成为Linux程序员的必修课。作为配置文件,Makefile中必须包括所有描述工程链接,编译甚至清理工作的详细解释。学习Makefile的语法,可以说是使用make工具的基础,也是重点。

Preface

最近读了David Allen所著的<Getting Things Done, The Art of Stress-Free Productivity>,其中提到的GTD理论,我个人感觉受到了相当的启发。在网上一看,才发现已经有了相当大量的人在研究和按照自己的节奏部署和执行这样一套理论。

想到自己现阶段的处境,感觉离工作也不远了,正好也是寒假,了解一下也不是坏事儿( (╯‵□′)╯︵┻━┻你丫又忘了你的GRE了吗? )。退一步说,以一个大学生的角度来说,尤其是我这种整天不知道在干什么的人,了解一下GTD对提高自己的效率也可能会有些帮助。

由于内容很大,再加上我自己也是一知半解,因此我决定按照学习的进度,大概写4篇关于GTD的Post,这是第一篇,主要总结一下GTD理论及其目的。后面的Post可能会包含部署和实践的方法,具体工具的使用体会,根据自身不同的情况做出不同的调节等等。不过要看学习的进度了。

嘛,╮(╯▽╰)╭,以下内容均为个人意见,欢迎留言拍脸。

Why GTD

首先要说的是GTD存在的理由,为什么我们需要这样一个理论来引导我们完成事务?简单来说就是:

我们需要做的事情太多了,以至于影响到了我们正在做的事情。

说的有些笼统,我们不妨举一个例子。

The second assignment stroke, inside I provided a powerful tool to explore the dataset of a migrant event.

Migrant Visualization

Hope you will like it~

Boss gave us one week to do a news visualization sketch, but he forgot it himself. It is a little upset to throw it into trash, so I put it here.

News Visualization

Hope you enjoy it.

This is an assignment for visualization course, inside I gave out a quantitative relationship of airelines of the world.

Airline visualization

Hope you will like it~

Just now I finished the barely-running version of this little project, seriously using Ruby(actually MacRuby, I will mention it later) for the first time.

Althrough I fell in love with Ruby the first time I saw it, I didn’t realize that writting with Ruby is such a pleasure. A GUI program using multithread tech and carefully handling exceptions is written in only 200+ lines, which seems impossible to Objective-C(I should have used it if I didn’t see MacRuby). Before talking about the details, I remind you that the project is avaliable in my github repo. Feel free to give me some feedbacks.

Background

In 2003, just two years after the online encyclopedia’s birth, Wikipedia was still not well known, and among those aware of it there was serious skepticism about its open authorship model. Researcher Martin Wattenberg and Fernanda Viégas felt some of this skepticism themselves, yet many of the articles were interesting and helpful. To find out how was such a haphazard process yielding a quality product and other related questions, they decided to investigate. They did a lot of works and most of them are masterpieces. I’ll focus mainly on the History Flow part which I think is beautiful and useful.