Picture
So you are:

A tech guru
A perfect coder, tester or IT specialist
Frustrated by the 9-5 routine work that's wasting your highly developed skills
 Looking for a highly qualified team 
Always looking for an opportunity to make maximized use of your tech potential
Sure that your coding skill will bring BIG financial rewards

You are likely to be interested in joining Banckle, because we:

Are skilled, professional, passionate, and FUNNY programmers
Have a boss who is willing to PAY :)
Have an online meeting product that's said to be even better in some aspect than the former leader in the field
Do java server, windows clients, iphone application, mac application, ajax, flash.... pretty many technologies you can choose (No, we don't mean to use so many technologies - we have to)
Have a growing, growing and growing number of customers


You probably want to know more about banckle here at: http://www.banckle.com
And we won't know about you unless you email you resume to: [email protected]
 
Picture
做人最要紧的就是开心。每个兴奋的大脑都在随时准备着看到些令自己开心的东西,比如,,和。(不再排比举例)。由于老天爷的眷顾,每个人都得到了一些快乐,对此表示祝贺。

但是显然的,有些人日子过得爽了些,好事自动上门;有些人则不太轻松,每天茫然追逐,失魂落魄,活得很累。我现在就是典型的后者。对于前一种成功人士,我也从一个失败者的角度认真观察,活得少许结论,聊以记录,留待后用。

。。。。。。。。。。。。。。。。。。。。。。。
。。。。。。。。。。。。。。。。。。。。。。。
。。。。。。。。。。。。。。。。。。。。。。。

分析无聊,直接上结论:

我们每天为了活得更开心点,会做很多事情,其中有些快乐是很容易就过去了的,有些则会让生活方式产生改变,继而创造源源不断的快乐。所以要根据自己的具体情况有所选择,不要像没头的苍蝇是的,问到点腊肉的味道就使劲儿钻,很浪费时间。

柴九哥说的好:人生有多少个十年,做人最要紧的就是痛快!
 
Picture
Well, it's like this, sometimes you find something frustrating in work, it's so stressful - you'll have to work a lot on something but what it produces is not that rewarding, OH SHIT!!!! This damn work!

But that's wrong, you are wrong. Think in this way, if it doesn't work and it cost time, be patient, cheers for steps instead of goal being achieved. Everything else is just as usual. And one part is malfunctioning. It's no big problem! There'll always be some big projects that requires long work. Be faced, you can't always skip that dirty part.

When you've made this clear, think back about this situation, not that bad, aha?
 
Picture
which makes me very unhappy... today is another ordinary day in this busy city, today is the special day on which my loneliness doubled. this might because i'm just back from home, where people share with me.

i get temporiry friends, then loose them.

i'm sad

this is a freaking unfair world for me, i'm surrounded with people who claims to enjoyed this world. it increases the contrast between i and them. when i say this i'm afraid because what i say shows that i'm weak and mentally unhealthy and as a reasult add the difficult people communicate with me.

i pretend, to be energetic, exited, reasonable, while the truth is i'm unsure, scared.

i don't figure out how this world works.
 
Picture

     (1)

     漫天的鹅毛雪片,整个山已经被雪包裹起来。
    
     笃笃笃的木鱼声
    
     “汪汪汪。。。。", Mat的狗急匆匆的跑了过来。
    
     tactoth很少这么急匆匆的。
    
     Mat是一个这座山上普通的一个和尚。tactoth是这座上上普通的一条狗。”tactoth" 也是住持的名字。
    
     Mat以前并不是特别喜欢住持,于是热衷戏谑的他给自己的狗起了这样一个名字。
    
     住持后来知道了这件事情,他也没说什么。
     现在的情况是,tactoth看上去很急,显然他发现了什么。mat显然不喜欢清修,他的兴致一下子集中在tactoth的发现上了。
    
     tactoth带mat到了后庙的小路上。mat发现tactoth所指的方向有一个趴着的女人。
     这是一个美丽的女人,不算单薄的黑色羽绒大衣没能遮住他匀称的背部。雪花飘在她金色的卷发上。她的脸侧向左边,于是他看到了她长长的上翘的睫毛,直挺的鼻梁,红润的脣,和光滑的透出淡淡血色的脸颊。
    
     她显然受伤了,同样显然的,她还活着。

Picture

     (2)
     mat习惯的一边在寒风中哆嗦着,一边敲打着木鱼。所以Lily——Mat现在已经知道那个女人叫Lily——听到的木鱼声有些杂乱无章。
     mat的木门‘咯吱’的响了一声,他抬起头来,看到Lily手里拿着一条厚大的围巾。看到mat仰起来的脸,她笑了一下。她最近恢复的挺好。她什么都没说,他也什么都没说,他的脖子伸的像一条鹅,她给他戴上了那条围巾。
    
     她的眼睛明亮又有种朦胧的温暖,他的笑容无声却热烈。
    
     她出去了,木鱼声变得整齐,响亮了。
    
     (3)
    
     这是做风雪覆盖的寺庙,没有人会去庆祝生日(据说庙规里面有一条明令禁止)。
    
     ‘生日快乐!’
     Mat手有点笨。他做的蛋糕很大,上面堆满了松子,奶油,巧克力,葡萄干。。。总之在Lily的眼里这不算是美观的组合,虽然东西很多。
    
    
     她一下子就很听话的快乐了,就像火车“噗”地划开那样神奇。

Picture
     (4)
    
     tactoth——庙里的住持,听到咚咚的敲门声。
    
     “进来!”,tactoth装模作样的继续闭目沉思着,仿佛他脑子里真的有丰富的,从经书中得到的世界。
    
     “您好,我是Coco警官”。
    
     这种人很麻烦,每次来了警察,庙里都会很麻烦。
    
     “这方面我不大帮得上忙。。。”。
    
     “你只要回答几个问题就可以了”
    
     “庙了最近有没有来一个。。。很多人都会说美丽的女人?”
    
     “没有”,tactoth继续闭目养神。
    
     ‘主席前几天遇刺了。。。。’
    
     tactoth不明白这和他有什么关系。
    
     Coco是一个聪明有没耐心的人,他说:
    
     ”你可以不认真回答我的问题,我只是想提醒你,如果这里的和尚都被那个女人干掉了,我没什么好难过的“。
    
     tactoth吃力的咽了口唾沫,Coco露出轻蔑的微笑,心满意足的出去了。
    
     窗外,mat装作若无其事的走开了,就好像他刚才什么都没有偷听到一样。

Picture

     (5)
    
     Mat使劲的抓着Lily的双臂:“你告诉我,你到底是谁。。。为什么,为什么你总是不告诉我你是谁!”
    
     Lily听着他男性胸膛中发出的急躁的声音,虽然他们已经相当熟悉,却依旧多少有点欣赏。她集中了一下精神,这让她回到了消极的状态。
    
     “亲爱的,你以为你真的会爱我的一切吗?”这是一个她想了很久的问题。
    
     “我永远都不会爱你的一切,但是我会接受你的一切”。这是一个他想了很久的答案。
     其实这不是她希望的答案,她是一个美丽的女人,她希望自己的一切都是美丽的,她只想拥有爱,她知道自己需要理解,包容,同情。。。但是这多少让她有些不自在。
    
     ”把手举起!“
    
     Coco警官急匆匆的冲了过来。
     ”不要过来."Lily一把卡住Mat的脖子,慢慢的移动到山上游客们放置降落伞的地方,随手拿了两个降落伞,单手帮自己和Mat戴好了降落伞。往山崖边走了过去。
    
     Coco警官由于没有处理过这种胁迫者和人质是情侣的情况的经验,况且又不方便上Google查,所以一时也没什么办法。
    
     他们走到崖边上,纵身跳了下去。
    
     Coco走到崖边上。他看到两把张开的降落伞,如蝴蝶美丽的双翼,像云雾更深处进去了。
    
     Coco枪法还行,可是由于被蝴蝶翅膀般的降落伞挡住,所以搞不清楚那个是人质。算了!其实他也不是很关心主席的事情(有时候发现自己在煞有介事的拿主席遇刺的事情来吓唬别人,自己就有点想笑)。

 
令人不得不想起皇帝的新装。
 
Picture
美好的一天应该是不同的,清新的早晨,活力的上午,兴高采烈的午餐,闲适的下午,夕阳中长长的影子笼罩的黄昏。美好的一年也应该是不同的,春花秋月夏日冬雪。这就是我们最原始的来自自然的快乐,豪不渲染却沁人心脾。

可是这种快乐现在离我们很远了,我们很少见到草和阳光,更不谈羽毛,昆虫,河流,树木.... 大多数时候,我们看到的是屏幕,其实也五彩缤纷的,可是我们从来都没有体验到那种不同景致应时而至的节律感。如同在迷宫,虽然变化多端,其实如出一辙。时间一久,就难免让人心生烦躁。

所以得为这件事情想想办法。
 
Picture
就拿想去哪儿玩这样的事情来说吧,他不应该是一个需要去精心策划的事情。相反的,应该是一件随意的,尽可能多的,无时无处不可的事情。即便你想通过玩来获得什么收获,也应该是不能提前计划的那种。因为期待的本来就是“意料之外的收获”,那又为什么要去“意料”呢?

获得交流也不必这么麻烦,既然想要的是被人听到和听到别人,那么就去一个大家都去的地方,说出自己想说的,听听别人有什么主意?相信在两个都生活在地球上,都长着鼻子眼睛嘴巴,都琢磨着怎么赚钱,都梦想着如何幸福的人之间,总会有共同的话题。当谈论了这些话题后,人和人就会有些互相的印象,那不久好了吗?

有些愚蠢的想法也大可分享,即便有人觉得你弱智。基本上每个人这一生都会被认为弱智无数次——想想这样的情况,有时候你确信无疑这事情值得一讲,结果被人当成弱智——这说明人和人虽然有相似性,有时候差别还是蛮大的。保不准你觉得说出来恐怕显得弱智的某事情,也是其他某人觉得说出来太弱智,但心里却是那样想的。所以当你这么和他讲了的时候,他跳了起来:“知音啊!”。

大多数事情都不必这么麻烦,不必制定规则以便想个操作员那样在余生遵守。如果你为一件事情精心策划了特别久,以至于扰乱了很多你以前的精心策划,那么你应该想想,这样自相矛盾的精心策划,还要吞噬掉多少宝贵的时间?

大多数时候,不要给自己这么大压力,觉得自己现在在这件鸡毛蒜皮的事情上的一些细节,会影响今后的人生。永远相信自己以后的智慧远胜现在,人是充满活力的,智慧的,向上的,最重要的工具。
 
Picture
With my new BB in hand I made a ambition to "work everywhere". I tried different productivity tools on my BB but .... unfortunately, none of them seems have worked well for me, typing some text as long as those in this article on a BB i'll have to spend 10 minutes or so, no matter how feature rich the application is. Finally I find the most useful feature of BB is still SMS and making calls, plus the web browser which occasionally guides me how to go to some place.

Then I realized that a cellphone is, no matter how powerful the producer say it is, always a cellphone. It's always an addition to your PC in case you are without it. It's designed to make it possible for you to access a piece of information, not to make it efficient. So for your serious work, it's simply not recommended that you spend too much time doing it on a BB, it's totally a waste of time.

And the best tool for me is still my PC and my small note book (yes a PAPER one) that's always with me. I've been so used to search for file with CTRL + WIN + S, look up a word with ALT + L, taking quick note with CTRL + ALT + N, and so many ... what without them I feel the world is just BIG, HEAVY, AWKWARD. And with my notebook I can write everywhere, draw lines, draw smile, draw whatever wherever whenever, it's just awesome!

Conclusion:
Looking for productivity tools for BB is as stupid as looking for good taste from ... some medicine.
How you do matters, much more then how long you do.

 
Recently I found some very interest discussion on Java performance, actually title of this post is from a question on stack exchange:

http://programmers.stackexchange.com/questions/368/why-do-people-still-say-java-is-slow/5064#5064

As I see, there are mainly two reasons for this (also could be found in the link above):

One reason is that people trust what others say instead of what they see.

According what I was told when I first started programming, Java is "slower" than C++, and reason why Java could be used is because it's "convenient and easier". It's very commonly believed that Java brings Safety and convenience, at the cost of performance. Even when later C# is invented people believe it's faster than Java because it's "native".

But the truth people see without sensing it, is that, eclipse, the IDE that's built with Java, is absolutely the FASTEST IDE in class. I've used nearly all main stream IDEs, those from MS and GNU, Borland..., eclipse is the absolute king, of IDEs, largely because of it's fast.

Another reason is its long start up time.

Java is not suitable for developing a tiny app that stay in system tray, consumes a little memory, popup a dialog reminding you to take a break; or a notepad that you use to open a text file, read it and close it. It should be used on something BIG, like a web server that's always there, make optimized use of you computing resource, respond to millions of requests every hour. Or an IDE like eclipse that manage thousands of workspace files. You don't know you Java app is fast until it has run for at least several hours, I believe.




Also there's proof that java DO is slower, although a little bit, than other even high level programming languages:

Modern Java is not slow, as others have noted. But, there are a couple exceptions:

  • Array access is still MUCH slower compared to C, due to bounds checks and so on. This improves with every version, and Java 7 should provide a massive boost here.
  • Lack of arbitrary memory access can make some I/O and bit-level processing slow (compression/decompression for example). This is a safety feature of most high-level languages now.
  • Java uses a LOT more memory than C, and if your application is memory bound or memory bandwidth bound (caching, etc) this makes it slower. The flip side is that allocation/deallocation is blazing fast. This is a feature of most high-level languages now, and due to use of GC rather than explicit memory allocation.
  • Streams-based I/O is slow as shit due to the (IMO poor choice) to require synchronization on stream access. NIO fixed this but is a pain to use. Java 7 should fix this with a new stream-based but unsynchronized I/O library.
  • Java doesn't provide the same low-level functionality C does, so you can't use dirty tricks to make some operations faster. This provides portability, but you can't use (for example) inline assembler or clever x86 tricks. This is a feature of most high-level languages now.
  • String operations are slow. Java uses immutable, UTF-16 encoded strings. This means you need more memory, more memory access, and some operations are more complex than with ASCII. It's the right decision for portability but carries a performance cost.
  • Startup times still suck. If I recall correctly, useless, bloated crap like CORBA still gets loaded or at least handled in some fashion.
In the end, Java was designed to provide security and portability at the expense of some performance, and for some really demanding operations it shows. Most of its reputation for slowness is no longer deserved. Still, Sun always chooses the "better" way rather than the "faster" way whenever it can.