個人檔案Gary's Space相片部落格清單更多  |  工具 說明 |
|
30 September Talking about Eileen Chang (张爱玲）Voted Most Beautiful Female Chinese Writer
Quote Eileen Chang (张爱玲）Voted Most Beautiful Female Chinese Writer 28 September 有志于长期从事软件的人们，建议看看一篇好文Gary也知道，总在自己的Space中贴别人的文章，是一种懒惰和令人唾弃的行为，但是下面的文章确实值得推荐。如果看官有兴趣一直从事IT行业，花点时间来了解这些观点是非常值得的。
The Future of Software Development
Written by Alex Iskold / October 16, 2007 1:28 PM
In 1975, Frederick Brooks wrote a classic book on software project management called The Mythical Man-Month. In the book, he famously argued that adding more people to a development project will hinder rather than help to get things done faster. The reason is that having more people working on the project introduces a non-linear overhead in communication.
Five years before Brooks' book, a software development methodology called the Waterfall Model was coined. This approach applied the insights from mature engineering disciplines (mechanical, civil, etc.) to software. The idea was to construct systems by first gathering requirements, then doing the design, then implementing it, then testing, and finally getting it out the door in one linear sequence. We have come a long way since then and learned a lot about making software. The Waterfall Model is now considered a flawed method because it is so rigid and unrealistic. In the real world, software projects have ill-defined and constantly evolving requirements, making it impossible to think everything through at once. Instead, the best software today is created and evolved using agile methods. These techniques allow engineers to continuously re-align software with business and customer needs. With the advent of modern programming languages (Java, PHP, Python and Ruby), rich libraries, and unprecedented infrastructure services like those from Amazon, we are arriving at yet another evolutionary step. Digg, del.icio.us, YouTube and other poster children of the new web era were developed by just a handful of programmers. To build software today all you need is a few good men (or women!). In this post we trace how we got here and where we are heading next. Why The Waterfall Model FailedNon-technical people tend to think that software is soft or easily changeable. Since there are no visible nuts and bolts and no hood to open people think that software can be tweaked and re-wired on a whim. Of course, this is not the case. Software, like any mechanical system, has a design and the structure; it is not as soft as it seems. Yet the accelerating pace of business requires constant changes to software. Older development methods completely fail to address business needs. Using the Waterfall Model, these changes were impossible, the development cycle was too long, systems were over engineered and ended up costing a fortune, and often did not work right.
The problem was that the Waterfall Model was arrogant. The arrogance came from the fact that we believed that we could always engineer the perfect system on the first try. The second problem with it was that in nature, dynamic systems are not engineered, they evolve. It is the evolutionary idea that lead to the development of agile methods. Agile Methods - Evolving SoftwareIn the early nineties a number of agile software development methods emerged. While they differed in details, they agreed at large that software development needed a major rethinking. First, software has to embrace change. Today's assumptions and requirements may change tomorrow, and software needs to respond to changes quickly. To meet the challenge, agile approaches advocate focusing on simplicity. Make the simplest possible system that satisfies today's requirements and when tomorrow comes, be ready to adapt.
Two techniques pioneered by agile methods are worth particular attention - refactoring and developer testing. Refactoring, elegantly described by Martin Fowler in his classic book is the idea of improving the design of the existing code without changing how it works.
Refactoring is what allows agile systems to embrace change, while remaining elegant and free from rot. Like an interior decorator continuously changes and improves the layout of your furniture, agile developers move code around to improve the product as a whole. Code is constantly changed to make sure we end up with the simplest, and best possible system that reflects our current needs. To make sure that changes do not break the code, agile methods introduced unit tests. As each agile project unfolds, it grows the base of unit tests. Each test is focused on a single component of the system and acts as an insurance that the component works as expected. Typically, the tests are run continuously against the code and require immediate fixes in case of a failure.
The software systems created using agile methods are much more successful because they are evolved and adapted to the problem. Like living organisms, these systems are continuously reshaped to fit the dynamic landscape of changing requirements. Without a doubt, agile methods made a major impact on how we think about building software today - dynamically and continuously. It's The Libraries, Stupid!While we discovered better way of making software, we also discovered better programming languages. C was replaced with C++, then came Java. Perl was great, but PHP and Python took its lessons further. More recently came Ruby, which has become very popular because of its natural way of expressing code. Because of this evolution, today we have a number of excellent, and virtually equivalent programming languages. While the choice of programming language is typically a sensitive subject, the truth is that it is not the language, but the libraries that come with it that make a difference. C++ never had the standard libraries that Java has. Yes, Java is the simpler language, but people used C++ for a decade just fine. What gives Java the edge is its rich set of reusable libraries. The story is similar with PHP. It has been the language of choice for web developers precisely because it comes with such rich support for web and database processing.
In addition to the libraries that come with modern languages, the open source movement has also contributed a wealth of code towards global software infrastructure. Notably, just the Apache foundation on its own has created a huge amount of high quality reusable code. We have now arrived at an age where we have a strong foundation for building complex software systems. We know the methods and we have the tools, so what does that mean? The Future of Software Development: Just a Few Good MenSince early days of software development people struggled to build good systems. More and more people where thrown at the problem, making matters worse. But with the recent explosion of social web we've witnessed a new and interesting phenomenon: a handful of developers are now able to build systems that are used by millions of people. How can this be? The secret is that as with any good endeavor it only takes a few good men (and/or women!). With a bit of discipline and a ton of passion, high quality engineers are able to put together systems of great complexity on their own. Equipped with a modern programming language, great libraries, and agile methods, a couple of smart guys in the garage can get things done much better and faster than an army of mediocre developers.
We are likely to see a few changes over the coming years:
ConclusionIronically, we are coming full circle with the mythical man-month. What was true twenty years ago is true of course today, but for a whole new set of reasons. An awesome array of programming languages and infrastructure libraries combined with agile methods has allowed us to break free of old software development dogmas. Just a handful of great engineers can now successfully build systems of great complexity. Craftsmanship has finally come to software engineering!
What's the future for the software industry? Ask academia...By Tom Foremski - April 4, 2007
Carnegie Mellon University and the University of California, Berkeley have joined together for a one day conference on April 30th in Mountain View. Academics and industry leaders will discuss issues and trends for "the new software industry." They promise that there will be no product demos (how about no PowerPoints too...)
It seems clear to me where the software industry is headed:
Industry Leaders Look To Software's FutureBusiness-technology executives, vendors, and software developers give their 2 cents on everything from how users will pay for software in the future to what's next for Linux.
By Rick Whiting
On relationships with software vendors:
"The issue of software quality might begin to hit software vendors where it hurts--on the financial bottom line. In the future, vendors who are used to getting paid for their products up front, even if the software is buggy, may find payments from customers tied to how well their products perform." – Tony Scott, a chief technology officer at General Motors Corp.
The trend is toward simplifying the enterprise software architecture, and software as services offers a way to do that. Hence, customers will demand that more software be delivered this way. With software as services, software vendors are being drawn more intimately into the day-to-day operations of their customers. "Increasingly, the software vendor's fortunes are being tied more closely to the customer's." – Madhavan Rangaswami, co-founder of Sand Hill Group, a Silicon Valley venture-capital firm specializing in enterprise software
On hosted software services:
"Software as a service is an appropriate name. Service should be in bold block letters, because it's the service over time that will change. Software will become more of a commodity." – Bud Mathasiel, CIO of Solectron (NYSE: SLR) Corp.
"Getting true functionality to the end user will drive success or failure. Welcome to the services world. If they don't like it, you don't get paid." – Treb Ryan, CEO of OpSource Inc., a provider of infrastructure, systems and application management, and hosting to ASPs
On application development:
"There's been a lot of hand-wringing over the number of development jobs that have been outsourced to offshore companies. Won't increased automation of software development processes accelerate that trend? I'm not sure if that actually pans out. It's the basic programming jobs that have already been outsourced that are in danger of disappearing." – Patrick Hynds, chief technology officer of CriticalSites Inc., an IT development and integration services firm
On the next killer app:
"The punch line is that the next killer apps are going to be new ways of doing old things." – Dan'l Lewin, VP of .Net business development at Microsoft (NSDQ: MSFT)
On standards:
Don't underestimate the influence China will have on the software industry. With millions of businesses and hundreds of millions of users, China may be positioned to dictate software standards for the rest of the world. "I believe China will play a larger role in setting software trends." – Danny Sabbah, chief technology officer in IBM (NYSE: IBM)'s software group, pointing to Red Flag Linux, China's own version of the open-source operating system
On the next version of the Linux operating system:
"I absolutely hope that it will be fundamentally different some way. But in many ways I don't actually expect that to be the case. Operating systems have been around for decades, and the fact is, they don't tend to do surprising things. I suspect we'll be doing some things very differently internally, and there are bound to be new interfaces for new things people do, but in the end, an OS is an OS." – Linux creator Linus Torvalds
On the cost of software:
"Software is a human, intellectual activity. It is automating knowledge. I think there is a natural limit to how cheap enterprise software can become." – Gerald Cohen, CEO of business-intelligence software vendor Information Builders Inc.
On security:
"People who are building service-oriented architectures --which as far as I can tell is everyone, I haven't found a global 2000 who isn't --(have) a whole bunch of new concerns and new issues. Web services punch a hole in the firewall, so the firewall doesn't do me any good, and someone with an identity unknown to me is coming in and asking for service. And if that service is accepted, out goes information that's potentially my business-critical information. How do we deal with that? I think the answer is you need to consider (having) security on every single one of your computers, not just (around) the perimeter." – Jothy Rosenberg, founder and chief technology officer of Service Integrity Inc., a developer of Web services monitoring and analysis software, and author of Security Web Services With WS-Security.
On long-term predictions on the future of software:
25 September 在路上，和孩子分享梦想（ 四）——“多背一公斤”河南尖山中心小学行
下午就是彪哥和剑锋的天下了，两位1kg的好汉，组织起活动来那是得心应手。彪哥应该相当于某山某洞的“总钻风”，那剑锋就是一个“小钻风”了——看过西游记的都知道，就是那种别着腰牌，敲着锣，唱着“大王叫我~~~来巡山啰~~~”的。上面还有一个老怪叫金角大王，哦不，叫“歪歪”。
说道适合小朋友的游戏，彪哥最有主意，篮球、足球、画画、唱歌、乒乓球。。。分别安排下去，GGMM们各就各位，分别带队施展武艺去了，游戏规则彪哥已经有交代：“一定要让小朋友赢！”
印象深的是足球，彪哥挂着哨子当裁判，分别组织了5个队（每个队4个小朋友），任务是把球踢到对方门里，其他规则就啥都没有了，所以球经常处于满院子飞的状态——已经有先知先觉的GG把院门关上了。
老陈的任务是组织第6个队，这个任务比我理解的要困难很多，因为性格比较开朗的小朋友已经自我组队了，剩下的几个小兄弟算比较内向的，总不肯出来当队长、挑人和组织人上场。老陈使出浑身解数，理智加情感，终于打动四位小弟参赛。
足球比赛后，空出的场地就上演彪哥最擅长的“砸球”，类似我们小时候玩的的扔沙包，一堆人在中间，砸中的下场，最后的就是胜利者。小户很积极，但是心太软，总是拿着球吓唬半天，等小朋友跑远了才扔出来。彪哥就很强悍，他的力道，俺看着心里都捏一把汗。。。
所有游戏都决出了胜利者，欢乐的时间到了，颁发奖品、礼品、还有KEEN赠送给老师和小朋友的运动鞋，总之，每个人都是冠军。然后合影，照例是“茄~~~子~~~”。。。
欢乐总是短暂的，当我们要离开的时候，才觉得时间过的真快，看着小朋友、老师和校长和围观的村民和我们挥手告别，真的觉得自己应该给小朋友们做得更多些。
在山村里和小朋友们在一起的时间，是充实的快乐，随后在开封的游览，是闲散的快乐，在鼓楼夜市的聚餐，是慵懒的快乐。。。亲身参与，谁会拒绝这一路的快乐呢？
回来已经有一段日子了，又回到了正常的工作生活。拖沓的文字，已经让心急的人们骂了又骂。在尖山拍的照片，也已经在邮寄的途中，相信这两天杨润佳应该能收到吧。大家又谋划着下一步的活动，让这份快乐延续。。。
感谢多背一公斤，让这么多陌生的人走在一起。让我们有机会一起来想，怎么更好地回报孩子们给大家带来的这么单纯的快乐。
最后，感谢我的“经纪公司”、彪哥、剑锋、歪歪和所有的V，你们的鞭策和鼓励，逼着俺写完这些文字。。。 ：）
23 September 一位很好的朋友走了 中午，听到，一位朋友，一位很好的朋友，我的很多同事都非常熟悉的朋友，走了。
很突然！是这两天的事情，不想细问，据说是脑溢血，今天早上走的。
他还很年轻啊，象我们的兄长一样，认真、快乐，我们中秋节前还在通电话，商量在北京见面的事，我和HF上周还在聊起他，聊到我们的尊重和喜爱。
人生无常。
愿他的亲人、朋友能常常想起他，想起我们都曾有这样一个很好的朋友。
失去了，才知道珍惜，我突然很想他。。。
21 September 在路上，和孩子分享梦想（三）——“多背一公斤”河南尖山中心小学行杨润佳的家在村里应该算经济条件不太好的，他们的有些邻居已经是砖房了，她家的院墙还是泥石的。进到院里，妈妈和爷爷已经在等候了，很客气的招呼，我猛地听这么密集的河南话，有点反应不过来。
进到房里，我发现地面还是泥地，屋子里摆设非常简单，妈妈连连道歉，仿佛简陋的房屋是对客人的慢待，这搞得我很有些内疚。房子中间的小桌上已经有摆了很多核桃，我们边砸核桃边聊天。爷爷是个健谈的老人，76岁了，对于孩子的教育、农业政策、封山育林、河南历史等等，说的头头是道，这让我有点小小的惊讶。他说道杨润佳的成绩在班上是非常好的，并且家里一定会让杨润佳一直读下去：“只要她自己愿意念，就让她念”。
我们在聊天，杨润佳忙着剥核桃递给我，偶尔应几句。她唯一去过的城市就是开封，好像是有亲戚在那，问她城里好玩吗？一个字“好”,多的不说了，呵呵。
妈妈张罗着饭菜。很快，菜都端上桌了，四五个青菜，还有一盘炒鸡蛋、一盘烙饼，用来卷菜的。饭菜应该是早就准备好了，我想我们的到来，对于学校和村里人感觉是件很大的事情。
路上就了解到村里人很少能吃肉，我和爷爷聊天，了解到由于边上的尖山风景区封山育林，所以家里也不能养羊，要吃肉只能到山脚下去买——你能想象得到一个山区农村能有多少经济收入，尤其是现金收入，能种粮食和青菜自给自足就不错了。
边吃边聊，我在西安呆过多年，所以能听懂大部分河南话，不过和爷爷讲话，必须用很大声音。村里的年青男子基本上都外出打工了，所以我能陪他老人家聊聊天也是件不错的事情。
杨妈妈很热情，我连卷了三张饼，肚子撑撑。吃完饭，和一家人在院门口照相——实在不好意思在人家屋子里照。我把相机硬塞给杨润佳，让她给妈妈照相，小姑娘新奇又羞涩，照完马上把相机递还给我，脸上漾着快乐的笑。
和杨润佳走在回到小学的路上，同行的GGMM们都陆续从山间小路冒出来，看来大家和结对的小朋友都混的很熟了，一路说说笑笑。
( 各位看官请不要骂我，请忍受下我唠唠叨叨的风格，下一节肯定收尾：）
18 September 抓住奥运的尾巴 9月16下午，北京，在国家体育馆看了轮椅篮球的决赛。9月17日晚，残奥闭幕。
本来和奥运八竿子都打不着的，最后却在尾巴上亲身参与了下。感想如下：
(1) 感谢Helena姐姐的全程赞助，送门票，还陪逛、陪看、陪吃：）
(2) 奥运期间北京干净太多了，不知道能不能坚持
(3) 奥运在北京真的是全民参与，在地铁中经常见到蓝衣服的志愿者，胸口挂着大牌子，很牛的
(4) 比赛现场气氛很热烈，咚咚咚、啪啪啪、摇滚乐，还有主持人的“A~~~~~~~U~~~~~~~Ready ? ”
(5) 运动员也很enjoy整个过程，俺旁观，但是能感受到。。。 14 September 在路上，和孩子分享梦想（二）——“多背一公斤”河南尖山中心小学行“群”第二天果真建立了起来，大家陆续在群里露了面，这个时候大家开始讨论具体的行程、我们应该带些什么东西给学校和小朋友、活动如何开展，等等等等。文具当然是最容易想到的东西，其它呢？大家七嘴八舌地讨论，很多的提议都淹没在快速滚动的文字中了。。。最后归结为几大类，一类是帮助孩子们学习的东西，一类是组织活动（一个小型的运动会，刚好可以趁着奥运的东风）需要的器材、一类是让孩子们快乐的东西（小糖果、小玩具之类的，我发现男同胞们都比较关注这些，相对MM们会比较喜欢文具，难怪现在的家庭大都是严母慈父），讨论形成的决议都由Lee造册登记，落实到人。 当然还有一件事情是很重要的，就是大家要多沟通沟通，免得到了现场自己人还相互不认识，闹出笑话，在剑锋的启发下，最后大家一致认为一场饭局是必要的。 周末，饭局在温馨友好的气氛中结束了，对于彪哥、剑锋、小陆、Martin和昭华（就是前述的“水壶”）有了更多的了解。 9月5号是上路的日子，老陈是一个很遵守纪律的人，早早的来到火车站，很快大家都到齐了，很多人是头一次见到，不过出门永远是件让人愉快的事情，大家兴致都挺高。车上的情形就不多说了，总之，食物让整个车厢充满了轻松愉快的气氛，彪哥更是眉飞色舞地讲述以前的旅途趣闻，绘声绘色，高潮迭起，有某个瞬间，我甚至怀疑这小子是从德云社溜出来的。 6号早上，车到郑州，转乘大巴，直奔新密尖山。这个时候，耳闻已久的小户出现了，一个很朴实、快乐的河南小伙，与我认识的好些油腔滑调的家伙大不相同。他也是1KG的人，怎么也是个堂主、香主之类的吧。 一路公路，只是海拔越来越高，才慢慢理解行前和朋友沟通的情况，新密是一个相对富裕的地区，但是山区里情况就比较艰难一些了。从我们快到尖山村，下车徒步，彪哥特意叮嘱：村里的生活用水都是靠积攒雨水，所以无论待会吃饭还是活动，都最好不要用水。 尖山村是在山顶上，学校在村中间，是一个简陋的小院子，院外墙上有一块碑，已经被刻画的字迹模糊，但是大意能看出是纪念1995年村里出资兴建学校的事情。大门进去，迎面是一个两层红砖小楼，两边是3，4间红砖平房，教室、老师的办公室都在这里了。地面很干净，我想起了我上小学的时候经常进行的大扫除后情景。 校长（一位衣着简朴的中年女老师）和老师们非常客气，都说着感谢的话，并忙着把教室中的小凳子拿到院中，让大家安定歇息下来。一个教室（三年级）中传出学生的声音，虽然是周六，但是孩子们还是被组织到学校参与活动。 尖山中心小学有1-4年级，学生上到5年级，就需要转到其他的学校去上了。从门口的牌子可以看出，每个年级都是一间教室，里面有10来个木头课桌和小木凳，满是刻划的桌子和小凳都有年头了，还有黑板和后墙的板报，总体感觉是：这是一个完整，但是简陋的乡村学校。 一路上彪哥和剑锋都是随意而放松的，但是一进学校，两位就显示出专业和经验来，和老师接洽、指挥搬运、组织学生、组织志愿者。。。井井有条，1kg果然是卧虎藏龙。 等我们到带来的东西搬到院中，学们走出教室在院中列队，我们也列队站好，原来安排的是志愿者和学生结对子，各自到学生家里吃午饭（当然是统一缴费的），然后下午回来组织小型的运动会。 去一个陌生的人家吃饭，这是一个小小的挑战，真的没有准备好如何沟通。和我牵手的是一个清秀的小姑娘，她叫“杨润佳”，9岁，和这里的每个孩子一样，认真而害羞，浓重的方言口音，我问她所有的问题她都是先是抿嘴笑，然后才用最简短的几个字作答。 她牵着我走出学校，经过一大片玉米地，转入一个山坳，她的家就在这里。
10 September 在路上，和孩子分享梦想（一）——“多背一公斤”河南尖山中心小学行8月，某天，在出租车上看到触动传媒的多背一公斤的广告，招募10名志愿者去山区小学公益里旅游。“多背一公斤”是早有耳闻的。按照广告发了短信，马上就收到了标准格式的回复，“欢迎参与，活动将另行通知”。到底是信息社会，确实方便。
8月，另一个某天，收到了短信，周末将在静安青少年中心开展一个培训。周末去了，迟到，满满一屋子人，估计有200左右，才惊讶原来还有这么多人会有兴趣了解和参加这种活动，原来我以为自己报名还是特立独行呢。
台上的GG是安猪，后来才知道是“多背一公斤”的创始人，GG在台上熟练地操作着PPT，掰开揉碎地讲解着“志愿者”、“志愿组织”等等概念，显然当时我没有认真领会安猪的微言大义，听了差不多半个小时就想着开溜。
出门时，遇到了笑容可掬的Rey Lee，也是之后知道她是触动传媒方的组织者，简单聊了几句，小丫头很客气的留了电话，这个细节是我能参加最重要的因素，不过当时我并没有意识到。
第二天，想起给Rey Lee发了个短信，言简意赅地表达自己想参加的愿望，Lee也客气地回复说请等待最终结果。短信虽短，效果不错，感谢Lee和组织团队的安排，8月的第三个某日，俺收到了确认信息，某个傍晚到触动传媒的办公室进行出行前的见面会。
我是后来知道的那天培训后半截的安排，有110多个人填写了申请表，当场进行了抽签，10位志愿者就此产生。俺连抽签的事情都不知道，更说不上被选中了，感谢Rey，让我以编外参与到此次活动中。
顶着肚饿，这次按时到了会场，各路英豪陆续到齐，端坐在桌角的两位神情安详的GG引起我的注意，老陈果真好眼力，这两位是组织上的人，本次的1KG领队，一个肥白的是彪哥，一个黑胖的是剑锋。
Rey Lee进行了简短的活动介绍，本次目的地是“河南新密尖山乡尖山中心小学”。各位又作了简短的自我介绍，才了解不少是媒体的记者MM、还有赞助方KEEN的MM 、还有一位混户外的专业驴，见人就发水壶——以致我很长时间没有记住GG的名字，就简称“水壶”了。
在场的俺年纪最大，惭愧，不敢拿出“Gary”的诨名，就顺势说俺简称“老陈”——这个就是俺整次活动中的大号。
Rey Lee最后令下，大家交出各自的MSN地址，第二天“群”将建立起来，我第一次知道了MSN也可以建群——以前一直混QQ群的，不过当时可没敢露怯。
会议不长，但是已经饿的前胸贴后背了，Lee很体贴，早准备了饮料和饼干，我狠狠喝了一大口可乐，若有所思：“尖山小学，俺要来了。。。”
(根据留言量决定是否待续。。。)
4 September Prehistoric Park 和过度特化 以前就在电视上断断续续看过一点点《Prehistoric Park （史前公园）》，昨天整个看了一遍，这类半科普、半故事的叙事方法挺容易吸引人的。
知道了：三角龙、雷龙、似鸟龙、四翼盗龙、剑齿虎、恐鸟。。。还有石炭纪一米多长的大蜈蚣！！！ 等等等等已经灭绝的史前动物。
知道一个词——“过度特化”，这也是剑齿虎灭绝的主要原因之一。过度特化的意思是动物在某方面能力进化的太强了，比如剑齿虎的锋利的长牙齿和强壮的前肢，特别适合对付比它大的野兽，所以，它曾统治整个南美的草原。但是，随着气候的变化，大型的动物（远古的“大型”好像动辄意味着几吨，和现在的概念差别很大）逐步灭绝，这样剑齿虎的优点成为它的拖累，变得连鹿这样的小型动物都追不上了。。。
优胜劣汰是自然法则，人和组织亦然。如果没有前瞻的眼光，我们说不定也走在过度特化的路上呢。。。
2 September 李若山语录李若山，男，复旦大学教授，会计学专业博士生导师，号称中国审计第一人 现任复旦管理学院财务系系主任，整天过得逍遥自在的"管院一霸" 本学期在有限的六周审计学课里，频频爆出让人"拍手称快"的话，这里转载收录一下 1。78界我们同学聚会，名单打印出来，很多人都是已故。为什么已故呢，都是枪毙的。当然现在还有很多还在里面。干我们这一行的，出来都是两院院士，做得好进医院，做不好进法院……
2。我有个60岁的朋友，他估计能够活到90岁，是正常的直线折旧。但是后来，他请了一个小保姆，两年后就死了，这就是加速折旧。 3。和我一起毕业的许多同学大多数都成为了什么CEO,CFO,CIO,CCO啊之类的，总是一个C加上结尾一个O，什么？CCO不知道？Cheif Culture officer。我呢，是大学财务系的主任，也是个O，财务英文的第一个字母是什么？F。然后大学是university，所以呢……UFO
4。那个我们知道审计师的独立性受到干预的话是无法客观出具审计意见的，比如有个审计师到公司去审计，公司的CFO是个复旦毕业的小姑娘，审啊审啊审出感情来了，就结婚了，那怎么出具反对的审计意见报告，否则怎么回去和自己当老板的老婆交待？而且大家知道上海的家庭治理结构和别的地方是不一样的，是丈母娘领导下的太太负责制。在我家就是这样，家里大事听我的小事听她的。什么叫大事呢？打伊拉克就是大事，其余的都是小事 5。中国第一代企业经理人是搞技术出身的，那个时候物资紧缺，生产出来不愁卖不掉。第二代经理人呢，是搞——我不知道中文怎么说——Marketing出身的。你们把marketing叫做什么啊？（我们：市场营销）不对，叫忽悠！你们知道他们系的祖师爷是谁么？赵本山！
6。加班不报OT有什么坏的后果呢？你不报加班时间以后安排time budget的时候就会更紧，然后别人不加班就没法按时完成，没法按时完成就没有奖金，没有奖金他就只好偷工减料，偷工减料审计报告的质量就会出问题，审计报告的质量出问题安达信就享年88岁了。这个都是环环相扣的，好比没有天哪有地没有地哪有你没有你哪有我…… 7。我们知道广告费用这个东西有个滞后效应，就是说你今天投下去要以后才看得到效果的。这个就好像青橄榄，青橄榄你们吃过伐？就是咬下去的时候有点苦涩的。小时候妈妈给我吃青橄榄，咬了一口苦苦的怎么这么难吃的啦，就丢到屋顶上面去了。嚼了一会以后突然觉得有甜甜的味道了。哦原来这个东西这么好吃啊，马上拿了个梯子爬到屋顶上面去找，找了半天没找到，只看到一个黑黑的东西。我想么大概是晒黑了，拿起来就吃，结果还是苦苦的。我去给妈妈看，妈妈说那是猫屎……
8。什么叫法人？法人就是被绳之以法的人 9。我也发过一个adverse审计报告，那家公司的财务报表对使用者会产生重大的误道，但是由于高超的处理，没有任何地方违反准则和法律的。结果实在没有办法怎么办？就用了杀手锏，Substance over Form (实质重与形式原则)。这个叫什么？这个就叫做欲加之罪，何患无词！
10。苦不苦，想想萨达姆。累不累，想想CPA 13。验资报告都是拿一张发票。说上面这点都是我的资产。有哪些啊？毛巾面盆大脚桶，牙刷牙膏香肥皂，汤勺盆子压力锅，碗筷调羹切菜刀……(上海话) 14。大家别以为4大那么好。一开始想想，本科一毕业，能拿个4、5千，非常诱人，但仔细想想呢，每天工作到很晚，除一下，平均每小时工资并不多。再看看忙季的时候，起得比清洁工还早，睡得比小姐还晚。我知道一个男同学，晚上半夜2点中去厕所，大哭一把，哭完洗把脸继续工作。 15。以前和一个老板吃饭，他问我：李老师啊，你是不是CPA啊？我说是啊，"那你能不能帮我出一份审计报告啊？""好啊，没问题啊"然后就签了engagement letter，我就去了，结果到他们财务部，说，你们的账在哪啊？他说：等下。然后搬来了一个大马甲袋，打开一看，里面全是各种发票和其他凭证，说"李老师啊，不好意思啊，我们不知道怎么做账，你既然来了就帮我们整理整理吧"，我一看说"哎呀，这个怎么做审计报告啊""哎呀李老师啊，那就不好意思了呀，我们是签了engagement letter的 啊，你不做是违约的啊"然后我一气之下，出了份"无法发表意见的审计报告"他一看"呀，这叫什么审计报告啊？"我笑笑"你不懂了吧，这就叫无法发表意见的审计报告，这个不好意思啊，我们是有engagement letter的啊，审计费还是要照付的，不然是违约啊" 1 September 学个英语：真把我给气炸了。。。 “他真过分，真个把我给气炸了！” 日常生活中，难免会遇到气火中烧，在郁闷、愤怒即将引爆的一刹那，“气炸”十有八九要从口中溜出。一句很美国化的用法，“气炸”—— to get someone's goat。 不难看出，“to get someone's goat”肯定与“山羊”脱不了干系。据美国语言学家、新闻评论家H.L. Mencken（亨利·路易斯·门肯）推测，该短语源于赛马，“山羊”在赛马比赛中居一席之地。早年，驯马师在比赛前，常把山羊置于性情暴躁的种马厩中，据说可以起到安抚烈马的功效。不过，卑劣的赌徒为了赢得“马彩”，会对未下赌注的马匹做手脚，偷偷把“安抚使者”山羊牵走。 故事讲到这儿也就明白了，to get someone's goat原指“把山羊从马的身边牵走，惹马生怒”，随着时间的推移，就成了“惹人愤怒”了。看个例句：You've carried it too far. That really gets my goat!（你做得太过分了，真个把我给气炸了。） |
What will the software industry look like in three, five, even 10 years from now? And what customer demands and business trends will drive changes in software products, how they're developed, and the industry that provides them? Here are some thoughts from suppliers and buyers of enterprise software:
|
|
