Coder

Unit4.8

2009-01-25T22:06:00.000-08:00

Hi, Christina. What took you so long?

I got you some travel brochures. Want to look?

Brilliant! Thanks! Did you get some for Greece?

I got you a whole range : everything from the cheapest package tour to most expensive resort.

Wow, you’ve got loads of them. Where’s that place with the gorgeous beach?
That’s in the Canary Inlands. It’s supposed to be one of the cleanest and most beautiful beaches, but it’s super-expensive.

I’m on a pretty tight budget . Where would you go?

Well, I like diving , so I’d go to the place with the best water and sealife. You don’t dive, do you?

Nah, I prefer lazing by the beach with a good book, and I like a place with a good nightlife.

Well, Ibiza is prefect to you then. It’s easily the busiest place for the nightlife. But the beaches are some of the most crowded in Europe. Don’t you mind?

Not really. My friend Charlie’s been all over Europe, and he told me he had the most fun in Ibiza. Plus, the other tourists were some of the friendliest he’d met.

So you want to go to Ibiza then?

It sounds like the most exciting place for a holiday, but let’s check out some more brochures before I decided.

Rational execs on empowering the "A" in SOA

2009-01-05T17:36:00.000-08:00

Jamie Thomas, Lee Nackman, and Scott Hebner talk about the leap forward with IBM Rational Software Delivery Platform Desktop products V7

Level: Introductory

Scott Laningham (scottla@us.ibm.com), Podcast Editor, IBM developerWorks

05 Dec 2006

The following is a transcript of a podcast interview between developerWorks podcast editor Scott Laningham and IBM® Rational® execs Jamie Thomas, Lee Nackman, and Scott Hebner.

developerWorks: You're listening to developerWorks interviews where we feature conversations with technical luminaries and thought leaders from a variety of disciplines on topics of interest to technology professionals. I'm your host, Scott Laningham. Our guests today are here to talk about the release of Version 7 of the desktop tools of the Rational Software Delivery Platform: a comprehensive set of Eclipse-based offerings and best practices processes. Our guests from IBM Rational are Jamie Thomas, vice president, Rational Software Development; Lee Nackman, vice president, Product Development and Customer Support; and Scott Hebner, vice president, Marketing and Strategy. Thank you all for making time for this today. We appreciate it.

developerWorks Interviews: Rational execs on empowering the "A" in SOA

Be sure to listen to the interview.

Thomas: Thanks, Scott. I'm glad to be here.

Nackman: Oh, it's great to be talking with you again, Scott.

Hebner: Yes, I couldn't agree more. Looking forward to it.

developerWorks: Scott Hebner, maybe you could kick us off here with a high-level sense of what is big and new with this release.

Hebner: Well, this is actually a very important announcement as it completes the delivery of Version 7 of the Software Delivery Platform. Earlier in the year, we had announced the team-based part of the portfolio; now this is the desktop. And really, what the theme of the announcement's all about and the new capabilities is empowering the architecture -- particularly in the delivery of software, services and systems -- in a more modular environment such as SOA. In essence, the new capabilities are going to help customers leverage a sound architectural design to more successfully deliver services faster -- particularly with architectural integrity -- in a more geographically diverse or decentralized environment that tends to come with SOA. So if you kind of look at it in total and you look at all the new capabilities, in essence, we're empowering global teams to better implement and manage software and systems architectures with improved life-cycle quality.

Guest: Scott Hebner

Scott Hebner is responsible for leading the development and execution of Rational Software’s worldwide business strategy, offering management, and marketing activities. He also manages the organization’s business partner and channel marketing, and serves on IBM’s Software Group marketing leadership board, which sets direction for the group’s marketing strategy and programs. Previously, he has served as vice president of ISV and Developer Relations, director of e-business marketing, and director of WebSphere® infrastructure software. He has also managed IBM’s development tools marketing programs and IBM's object technology market development group. You can contact him at hebner@us.ibm.com.

Four key things to look for in the new capabilities. One, it will speed SOA results due to the sound architectural design and the automation of service delivery and maintenance. Two, it's going to ensure global architectural integrity and the software quality that gets delivered within, particularly and including support for ... new support for testing within packaged applications such as SAP, Oracle, and Siebel. Important also is the new, simpler, modular systems development approach that we're taking, particularly important for those customers that are building systems and software that is highly coupled, such as maybe in aerospace and defense, where you're building the navigation system for a missile system, or building for a cell phone or analog breaks, and it brings new hardware and software modeling and standards support to that effort. And then finally, you'll see a great deal of enhancements in terms of consumability by not only leveraging the latest and greatest of the Eclipse community innovation in standards, Eclipse 3.2, but also some IBM innovation that will allow our customers in a more modular way to kind of build out the environment that they need at the desktop through a much greater degree of modularity, again, all based into the Eclipse platform.

And so when it's all said and done, it's empowering the "A" in SOA, and we're hoping that this is going to help our customers scale their business of global architecture, design, and quality.

developerWorks: That's great -- very comprehensive. Thank you. And I hear you using that term "delivery," in there -- "delivery platform." I've always heard "development platform" before. Is this a newer term, or is this just a different thing that I've not been paying attention to before?

Hebner: Well, we've been playing on the word delivery because the value of what we can deliver and help our customers with is evolving. And when you think about the people that we are providing products and services to, it's those that are responsible for delivering software to the business. And delivering software is not only developing new software but it could be leveraging existing Web services, it could be building and extending and integrating within packaged applications. So when you think about the capabilities being delivered, it's going to help customers more effectively deliver software against their strategic business imperatives.

And again, the notion of delivery is the end goal that you're trying to do here. And you may develop it, you may outsource it, you may be customizing services, you may be building and integrating within a packaged application scenario. So we wanted to ensure that it's not just about software development of new custom applications but the broader notion of how to more effectively deliver software.

developerWorks: I see -- so a refinement of terms -- just more clarity about what is being delivered here, what's being offered in the platform then.

Hebner: Exactly. But it's still as comprehensive as ever, if not more in terms of software development. But again, there's things in there you can do that are broader than just developing new code.

developerWorks: Lee, can I ask you, how does this complement the Baltic announcement of the team products that was made back in June?

Guest: Lee Nackman

Lee Nackman is responsible worldwide for IBM Rational's product strategy, product development, and customer support. Previously, he was Rational's CTO. He initiated the Eclipse open source tool platform and IBM® WebSphere Studio tool products. He was a founding member of the Board of Stewards for eclipse.org. Prior to joining IBM Software Group in 1998, he held technical and management positions at IBM's Thomas J. Watson Research Center. He was elected to the IBM Academy of Technology in 1998. He has published 50 papers, a book, and holds two patents. You can contact him at lrn@us.ibm.com.

Nackman: It really completes that announcement. Let's just talk about this notion of delivery that you and Scott have just been talking about. In the Baltic announcement, we announced capability for coordinating the overall software life cycle. So this is not just about developing the code but it's also about how do you do the models for architecture, how do you do the requirements gathering, how do you connect requirements with test cases and test results, how do you connect it with builds. And even, how do you take good builds that have passed tests and push those out and deploy them? So it's all about the delivery piece.

Well, what Caspian does is it really adds to that capability. So, as Scott mentioned, it adds new capability for modeling and better capability for modeling of services. It enhances our test capabilities so we can support testing of packaged applications for SAP and for Siebel in ways that we couldn't do back in the Baltic timeframe. It makes it possible to deploy our tools more easily to larger teams than you could do before. Scott mentioned the whole idea of improved consumability. One of the big things that we've been hearing from our customers is they want more flexibility in the ways the tools actually get deployed to the, I'll call them the practitioners rather than the developers, because there's a lot of different kinds of people using these tools. So we've made big steps forward in the ability to do that kind of deployment. So I really view Caspian as part of a one two punch with Baltic.

developerWorks: And Caspian is the internal term for Version 7 that we're talking about here, right?

Nackman: Right, just in the same way that Baltic was the internal name for Version 7 of the Team products.

developerWorks: Right, OK. Well, you talked a little bit about this here just now, but what are other evolutionary changes in IT and in business that have really been the impetus for these new releases?

Nackman: You know, customers are trying very hard to improve their ability to deliver business value. So our customers who are in IT are trying to be more responsive to the changes in business models that customers have, and that means that the IT organizations have to be able to have a good control of the overall life cycle. So when a requirement changes, or a new requirement comes in, how do they manage implementation of that requirement? How do they manage testing of the implementation of that requirement? How do they manage prioritization? All of those sorts of things. And so what we're doing in the software development platform really brings together that whole broad set of capability to meet that kind of challenge.

Now, the other thing is, this is not just about IT; it's also about systems development. So we're hearing very similar kinds of directions from our systems customers where they're not only concerned about developing code but how does their software fit together with the hardware to make a whole system that they're developing? So this is an area where it's really important that they have ways of modeling the architecture, they have ways of understanding how the software interacts with the larger system that they're part of and those kinds of things. So we're seeing this push across the industry both in IT and in systems for more responsiveness and faster ability to do integration of software with other parts of what they're doing.

The other thing that I would point out is that we're seeing in many customers, in both IT and in systems, a need to be able to document and be ready for auditability that they really can track the whole life cycle of this software. So for compliance purposes with various regulations, how do they know exactly what software they deployed? And when they deploy new software, what requirements or what defects are fixed, and how do they document that? Who approved the deployment of this new code, and how is that documented? That's all part of how these two pieces, Caspian and Baltic, fit together because Baltic really provided a lot of the infrastructure for doing that, and Caspian provides the practitioner tools that fit into that infrastructure.

developerWorks: And I think that's a good lead in for Jamie to get in on this discussion a bit. Jamie, could you talk in a little more detail about some of the things that have been mentioned so far, service-oriented architecture, tracking, testing, some of that stuff? Maybe give us some detail on the day to day impact of this for developers?

Guest: Jamie Thomas

Jamie Thomas is vice president of Rational Software Development in Raleigh, N.C. She provides direction for development across the Rational portfolio. Prior to her current role, she was vice president of WebSphere Server Development, providing direction for the development of WebSphere Application Server, WebSphere XD, and Java™ technology teams. She also acted as director of WebSphere Strategy and Communications in the Application Integration Middleware Software organization for IBM. Throughout her career, she has managed product development and planning across multiple software divisions, including various products in the application development family and components of the System z platform. You can contact her at tjamie@us.ibm.com.

Thomas: Well, Scott -- clearly, a key component of what we want to address for developers and their ability to better develop in this world of SOA architectures, right? So we focus on a couple of key dimensions. One is primarily around the management of architectural changes across the life cycle, and another of course is managing this issue of quality across the life cycle. Some of the key elements, we think developers really want to be able to achieve as part of their development process is ensure that they can trace artifacts throughout the life cycle all the way from the requirements phase throughout the modeling phase to production of code and understand of course systematically how that code gets tested and deployed in a production environment. And so when we talk about the end-to-end life cycle we're really talking about this whole management of these assets across the spectrum.

Providing some key capabilities, things like providing the ability to have traceable steps, which is of course a key element in being able to comply with many standards that exist across industries today, which is a key element of governance, which of course goes hand in hand with SOA architectures, typically. Being able to better utilize some of our new capabilities that we've brought into Rational around BuildForge to truly achieve this end-to-end life-cycle deployment aspect, being able to automate the back-end deployment of artifacts into the various production environments, and also being able to really understand customer environments more fully, being able to have repeatable results in those environments and understand production patterns, and being able to replicate those appropriately utilizing the Rational tool set.

Another key element I think that's key for the developers here is just this whole focus on productivity. Our continued focus on standards including Eclipse-based standards, UML standards, Web services standards, and of course the continuation of our strong support for Java standards, are all a key element of the product line that we've announced here with the Caspian update. Some significant changes that I think will increase developer productivity not only from the standards perspective but also in terms of how the products actually get installed and get reflected on the individual desktops. So some key requirements that developers have been asking us for, for quite some time.

developerWorks: So you mentioned some enhanced testing features and products with this release. Tell us a bit more about that, if you would.

Thomas: Yes. We believe in terms of quality management of course the testing and automation of testing is absolutely critical for a lot of companies to really achieve what I've referred to as repeatable results and being able to better predict what's going to occur in the production environment.

We have a couple of products that we've enhanced, the Rational Performance Tester, the Rational Function Tester. In the case of the Performance Tester, we've integrated that with a lot of the Tivoli® product line to ensure that we can basically share information between Rational and Tivoli with Tivoli being predominately focused on the deployment environment. And by being able to share that information that Tivoli basically ascertains to the monitoring time, they can then input that information back into the Performance Tester and be able to drill down a particular performance bottleneck and areas where perhaps we know that there is a problem that we need to analyze and of course fix from an application development perspective.

This whole area of end-to-end life-cycle management including the monitoring aspect, being able to more fully diagnose problems and remediate those problems quickly is a key problem for today's architectures and, of course, SOAs as well. And we think that these enhancements to the testing portfolio will greatly enable customers to solve some of these problems in a much more effective manner.

developerWorks: All a part of this overarching message about governance that you were talking about, isn't it?

Thomas: Exactly. So you know, my thought is we're really looking at a cycle of course that starts with requirements definition, early modeling from a business and architectural modeling perspective, co-production, all the way through building the assets, being able to then understand what was built, test those assets of course, understand how they're performing in a production environment. And so our ability here to integrate between the Rational and Tivoli portfolio is quite critical in achieving that end goal.

developerWorks: Thank you for all of that, Jamie. And, we won't keep you because we know you've got to get on to something else, but we appreciate you taking a few moments to join us for this today.

Thomas: Thanks, Scott, and I look forward to talking to you and this audience in the future.

developerWorks: Absolutely. Again, that was Jamie Thomas, vice president, Rational Software Development.

Now, Scott Hebner, if we could come back to you for a second. I'm wondering after what Jamie said and some of the other things that have been said, if you could give us a little more about how this release enhances and strengthens this drive towards service-oriented architecture.

Hebner: Well, SOA is all about modular software and the ability to create business flexibility by being able to deliver, maintain, integrate, and build new software in a more modular approach. And what we're finding with our customers is that it is very much driving a change in how they do solutions development and delivery, and in many ways, there's some practical realities that become even more important for our customers to focus on ... such as, you know, it becomes critically important that you're linking to the business architecture and the business process models that have been put in place the actual IT architecture and the service models underneath that so that you can automate the delivery of services that fulfill the business process model, keep them in sync, be able to reconcile them, particularly when you get into broad-based use of services.

In addition to that, there's the need to address and control risks that are inherent in a globally distributed environment. Customers begin to manage more and more services, very large numbers of services, and you need to ensure their architectural of how those services work with each other, and make sure that you can reconcile them, the actual code and the applications with the designs. And of course at the same time, while the notion of SOA kind of drives a greater degree of control and governance that's needed to make the overall organization effective, we also need to make sure that we're enabling flexibility for the developer and managing their ability to build out a custom desktop particularly with more and more open source elements being introduced.

So then, when it's all said and done, decentralization and the modularity that SOA brings is really driving a much greater need for a structured approach to architecture, modeling and life-cycle quality management. And that's what the new capabilities in this release help provide developers and the overall customers that are involved in SOA projects.

developerWorks: What about business partner support for this? What are you all seeing on that?

Hebner: Well, as I mentioned earlier on, one of the key parts of the new value that's coming in these products in Version 7 is a much greater degree of modularity in the ability to consume different elements of functionality and kind of configure them to the needs that a developer would have. And part of that is allowing and enabling business partners to build extensions into the platform. We have this whole Ready for Rational program, and we have a whole bunch of new partners who have already enabled new capabilities within the Version 7 desktop products, such as Black Duck for open source software reuse, Clockwork, the systems delivery and embedded development extensions, Exaltech software for helping to modernize existing applications within an SOA environment.

So the business partner has become increasingly important as we move through time here because they're going to help provide some of the added value and capabilities that our customers are going to need in their desktop products and provide the broader set of consulting -- services that are going to help them be successful not only in SOA but any kind of development such as systems development.

developerWorks: Well, this is great. You guys have given us a good sense of why this is an important series of releases and what it represents for everyone involved. Any closing thoughts? Anything we didn't cover here you wanted to share?

Nackman: I'd just like to mention a couple of other things that I think are important about this release. Scott already mentioned that this release is based on Eclipse 3.2. Another thing that we've been hearing from a number of our customers is that, you know, "We already use Eclipse in our shop, and we'd like your tools to just install as plug-ins on top of the Eclipse that we've already deployed." That's another consumability feature that is in Caspian. So we've really put a lot of effort into making sure that the Caspian release products play very well with existing Eclipse deployments, existing Java Virtual Machine deployments. So that's another important theme in this release.

One more thing I'd like to mention is the support for the latest version of the WebSphere Application Server. That's a big step ahead for the Rational Application Developer, Rational Software Architect product in this release.

Hebner: And I'd just add to that, too. It's actually the fifth anniversary of Eclipse. There are over 150 member companies now, over 2.4 million users around the world. It's the basis of nearly 1,300 products. So you know, five years, man -- time really flies. But it just seems to be really on a roll, it's hit a nerve, and the community is continuing to grow. It has real tangible effects on the overall software industry. So this is a timely announcement, as Lee just mentioned, our support for Eclipse, and how we're hoping to really leverage it to provide the consumability and the support for business partners and the ability to adapt our products. But again, playing in the larger, broader community that's out there. And it's an important milestone. Five years, and you know, it will be 10 years before we know it.

Nackman: Yes, absolutely. Another piece of this announcement is the service offering for Eclipse, because again, we're seeing a number of customers who are using Eclipse in their organizations and would like to have support from IBM for their use of Eclipse. And that's a new capability that we're introducing in this release.

Hebner: I guess, Scott, the last thing we should probably wrap up on here is what products are we actually talking about here? We referenced the desktop products as part of the Software Delivery Platform Version 7. But just to be explicit, we're talking about Rational Software Architect, Rational Software Modeler, Rational System Developer, and Rational Application Developer, which are the integrated development environments, and of course, our suite of testing and quality management products such as Rational Performance Tester and Functional Tester and Manual Tester. And, of course, there's some suites and bundles that come along with all of that. But when we talk about the desktop products, that's essentially the configurations that we're talking about there.

developerWorks: And as you said, with the Eclipse part of it it really represents another important point along the road of what is a very neat success story, doesn't it?

Hebner: Yes, it certainly does. And you know, without the community out there, without the thriving innovation that's occurring out there, the value that's adding to our customers is quite significant, and, therefore, we're going to continue to invest and expand on that as we move through time, no doubt.

developerWorks: Lee Nackman, Scott Hebner, thanks again to you both for doing this. Always good to talk to you guys.

Nackman: Thank you, Scott.

Hebner: Thank you.

developerWorks: Again, our guests today were Jamie Thomas, vice president, Rational Software Development; Lee Nackman, vice president of Product Development and Customer Support; and Scott Hebner, vice president of Marketing and Strategy. For everyone at developerWorks, I'm Scott Laningham. Talk to you next time.

把你送进世界500强企业的英文简历

2009-01-05T17:24:00.000-08:00

应聘外企，一份高水准的简历必不可少，英文简历的构成：

　　一、说明信(Cover letter)

　　一封介绍性的信笺，介绍你自己以及你应征的目的，并有机会在其中概述你的技能和你能为公司做出的贡献，大多数公司除了要履历之外还要求附上一封说明信。(An introductory letter which introduces yourself，states your intent，and gives you an opportunity to summarize your skills and sell what you can offer to a company. Most companies require a cover letter in addition to a resume.)主要包括三部分：开场白(Anfang)、自我介绍(Selbstvorstellung)和结束语(Schluss)。

　　二、简历(Resume)

　　一个正规的个人鉴定，描绘出专业目标、工作经历和教育背景以及与某专业相关的其他的活动，或参加的专业组织，等等。这是一种向一个可能成为你老板的人推销你技能和专业技巧的手段。(A formal document which identifies a person，outlines professional goals，describes work history and educational background，and identifies other activities，memberships in professional associations，etc.，which are relevant to a career. It is a tool by which you market or sell your skills and expertise to a potential employer.)

　　英文简历与中文简历内容相似，主要包括：

　　(一)求职目标(Goals)：

　　一份描述你专业抱负或是职业目标的陈述报告。(A statement which expresses your professional ambitions and/or career objectives.)包括：目标(objective)、工作目标(job objective)、职业目标(career objective)、谋求职位(position sought)、希望职位(position wanted)、申请职位(position applied for)等。例：

　　1.Executive and Managerial管理部分：

　　Executive Marketing Director市场行政总监Vice-President副总裁

　　Assistant Vice-President副总裁助理Controller(General)管理员

　　Vice-President of Administration行政副总裁manager经理

　　Production Manager生产经理Operations Manager操作经理

　　Chief Executive Officer(CEO)首席执行官President总统

　　Chief Operations Officer(COO)首席运营官Branch Manager部门经理

　　Controller(International)国际监管Director of Operations运营总监

　　Claims Examiner主考官General Manager总经理

　　Property Manager房地产经理Field Assurance Coordinator土地担保协调员District Manager市区经理Regional Manager区域经理

　　Hospital Administrator医院管理HMO Administrator医疗保险管理

　　Import/Export Manager进出口经理Insurance Claims Controller保险认领管理员

　　Program Manager程序管理经理Insurance Coordinator保险协调员

　　Project Manager项目经理Product Manager产品经理

　　Inventory Control Manager库存管理经理Warehouse Manager仓库经理

　　Manager(Non-Profit and Charities)非盈利性慈善机构管理

　　Manufacturing Manager制造业经理Vending Manager售买经理

　　Telecommunications Manager电信业经理Transportation Manager运输经理

　　Service Manager服务经理Food Service Manager食品服务经理

　　Retail Store Manager零售店经理Assistant Store Manager商店经理助理

　　2.Administration行政部分：

　　Office Manager办公室经理Administrative Director行政主管

　　File Clerk档案管理员Receptionist接待员Secretary秘书

　　Executive Assistant行政助理Executive Secretary行政秘书

　　General Office Clerk办公室文员Typist打字员

　　Inventory Control Analyst存货控制分析Staff Assistant助理

　　Mail Room Supervisor信件中心管理员Stenographer速记员

　　Order Entry Clerk订单输入文员Telephone Operator电话操作员

　　Shipping/Receiving Expediter收发督导员Ticket Agent票务代理

　　3.Education and Library Science教育部分：

　　Daycare Worker保育员Nanny保姆Teacher教师

　　Developmental Educator发展教育家Head Teacher高级教师

　　Foreign Language Teacher外语教师Physical Education Teacher物理教师

　　Guidance Counselor指导顾问Music Teacher音乐教师

　　Library Technician图书管理员Librarian图书管理员

　　Principal校长College Professor大学教授ESL Teacher第二外语教师

　　School Psychologist心理咨询教师Vocational Counselor职业顾问

　　Special Needs Educator特种教育家Teacher Aide助理教师

　　Art Instructor艺术教师Computer Teacher计算机教师

　　Coach教练员Assistant Dean of Students助理训导长

　　Tutor家教、辅导教师Archivist案卷保管员

　　(二)个人资料(Personal Data)：

　　主要是介绍你自己(Introduce yourself)，包括个人的一些自然状况：姓名(name)、年龄(age)、出生日期(date of birth)、住宅电话(home phone)办公电话(office phone)、民族，国籍(nationality)、籍贯(native place)、家庭状况(family status)、婚姻状况(marital status)等。

　　(三)应聘的资格(Qualifications)：

　　在何种程度上，教育背景及工作背景适合从事某一工作。(The degree and/or depth to which a person’s work and educational background is a good fit for a particular job.)如：

　　1.教育背景(Educational background)：

　　即正规学校教育/或培训(A history of a person’s formal schooling and/or training.)包括：学历(educational history )、教育程度(educational background)、知识背景(knowledge background )、所学课程(courses taken)、专业课程(specialized courses)、进修课程(refresher course)、脱产培训(off-job training)计算机科学(computer science)等，及掌握情况。

　　2.工作背景(Work background)：

　　即专职及兼职工作经历。(A history of a person’s professional and/or non-professional employment. )包括：工作经历(work experience)、职业经历(professional history)、具体经历(specific experience)、兼职(Part—time)、实习(Intern)、实际业绩(Performance)、工作成就(achievements)、个人能力(People)、市场开发(Marketing develop)、关键问题的解决(breakthrough)、成功的要素(Element of Success)、胜任力(Competence)、被认命的职位(appointed position )等。

　　3.实力/优势(Strengths)

　　你擅长的工作，你所拥有的积极的个性特点，你想向你未来老板推销的你的一些技能。实力包括较强的思想交流能力、分析能力、技术能力、管理能力、创造力、团结力和可取的个人品质。(Tasks which you feel you excel at，positive personality traits that you feel that you possess，and skills that you sell to a potential employer. Strengths can include superior communication skills，high analytical ability，technical skills，managerial prowess，creativity，people skills，and desirable personality traits.)例如：

　　良好的沟通能力(Good Communication skill)

　　敏锐的商业头脑(Sharp Business Mind)

　　决策及信息高度透明(Transparency)

　　能当机立断(I’m willing to make decisions.)

　　我和他人容易共事。(I work well with others.)

　　我能有效进行时间管理。(I can organize my time efficiently.)

　　(四)弱点(Weaknesses)

　　你认为你自身需要改进的地方，无论是工作习惯，还是专业知识，或是交流能力，等等。任何一个潜在的弱点必须附有能使之转变为一种潜在能力的积极有效的方法。(Areas that you perceive that you need improvement in，whether it be work habits，business knowledge，communication，etc. Any potential weakness must be spun into a positive answer which converts it into a potential strength.)例如：

　　我有时对自己要求过于严格。(I tend to drive myself too hard.)

　　我对别人的能力期望过高。(I expect others to perform beyond their capacities.)

　　我喜欢速战速决。(I like to see a job done quickly.)

　　(五)业余爱好(hobbies)：

　　爱好代表一个人的性格、涵养、为人以及品德，爱好广泛的人往往比较开朗、合群、思维宽阔。例如：

　　弹吉他(play the guitar)、阅读(reading)、话剧(play)、慢跑(jogging)、

　　长跑(long distance running)、集邮(collecting stamps)、打桥牌(play bridge)、打网球(play tennis)、下棋(play chess)、旅游(traveling)、缝纫(sewing)、听交响乐(listening to symphony)、搞泥塑(do some clay scultures)

　　(六)离职原因：

　　最重要的是：应聘者要使招聘单位相信，应聘者在过往单位的离职原因是某些良好的愿望，避免把离职原因说得太详细、太具体;不能掺杂主观的负面感受;不能涉及自己负面的人格特征;尽量使解释的理由为应聘者个人形象添彩。例如：

　　为更专门的工作(for more specialized work)

　　为晋升的前途(for prospects of promotion)

　　为更高层次的工作责任(for higher responsibility)

　　为扩大工作经验(for wider experience)

　　由于公司倒闭(due to close-down of company)

　　由于雇用期满(due to expiry of employment)

　　(七)薪酬奖金

　　应聘之前应该做到对相关行业及相关职业的薪酬有个大致了解，同时最好先能确定一下自己的底线，但除金钱外，应聘者还应该将该单位的员工福利如假期，发展空间，行业前景等因素考虑进去，这样作决定时才能不目光短浅，才能符合自己事业发展的整体规划。如：基薪(Base Salary)、全面薪酬(Total Compensation)、年度奖金(Annual Bonus)、业绩奖金(Performance Units)、红利(Benefits)、津贴(Perquisites)、特殊津贴(Perquisites)、业绩股份(Performance Shares)等。

　　宏威职业顾问友情提示：

　　英语，作为交流沟通的工具，已成为当今社会的一种流行元素，应聘外企、名企用英文简历作为敲门砖也已成为时尚。制作一份精致的英文简历，更容易吸引HR眼球，你要坐上英文简历的快艇，让它把你送到500强企业的彼岸，插上理想腾飞的翅膀，进入外企、名企的天空，自由地翱翔。

利用模板实现单例模式

2008-12-10T08:21:00.000-08:00

利用模板实现单例模式，这样我们就可以对任意类型创建单例模式
singleton.h

#ifndef SINGLETON_H
#define SINGLETON_H
#include

template< class T >
class Singleton
{
class InstanceHolder
{
public:
InstanceHolder() : mObject(0) {}
~InstanceHolder() { delete mObject; }
T* get() { return mObject; }
void set(T* p) { delete mObject; mObject = p; }

private:
InstanceHolder(const InstanceHolder&);
InstanceHolder& operator=(const InstanceHolder&);

private:
T* mObject;
};
public:
static T* instance()
{
if (!mFlag)
{
pthread_mutex_lock(&mMutex);
if (!mFlag)
{
mInstance.set(new T());
mFlag = 1;
}
pthread_mutex_unlock(&mMutex);
}
return mInstance.get();
}

private:
static InstanceHolder mInstance;
static volatile int mFlag;
static pthread_mutex_t mMutex;

Singleton();
Singleton(const Singleton&);

Singleton& operator=(const Singleton&);
};

template typename Singleton::InstanceHolder Singleton::mInstance ;
template volatile int Singleton::mFlag = 0;
template pthread_mutex_t Singleton::mMutex = PTHREAD_MUTEX_INITIALIZER;

#endif

下面我们利用这个模板来创建我们所需要的单例类型

app.h

#ifndef APP_H
#define APP_H
#include "singleton.h"
#include

using namespace std ;

class ServiceListener{
public:
ServiceListener(){cout << "ServiceListener" << endl ;};
~ServiceListener(){cout << "~ServiceListener" << endl ;};
};
class ServiceController : public ServiceListener
{
public:
ServiceController(){cout << "ServiceController" << endl;}
~ServiceController(){cout << "~ServiceController" << endl;}

int init(){cout << "init" << endl ;};
int run(){cout << "run" << endl ;};
int start(){cout << "start" << endl ;};
int stop(){cout << "stop" << endl ;};
};

typedef Singleton ServiceControl;

#endi

app.cc

#include "app.h"
#include "singleton.h"

int main()
{
ServiceController *ctl = ServiceControl::instance() ;
ctl->init() ;
ctl->run() ;
ctl->start() ;
ctl->stop() ;
return 0 ;
}

每日英语

2008-12-10T07:53:00.000-08:00

MARILYN: What do you think of this?

DIANE: I don't know. It's a little old-fashioned. What kind of party is this again?

MARILYN: It's a party for the opening of this new club downtown so I want something special. Some famous people may be there.

Have you ever met a famous person?

DIANE: Like who?

MARILYN: My friend said Tom Cruise and Jennifer Lopez might be there.

We can also say Tom and Jennifer may be there.

DIANE: Are you serious?

MARILYN: Yes, they're good friends with the owner.

DIANE: Wow, it sounds like it will be a fun party. When is it?

MARILYN: Saturday night. It starts at 8.

DIANE: Are you going with John?

MARILYN: Maybe. He might not have enough time. He has to go to Brazil next week. If he can't come, do you want to go with me?

Do you have enough time to study English?

DIANE: Of course! Maybe I'll meet Tom Cruise?

MARILYN: Super. What do you think about this one? Is it formal enough?

Do you prefer formal or casual clothes?

DIANE: Yeah, it's nice. But, it's a little expensive, isn't it?

MARILYN: Yeah, it is four hundred dollars.

DIANE: Maybe we should go to another store. I know this one store that has really stylish clothes and the prices are very reasonable.

每日英语

2008-12-09T07:45:00.000-08:00

STANLEY: Hello, Becky? This is Stanley.

BECKY: Hi, Stanley! What's up?

STANLEY: Becky, I just made a big decision. I'm going to travel around the world and I'd like you to come with me.

BECKY: The entire world?

STANLEY: Yes. All of it. I'm going to begin in Los Angeles and go west. I'm not going to stop until I come to Los Angeles again.

BECKY: That sounds like an adventure!

STANLEY: It will be an adventure. Do you want to come?

BECKY: Of course I do! How are we going to travel?

STANLEY: I'm not sure yet. But I expect we'll travel in many ways. Sometimes we'll take a plane or a train. Other times we'll ride the bus or go by taxi. Perhaps we'll rent a car or even a motorcycle.

BECKY: How exciting! What should I bring? Will I need a lot of clothes?

STANLEY: You'll need clothes for all kinds of weather, and of course you should also bring a notebook.

BECKY: Why should I bring a notebook?

STANLEY: We're going to write about all of the places we visit.

BECKY: Oh. Do you mean I should bring a travel log?

STANLEY: Yes! Bring a travel log and a pen.

BECKY: I won't forget. I'm so excited!

开博第一帖

2008-12-07T18:51:00.000-08:00

一直希望有自己的博客，今天在google创建了，希望朋友们多捧场.