近日收到一個推銷 Wifi 計劃的電話,對話大概如下:
推 (推銷員):現在我們有新的 wifi 計劃,XX寬頻的長期客戶可享有優惠價… 我:但我沒有任何可駁 wifi 的隨身裝置 推:其實現在很多裝置都支持 wifi,例如閣下的電話、Notebook,甚至 PSP、
Here's a thesis:
The problem I see with making ticketing systems accessible to users isthat you periodically need to have a genuinely private conversationamong the sysadmins in response to user requests. I'm not sure how oftenthis happens in typical organizations; ours is somewhat atypical in howwe structure support, and possibly as a result it seems to happen fairlyoften here.
If your ticketing system is (internally) public, then you can't havethese conversations in the ticket; you have to find some
近日收到一個推銷 Wifi 計劃的電話,對話大概如下:
推 (推銷員):現在我們有新的 wifi 計劃,XX寬頻的長期客戶可享有優惠價… 我:但我沒有任何可駁 wifi 的隨身裝置 推:其實現在很多裝置都支持 wifi,例如閣下的電話、Notebook,甚至 PSP、
On the surface, the (c)Pickle module looks like a good, simple wayfor your Python program to save and load its data; much like XML , it means you don't have to write a parseror even save and load routines as such, just some file and objectmanipulation code. However, through my experience in writing DWiki I'vecome to understand that this temptation would be a mistake (one thatI've actually half-made; DWiki 's caching layer uses pickling)