星洁陪外公在屋前马路边摆档卖榴莲和红毛丹。
星洁看到客人把榴莲放进车里，脸色顿时变得很伤心，说：“不要把榴莲放进车喔！”
榴莲卖完了，收档回家了。星洁幽幽地说：“榴莲卖完了，我没有榴莲吃了。”
外公安慰她说：“家里还有。”
星洁没睡午觉，到了傍晚‘电池’快消耗完了。外公抱着累得快睡着的星洁，正要哄她入睡。外婆一句话：“星洁，吃榴莲啰！”，星洁挣扎着起来，哭说：“我要吃榴莲。”
外公开榴莲，喂星洁吃了几粒。外公递了一粒榴莲果肉给星洁，问道：“你要自己拿吗？”
星洁伸出一半的手停住了，说：“肮脏。用手拿。”（意思是用手拿，手会弄脏）。结果还是外公喂。
榴莲吃了，是时候睡觉了。星洁讨奶喝后，倒头就睡了。
榴莲季节
星洁两岁两个月。
听到‘榴莲’。
星洁：“公公家有榴莲。”
爸爸准备要‘杀’榴莲。
星洁：“小心尖尖啊！”
榴莲‘杀’开了。
星洁：“我要吃榴莲。”
吃完一粒。
星洁：“还要。”
吃完第五粒。
星洁：“还要。”
婆婆说不能再吃了。
星洁：“啊。。。” （闹别扭）
听到‘榴莲’。
星洁：“公公家有榴莲。”
爸爸准备要‘杀’榴莲。
星洁：“小心尖尖啊！”
榴莲‘杀’开了。
星洁：“我要吃榴莲。”
吃完一粒。
星洁：“还要。”
吃完第五粒。
星洁：“还要。”
婆婆说不能再吃了。
星洁：“啊。。。” （闹别扭）
星洁语出惊人
星洁两岁左右。
妈咪在用吹风筒吹干头发。星洁走向妈咪。
妈咪：“不要过来。烧。”
星洁：“好像婆婆煮菜这样啊！”
~*~*~*~
妈咪和星洁坐在沙发上。妈咪跟星洁说了一些话。
妈咪：“星洁，妈咪刚才讲什么？”
星洁：“讲话啦！”
~*~*~*~
爸爸驾车载一家人去逛街。星洁坐在司机位旁，在开心的笑。
爸爸：“星洁，开心就是Happy.星洁会唱Happy歌吗？”
爸爸：“[唱]If you're happy and you know it clap your hands [啪][啪]”
星洁：“有蚊子啊！”
妈咪在用吹风筒吹干头发。星洁走向妈咪。
妈咪：“不要过来。烧。”
星洁：“好像婆婆煮菜这样啊！”
~*~*~*~
妈咪和星洁坐在沙发上。妈咪跟星洁说了一些话。
妈咪：“星洁，妈咪刚才讲什么？”
星洁：“讲话啦！”
~*~*~*~
爸爸驾车载一家人去逛街。星洁坐在司机位旁，在开心的笑。
爸爸：“星洁，开心就是Happy.星洁会唱Happy歌吗？”
爸爸：“[唱]If you're happy and you know it clap your hands [啪][啪]”
星洁：“有蚊子啊！”
Bored with my job!
User feedback transaction error. Fix the error. Find out root cause. Suggest solution. Forward to developer if cannot find permanent solution.
There is no perfect system. Sure has loopholes here and there. So many systems and applications to support. Each system 1 error a day is enough to consume your 8 hours working time.
When there are new users, they made more mistakes, creating more errors. And they ask questions which already answered to the experienced users before. Still have to educate them so that they don't repeat same mistake.
It is lacking of systematic training process/program for new comers.
Every week need to submit weekly report. Every month follow up on the change request status.
On top of that, users have new system requests now and then. Need to gather requirements, propose system change, submit change request to developer team, wait for team to feedback when will this request be developed, users chase after you and ask when the request will be done.
.... boring.
There is no perfect system. Sure has loopholes here and there. So many systems and applications to support. Each system 1 error a day is enough to consume your 8 hours working time.
When there are new users, they made more mistakes, creating more errors. And they ask questions which already answered to the experienced users before. Still have to educate them so that they don't repeat same mistake.
It is lacking of systematic training process/program for new comers.
Every week need to submit weekly report. Every month follow up on the change request status.
On top of that, users have new system requests now and then. Need to gather requirements, propose system change, submit change request to developer team, wait for team to feedback when will this request be developed, users chase after you and ask when the request will be done.
.... boring.
Subscribe to:
Posts (Atom)
Posts
