不浪漫的家伙

歌手：曹格 专辑：曹格首张创作专辑




多想要记住这一分钟
回应我幸福的要求
我或许没有别的梦
唯一的是我爱你你也爱我
我担心一杯红酒
把我的真心透露
或许你早就该懂
冰淇淋在喉咙
能多冷静几秒钟
气氛在浪漫都不够
烛光晚餐像一场美梦
想这样望着你到永久
一束玫瑰交到你的手中
这一天这一刻这一切
你属于我
多想要留住这一秒钟
你每天晚餐都陪我
美味比不过你温柔
从此以后我爱你你爱我
多想要记住这一分钟
回应我幸福的要求
我或许没有别的梦
唯一的是我爱你你也爱我
我不是个浪漫的家伙
却甘心为你这样做
想要什么都跟我说
从此以后我爱你你爱我
我是不是有一点别扭
从不曾这样说出口
太多的愿望在心中
重要的是我爱你你也爱着我...

想知道你吃醋时的样子吗

一个夏日夜晚，你正经过隔壁邻居的庭院前，看到老爷爷带着孙子在庭院拿着打火机不知道要点什么东西。 依照你的直觉，他们在点什么呢？（直接点击选项看解答！）

　　　A、蚊香

　　　B、仙女棒

　　　C、蜡烛

　　 D、木材堆

我叫金三顺

我好欣赏她那种勇敢面对自己的爱的女人， 爱上一个潇洒、帅气、小他两岁的男人。虽然她是个没女（没身材、没钱、没屋子、没男友。。。什么都没有的女人）。在这世界上，没女是多过美女。所以借此告诫所有的男生，别一直在奢望美女了、踏实点找个自己爱的人而她也爱你的人。
真正的爱情并不需要有外在的托衬，只要两个相爱-其他的东西都不成问题。可是那男的就有点拖泥带水，还没解决前一段恋情就想要和她开始新的恋情（看来男人都爱劈腿，纳闷。。。）。
嘻嘻，现在我每晚都追着这部电视剧。只有十六集，很快就要结局了。
惨了，我迷上了韩剧！

爱

买爱的人，买到假心。
卖爱的人，心灵空虚。
等爱的人，空等一场。
示爱的人，心跳一百。
错爱的人，不敢再爱。
恋爱的人，居安思危。

My Nephew

Happy to see he is growing(3.4kg, but i think my mom is losing weight...so do i), but he still facing the diarrhea problem.
Hope he can get well soon.9/4/2006

测试：你是天真的行动派吗 ？

你急着要上楼，当你赶到电梯前的时候，电梯刚好上楼去了，于是，你只好再等下一部电梯了，等待中，你会做些什么动作呢？以下的答案，请选出一个最接近的吧！

　　Ａ重复地按电梯按钮

　　Ｂ走来走去

　　Ｃ看电梯周围的告示板

　　Ｄ低着头，无意识地看着地板

　　Ｅ紧紧盯着显示电梯位置的灯号

　　结果诊断

　　等待电梯时的动作是很无意识的，而无意识正巧可以流露出本性的一部分。这个测验也可以用来观察别人，让你对人性有进一步的认识喔！

Small ISVs: You need Developers, not Programmers (By Eric Sink)

Context is critical. Management advice can be worthless or worse if it is not appropriate for your situation. The right decisions for a big company can be fatal in a small one. Make sure you consider your context before you listen to anybody's management drivel, including mine. :-)

I run a small ISV (Independent Software Vendor) with no substantial outside funding. SourceGear is 6 years old and has 25 employees. I've learned plenty of interesting lessons along the way. One of the things I've learned is that a small ISV should not have any programmers.

For the purpose of this article, a "programmer" is someone who does nothing but code new features and [if you're lucky] fix bugs. They don't write specs. They don't write automated test cases. They don't help keep the automated build system up to date. They don't help customers work out tough problems. They don't help write documentation. They don't help with testing. They don't even read code. All they do is write new code. In a small ISV, you don't want any of these people in your company.

Instead of "programmers" (people that specialize in writing code), what you need are "developers" (people who will contribute in multiple ways to make the product successful).

My apologies if I'm trying to be too cute with my word definitions, but it really doesn't matter what terminology you use. In a small ISV you can't afford to have people who think their only responsibility is writing code. There are far too many other things to be done, all of which are critical to having a successful product. If you were a BigCo, you would just hire more specialists until every job function is covered. But as a small ISV, what you need are fewer people who are more versatile.

Boundaries vs. Flexibility

This is a really important difference between small companies and big ones:

In a small firm, most people wear multiple hats. It simply isn't feasible to have a person who focuses on just one small area. Small companies need versatile people who are content and capable to step in and do whatever it takes to help the company succeed. One accountant or bookkeeper handles basically everything. There is often a utility infielder who is always busy but nobody knows what they do. The key concept here is flexibility.

Big companies have more specialists. Payroll is different from "accounts receivable" which is separate from "accounts payable". Architects do design. Programmers write code. Technical Leads manage programmers. Program Managers keep the spec and schedule. Product Managers do positioning and message. Evangelists do, er, well, nobody really knows what evangelists do. :-) Anyway, each person has a specific, well-defined job. The key concept here is respect for boundaries.
By the way, these are two very different cultures and ugly things can happen when they intersect. Flexibility and boundaries don't mix very well. A person who has been successful in one of these cultures often stumbles badly when they transition to the other one.

Developers

In a small ISV, every developer is first and foremost a programmer. The bulk of their time should be spent writing code and fixing bugs. But every developer also needs to be involved in other areas such as the following:

Spec documents
Configuration management
Code reviews
Testing
Automated tests
Documentation
Solving tough customer problems
Using my terminology, these things are the difference between a programmer and a developer. The developer has a much larger perspective and an ability to see the bigger picture. The programmer writes code, throws it over the wall to the testers and waits for them to log bugs. The developer knows it is better to find an fix bugs now, since he just might be the one talking to the customer about it later.

When your team evolves from programmers to developers, your pecking order may change. Your best developer may not be the person who usually gets thrown the really tough problems. A programmer of amazing talent can be a lousy developer. Coding is a necessary but insufficient part of being a developer. Similarly, the less gifted members of your team can still distinguish themselves as excellent developers through their contributions to the non-coding parts of the product.

My Nephew

he was so tiny just 3.1kg n fragile.
Now he live in my house, me n my mom will try our best to feed him until fat fat white white de.
:) 7/4/2006

永在我心

看到它那么努力的呼吸着来延长它的生命，我的心好痛。。。
它走了。。。
我试着不再去想它，但我做不到。。。一想到，鼻子酸了、眼眶又红了、泪液一滴一滴的流了下来。
每次回到家时，它不再向我摇尾巴了、也不再拖我的手指向我要狗饼吃了（那包用他的照片参加比赛赢回来的狗饼都吃不完了）。。。T T
葬它的那天早上，要求爸爸把狗饼洒在它身边因为它从来不敢未经我们的同意而偷吃。。。
安息吧！愿你找到你的净土。。。