FormsAuthentication Class
Monday, November 10, 2008
Forms authentication failed for the request (solution)
How To: Configure MachineKey in ASP.NET 2.0
FormsAuthentication Class
FormsAuthentication Class
Wednesday, September 17, 2008
Windows Workflow Foundation Tutorial Series
Windows Workflow Foundation Tutorial Series
http://joeon.net/post/2008/02/Windows-Workflow-Foundation-Tutorial-Series.aspx
Monday, September 1, 2008
Tuesday, August 26, 2008
Monday, August 25, 2008
Tuesday, August 19, 2008
136 (SKILL INDEPENDENT IMMIGRATION)
The steps:
Visit below link to find out more:
Australian Computer Society
Visit below link to find out more:
Professionals and other Skilled Workers
Australian Computer Society
ACS Assessment - Skilled Occupations
| ASCO Codes | ||
| Information Technology Officer - Applications and Analyst Programmer | 2231-17 | |
| Information Technology Officer - Computer Systems Auditor | 2231-21 | |
| Information Technology Officer - Computing Professionals (not elsewhere classified) | 2231-79 | |
| Information Technology Officer - Software Designer | 2231-15 | |
| Information Technology Officer - Systems Designer | 2231-13 | |
| Information Technology Officer - Systems Manager | 2231-11 | |
| Information Technology Officer - Systems Programmer | 2231-19 | |
| MIGRATION OCCUPATIONS IN DEMAND (MODL) | |
|---|---|
| Managers and Administrators | ASCO code |
| Child Care Coordinator | 1295-11 |
| Engineering Manager | 1221-11 |
| Professionals | ASCO code |
| Accountant | 2211-11 |
| Anaesthetist | 2312-11 |
| Architect | 2121-11 |
| Chemical Engineer | 2129-17 |
| Civil Engineer | 2124-11 |
| Computing Professional - specialising in CISSP * | 2231-79 |
| Computing Professional - specialising in C++/C#/C * | 2231-79 |
| Computing Professional - specialising in Data Warehousing | 2231-79 |
| Computing Professional - specialising in Java * | 2231-79 |
| Computing Professional - specialising in J2EE * | 2231-79 |
| Computing Professional - Linux | 2231-79 |
| Computing Professional - .Net technologies | 2231-79 |
Wednesday, August 13, 2008
5 regular mistakes in public speaking
Author: Vince Stevenson
How to impress your colleagues and clients with a successful speech or presentation that will enhance promotional prospects or win new business.
Copyright © 2007 The College Of Public Speaking
1. The audience will listen because I'm a subject matter expert and what I have to say is interesting.
This is probably one of the most frequent mistakes made by speakers. We all like to think that we know our stuff, and many people do. But that alone will not engage your audience. Albert Mehrebian the US Educational Psychologist's research demonstrated that only 7% of your presentation's impact will be your words. Only 7%... This is worrying for subject matter experts. You could prepare for weeks, select the best words and key messages, you could have the best introduction, middle section and ending than any speaker on the bill, but your impact could be negligible.
A few year's ago I became a school governor and as such, I was offered training sessions by my local Education Authority. The general standard of the 2 hour presentations was good. One evening, the guest speaker, a man who had worked in education all his life with a career that spanned being a headmaster, Ofsted inspector and a senior role in the Ministry of Education and Science; what this fellow didn't know about the history of secondary education was not worth knowing. However, he ended every sentence with a pronounced hmmmmmmmmm. Imagine that 6 times per minute, for two hours.... I nearly lost the will to live.
Tip - Listen and react to feedback from your colleagues. I'm certain that over the course of this fellow's long and distinguished career, many people must have mentioned his verbal mannerisms. If your company culture prohibits you from giving constructive feedback, seek professional help. Advice from consultants is more likely to be accepted because it is seen to be given objectively.
2. Speaking too fast.
Nervous and inexperienced speakers always remind me of the 100 metres sprint. They hear the gun, they're out of the blocks fast and they can't wait to get it over with. This is not unusual - it is the normal reaction to any potentially stressful situation. Let's close our eyes, do it, and get it over with. It's a bit like going to the dentist. However, some speakers do not even devote themselves to such minimal preparation.
Tip - for each minute of your speech, spend ten minutes of preparation on it. Watch yourself on video and ask yourself if you're delivering too fast.
3 Keep it short and simple and always leave them wanting more. The best way to maintain the attention of an audience is to start with a gripping opening, develop a maximum of three themes or key messages, and conclude with a message that pulls the introduction and key messages together with impact. An experienced speaker can make this look simple and seamless, but we're looking at perhaps 0.001% of the population. We all need help developing this skill. If you speak for over 10 minutes it's almost inevitable that the structure will suffer and you will lose your audience because you haven't signposted your structure well enough. Tell them what you'll tell them, tell them, and tell them what you've told them.
Tip - keep it short and simple and use your best material at the beginning and the end of your speech. Start and end with impact.
4. Maintaining eye-contact with your audience. For the new or inexperienced speaker, eye-contact is one of the hardest aspects of speaking. Looking into the eyes of strangers does not come naturally to most of us. Indeed, in some cultures young people looking directly into the eyes of their elders is seen as a mark of disrespect. However, as a speaker, your audience is your primary concern. Remember that without audiences, we do not need speakers. Making eye-contact and engaging your audience is critical to success. It shows respect and demonstrates confidence. We listen and learn most from confident speakers. Life is a busy place, and when we invest time in a speaker, nobody likes to feel they have wasted their time.
Tip - if you find eye-contact difficult, try it out with friends and family in regular conversations. You will have a major impact on those with whom you are conversing. It' very difficult (almost rude) to disengage eye-contact with somebody when you're having a pleasant chat. Bear that in mind when you're making a speech and you'll do very well.
5. Speaking in a dull and monotonous voice. Throughout our professional careers, how many times have we endured the monotonous speaker?
In my case rather too often. Tonal variety is what adds massive impact to your speech or presentation. We need some highs and lows allied to seamless changes in pitch and pace. These effective techniques help to keep your audience engaged and participating in your presentation.
Mehrebian's research demonstrated that 38% of what an audience remember is down to the effective use of tonal variety. A massive 55% relates to your body language. If you send a mixed message, don't be surprised if the message is dropped. A key factor in any speech or presentation is simply this:
Tip - It's not what you say. It's the way that you say it.
Scenario 1: You're trying to find the channel with the live football. Suddenly, your wife sitting in the opposite armchair says, ‘Do you love me?' You continue flicking through the channels, you don't look back at her and you eventually say the words, ‘Of course, I love you.'
Scenario 2: You're trying to find the channel with the live football. Suddenly, your wife sitting in the opposite armchair says, ‘Do you love me?'
You stop flicking through the channels with the remote and put it down. You walk across the room and take your wife by the hand, gently and sincerely you look her in the eyes, caress her cheek and say, ‘Of course, I love you.'
Notice that the same words are used, but which do you think conveys the stronger message?
About Author
Vince Stevenson is one of England's greatest speaking enthusiasts, having competed for and won many prestigious competitions. Vince is involved with speaking at many levels and has just finished his year as District President of the South-Eastern District of the Association of Speakers Clubs having been involved in its educational development for many years. Vince is a founder and lead trainer at the College of Public Speaking, a business dedicated to improving effective communication skills in industry. He is also an in demand after-dinner speaker. http://www.collegeofpublicspeaking.co.uk
Article Source: http://www.1888articles.com
Tuesday, August 12, 2008
工作面试时最难的25个问题
简介:工作面试时最难的25个问题,很好的准备是成功的一半。如果你是一个对目前的职位不满意,正着手去在新的一年里找到一个新的职位,这篇文章就是你的 一个帮手。工作面试是你去面对未来的老板的征途中最重要的一个过程。你必须像进行一个击剑锦标赛或着一个国际象棋比赛那样的坚韧和敏捷来对待面试。
准备是成功的一半如果你是一个对目前的职位不满意,正着手去在新的一年里找到一个新的职位,这篇文章就是你的一个帮手。工作面试是你去面对未来的老板的征途中最重要的一个过程。你必须像进行一个击剑锦标赛或着一个国际象棋比赛那样的坚韧和敏捷来对待面试。
Morin是纽约的Drake Beam Morin公司的董事长,Cabrera是该公司的主席。该公司是国家主要的新职介绍公司,办公所在地在费城。
1.介绍你自己
这 个问题通常是一个面试的开始的第一个问题,要额外的小心不要滔滔不绝。尽可能的让你的回答在一分钟,最多2分钟的时间内结束。你的回答应该包含以下4个主 题:早期生活,教育背景,工作背景以及最近的工作经验。要着重强调最后的那个主题。要牢记这个问题通常是一个热身的问题,不要把你的最重要的观点浪费在这 个问题上。
2.你对我们公司有什么样的了解
你必须能够谈论关于这个公司的产 品,服务,收入,业界声望,形象,目标,存在的问题,管理风格,职工,历史和企业文化等问题。但是不要表现出你对这个公司的一切都了如指掌。让你的回答能 够体现出你对该公司做了一些研究,但是不要让面试官被你打败(overwhelm),并表现出你希望能够了解关于公司更多的情况。
你可以用这样的态度来开始回答问题:“在我的寻找工作的过程中,我调查研究了很多公司,出于如下的理由,贵公司是我感兴趣的公司之一:”。
用一个积极的态度来回答这个问题,不要这样说:“每个人都告诉我这个公司处于困境中,有各种样的麻烦,这就是我来这儿的原因”,即是那的确是你在这儿的理由。
3.为什么你希望来我们公司工作?
最糟糕的答案就是“因为我喜欢人”。要是你喜欢的是动物,那你去哪工作呢?
在 这个问题的回答上,并且贯穿整个面试的过程中,一个优秀的答案总是来自于你所作的调查研究,这样的话你可以从公司的需要那个方面来回答。你可能说你的研究 表明这个公司所做的工作正是你说希望参与的,并且他们做这个工作的方式极大的吸引了你。例如,如果这个公司由于强大的管理而著称,纳闷你的答案可以提到这 个事实,并表示你希望成为这个小组的一员。如果这个公司着重强调研发,那么就强调你希望创造你的事物,而你知道这个公司非常鼓励这样的行为。如果这个公司 强调经济控制,你的答案就应该包含对数字的热爱。
如果你觉得你必须捏造一个答案,例如如果这个公司强调研发,但是你觉得你必须提到这一点而实际上你对这根本不感兴趣,那么你可能根本不应该参加这个面试,因为你可能根本不会考虑在这个公司工作。
你的之前的准备必须包括对这个公司做详尽的了解,来避免到一个你无法发挥才干或者根本不想去的公司面试。大多数人都不擅长说谎,所以在面试中欺瞒面试官是一件很困难的事情。即使你成功的做到了这一点,你所获得的也只是一个你不想参加的工作
4.你可以为我们完成哪些其他人做不到的事情?
这 个问题上,你有权利或者是义务来自吹自擂。谈论一些你完成工作的记录,提到你简历中的独特之处,或者列出你职业生涯中的成就。告诉别人,你的技能和兴趣在 获取这些结果的过程中发挥了很大的作用,并使得你很有价值。提到你能够合理的安排工作优先顺序,找出问题,并利用你的经验和精力来解决问题。
5.你觉得这个职位最吸引你的地方是什么?最不吸引你的地方又是什么?
列出3到4个这个工作吸引人的方面,然后提出一个简单的不重要的不吸引人的问题。
6.为什么我们应该雇佣你?
参见问题4, 考虑你的能力,你的工作经历和你的干劲。
7.你希望在工作中能够获得什么?
让你的答案来源与这个公式提供的机会。谈论你希望能够大展身手并获取认可的要求。让你的答案基于工作机会而不是个人的要求
8.谈论一下你对你应聘的这个职位的定义
你的答案应该简短并且是基于工作要求的。考虑这个工作的责任和义务。在你回答问题之前确定你真正的了解这个职位所涉及的方方面面。如果你不确定,就去问面试官,他可能会帮你回答这个问题。
9.你需要多久能够对公司做出显著的贡献?
答案要实际一点。可以这样回答,尽管你希望从第一天开始就能够满足公司紧迫的要求,并开始发挥作用,但是你可能需要6个月到1年的时间来足够了解这个公司及其需要来做出很大的贡献。
10.你会在公司工作多久?
可以这样回答,你对在这个公司的职业生涯很感兴趣,可是也得承认你必须能够不断感觉到有挑战才能够继续在任何公司呆着。可以考虑这样的语句“只要我们双方都感觉有收获”。
11.你的简历显示你的能力超出了这个工作的要求,你是如何认为的?
强 调你对在这个公司开始一个长期的合作的兴趣,你可以说你认为如果你在这个职位上表现的很好,公司还会为你提供新的机会。也要提到一个好公司需要好的职员。 有检验的职员总会有很好的奖励;既然你是如此的很是这个职位,雇主将会很快从他的投资中获得回报。一个发展中的,充满活力的工资永远不会嫌天才多的。
12.你的管理方式是什么样的?
你 必须对这个公司的风格有足够的了解,这样才能让你的管理风格对其进行补充。可能的风格包括:基于任务的(我喜爱问题-研究那些是错误的,选择一个解决方案 并完成),基于结构的(我做出的任何一个管理的决定是基于它是如何影响问题的底线的),或者是家长式作风的(我致力与管理好我的每一个下属,并给他们指引 正确的方向)。
民主参与式的风格是目前比较流行的一种:一个开放的管理方式,通过激励手下并根据所负责的事情分派任务来完成每一件事情。
当你考虑这个问题的时候,要思考你的风格是否会让你在这个公司里高兴并有效率的工作。
13.你是一个合格的经理吗?你可以举一些例子吗?你是否觉得你有顶级管理人员的潜力?
保证你的答案是基于成果和任务的。通过你职业生涯中的一些例子来加固你的论点。强调你的经验和精力
14.当你招聘人手的时候你需要什么类型的?
考虑一些技能方面的问题。主动性,以及能够舒服和有效的与其他人一起工作的适应性。提到你希望雇佣一些看起来能够在公司中获得提升的人。
15.你是否曾经不得不解雇一些员工?是什么理由?你是如何解决这个情况的?
要承认这个情况不是容易解决的,但是你还是很好的解决了,不管是从公司角度还是从个人角度。让他们知道,和其他人一样,你不喜欢这种让人不乐意的工作,但是你可以有效的富有人情味的解决问题,尤其是在要解雇某个人的时候。
16.你认为作为一个经理或者高级行政人员最困难的事情是什么?
要提到指定计划,指定和成本控制。最困难的任务是要去激发并管理雇员来完成一些计划中的事情,并且按时的在预算范围内完成任务。
17.在我们这个行业中你觉得什么是最重要的趋势?
一样要准备两到三个趋势来阐明你对所在行业的是多么的了解。你可以需要考虑技术上的挑战或者机会,金融环境甚至管理的需求作为你所应该考虑收集的关于你的行业说面对的状况。
18.你为什么离开你现在的工作(上一个工作)?
在不伤害你自己的情况下要简明扼要并诚实的回答这个问题。回溯到你寻找工作的计划阶段,那时你正在把这个话题当作你的工作经历。如果你是在一次公司裁员中被裁掉的,直接说出来好了;否则的话,要指明这次离职是你自己的决定,你自己行动的结构,不要特到任何关于性格冲突等。
19.你觉得放弃原来所有的福利待遇等来寻找一个新的工作是什么感觉?
要提到你很自然的担心这一点,但是并不很恐慌。你愿意为寻找到合适的工作而冒一点风险。不要说,你对安全感比成功的完成工作更感兴趣。
20.在你上一份工作中,你最喜欢那个方面的特点?最不喜欢哪个?
要小心而计息的回答这个问题。要多说你喜欢的特性,而少说你不喜欢的。不要引用个人的问题。如果你使得你的上一份工作听起来很糟糕,面试官会疑问你为什么还能在上一份职位上一直待到现在。
21.你如何看待你的老板?
要尽可能积极的回答这个问题。你潜在的未来的老板很希望能够了解你未来在相似的场合会如何谈论他。
22.你在现在的年龄中为什么不能赚到更多?
要告诉他这是你寻找新的工作的理由之一,不要处于守势。
23.你希望这个职位的薪水是多少?
讨论薪水是一个很微妙的问题。我们建议你在条件允许的情况下尽可能的拖延用一个精确的数据来回答这个问题。你可以说,“我知道这个工作的薪水的大概范围是￥---到￥---。这个对于我来说是合适的价位。”你也可以用一个问题来回答这个问题:
“你可能在这个问题上可以帮助我。你能否告诉我在公司中对相似职位的工作的大概薪水是多少?”。
如 果你是在一个最初的面试中遇到这个问题,你可以说你觉得你需要更多的了解这个职位的职能才能够对这个问题有个有意思的回答。在这个问题上通过询问面试官或 者人事高级主管或者自己去寻找结果,你可以尝试去获得这份工作是由有一个工资等级。如果有,并且你能够接受,那么直接回答你满意这个薪水范围好了。
如果面试官继续纠缠这个问题的话,你可以说“我现在的薪水是￥--。和其他人一样,我希望能够提升这个数字,但是我主要的兴趣还是在工作本身。”要记住,获取一个新的工作这件事本身不会使得你能够赚到更多的钱。
如果一个猎头公司也参与了此事的话,你的联系人可能可以帮助你解决这个薪水的问题。他甚至可以帮你介入此事。例如,如果他告诉你这个职位的待遇,然后你告诉他你现在已经赚那么多的,并且希望待遇能够适当的提升,他可能会去雇主那然后提议给你增加10%的待遇。
如 果没有获得关于这个职位的合适的信息,而面试官还继续这个话题的话,你可以用一个具体的数字来回答这个问题。你不能给别人留下待遇完全没有影响你将会接受 任何待遇的印象。如果你年薪8W的话,你不可能没有变现出放弃自己的时候,说3.5W一年也是可以接受的。(如果你是在做工作的一个彻底的变化的话,这种 情况可能也是有道理,可以理解的)。
不要很快就把你自己卖掉:),但是要继续的强调这个工作本身才是你最看重的东西。面试官可能会去判断你希望从这个工作的待遇是多少哦。不要给面试官留下金钱对你来说是唯一重要的事情的感觉。把薪水的问题和工作本身挂钩。
但是无论合适可能的话,在你到面试过程的最后一个阶段之前,少谈论薪水的问题。到那个阶段的时候,你就应该知道,这个公司对你有很大的兴趣,这个时候在谈论薪水待遇的话就会有很大的余地了。
24.你长期的目标是什么?
回到你寻找工作的计划阶段。不要这样回答“我希望能够得到你广告中的工作”。把你的目标与你面试的公司关系起来,“在你们这样一个公司,我希望能够...”
25.你目前位置在工作中是多么的成功?
你要回答,总的来说你对你目前为止的职业生涯是很高兴很满意的。列举一些生活中普通的琐事,你觉得你完成的很好,没有怨言。
要想别人展现一个积极和自信的面貌,但是不要夸大其词。例如这样的回答“所有的事情都特别的好!我不能想象一个更好的事情了!我非常的开心。”,会使得面试官觉得你是不是在愚弄他或者你自己。最具有说服力的答案通常都是相当自信的。
英文电子邮件高频句式
1. Greeting message 祝福
Hope you have a good trip back. 祝旅途愉快。
How is the project going on? 项目进行顺利吗?
2. Initiate a meeting 发起会议
I suggest we have a call tonight at 9:30pm (China Time) with you and Brown. Please let me know if the time is okay for you and Ben.
我建议我们今晚九点半和Brown小聚一下,你和Ben有没有空?
I would like to hold a meeting in the afternoon about our development planning for the project A.
今天下午我建议我们就A项目的发展计划开会讨论一下。
We'd like to have the meeting on Thu Oct 30. Same time.
十月三十号(周三),老时间,开会。
Let's make a meeting next Monday at 5:30 PM SLC time.
下周一盐湖城时区下午五点半开会。
I want to talk to you over the phone regarding issues about report development and the XXX project.
我想跟你电话讨论下报告进展和XXX项目的情况。
3. Seeking for more information/feedbacks/suggestions 咨询信息/反馈/建议
Shall you have any problem accessing the folders, please let me knows.
如果存取文件有任何问题请和我联系。
Thank you and look forward to having your opinion on the estimation and schedule.
谢谢你,希望能听到更多你对评估和日程计划的建议。
Look forward to your feedbacks and suggestions soon.
期待您的反馈建议!
What is your opinion on the schedule and next steps we proposed?
你对计划方面有什么想法?下一步我们应该怎么做?
What do you think about this?
这个你怎么想?
Feel free to give your comments.
请随意提出您的建议。
Any question, please don't hesitate to let me know.
有任何问题,欢迎和我们联系。
Any question, please let me know.
有任何问题,欢迎和我们联系。
Please contact me if you have any questions.
有任何问题,欢迎和我们联系。
Please let me know if you have any question on this.
有任何问题,欢迎和我联系。
Your comments and suggestions are welcome!
欢迎您的评论和建议!
Please let me know what you think?
欢迎您的评论和建议!
Do you have any idea about this?
对于这个您有什么建议吗?
It would be nice if you could provide a bit more information on the user's behavior.
您若是能够就用户行为方面提供更多的信息就太感激了!
At your convenience, I would really appreciate you looking into this matter/issue.
如果可以,我希望你能负责这件事情。
4. Give feedback 意见反馈
Please see comments below.
请看下面的评论。
My answers are in blue below.
我的回答已标蓝。
I add some comments to the document for your reference.
我就文档添加了一些备注,仅供参考。
5. Attachment 附件
I enclose the evaluation report for your reference.
我附加了评估报告供您阅读。
Attached please find today's meeting notes.
今天的会议记录在附件里。
Attach is the design document, please review it.
设计文档在附件里,请评阅。
For other known issues related to individual features, please see attached release notes.
其他个人特征方面的信息请见附件。
6. Point listing 列表
Today we would like to finish following tasks by the end of today:1…….2…….
今天我们要完成的任务:1…….2…….
Some known issues in this release:1…….2…….
声明中涉及的一些问题:1…….2…….
Our team here reviewed the newest SCM policy and has following concerns:1…….2…….
我们阅读了最新的供应链管理政策,做出如下考虑:1…….2…….
Here are some more questions/issues for your team:1…….2…….
以下是对你们团队的一些问题:1…….2…….
The current status is as following: 1……
2……
目前数据如下: 1……
2……
Some items need your attention:1…….2…….
以下方面需提请注意:1…….2…….
7. Raise question 提出问题
I have some questions about the report XX-XXX
我对XX-XXX报告有一些疑问。
For the assignment ABC, I have the following questions:…
就ABC协议,我有以下几个问题:……
8. Proposal 提议
For the next step of platform implementation, I am proposing…
关于平台启动的下一步计划,我有一个提议……
I suggest we can have a weekly project meeting over the phone call in the near future.
我建议我们就一周项目开一个电话会议。
Achievo team suggest to adopt option A to solve outstanding issue……
Achievo团队建议应对突出问题采用A办法。
9. Thanks note 感谢信
Thank you so much for the cooperation感谢你的合作!
Thanks for the information
谢谢您提供的信息!
I really appreciate the effort you all made for this sudden and tight project.
对如此紧急的项目您做出的努力我表示十分感谢。
Thanks for your attention!
谢谢关心!
Your kind assistance on this are very much appreciated.
我们对您的协助表示感谢。
Really appreciate your help!
非常感谢您的帮助!
10. Apology 道歉
I sincerely apologize for this misunderstanding!
对造成的误解我真诚道歉!
I apologize for the late asking but we want to make sure the correctness of our implementation ASAP.
很抱歉现在才进行询问,但是我们需要尽快核实执行信息。
沪江英语 - 英语口译
Tuesday, July 29, 2008
Items of ASP.NET need to investigate
- ASP.NET Video #2: Create a Multi-Lingual Site with Localization
- Multiple file uploads in ASP.NET: Video #33, #34
- ASP.NET Video #46: Configure an ASP web site for a .Net framework version
Tuesday, July 22, 2008
Thursday, July 3, 2008
Don't Make These 10 Cover Letter Mistakes
by Katharine Hansen, Ph.D. from http://www.quintcareers.com/cover_letter_mistakes.html
Your cover letter shows employers how well you express yourself. It can also demonstrate that you are savvy in the ways of marketing yourself and selling your best qualifications. A good cover letter can entice the recipient to review your resume. A bad cover letter, on the other hand, can nip your chances in the bud. Here are 10 mistakes that contribute to bad cover letters.
To ensure that your cover letter is effective, avoid these mistakes:
1. Sending your resume without a cover letter.
Sure, there are some employers that don't read them or place much importance on them. But since you don't know whether the employer you're writing to reads and values cover letters or not, you must include a letter.
2. Failing to address the letter to the specific name of the recipient.
Addressing the letter to "Dear Personnel Director/HR Director," "To Whom It May Concern," "Dear Sir or Madam" (or worse, "Dear Sirs") instead of a named individual are all lazy approaches that show the employer that you were not concerned enough to find out the name of the person with the hiring power. It's not always easy to find the name of the specific hiring manager, but try to do so if at all possible. Usually, you can just call the company and ask who the hiring manager is for a given position. Tap into your personal network to learn the names of hiring managers. Let's say a company post an opening online. You know someone who works at the company. Ask your contact to find out the name of the person hiring for that position. Also use the library, phone book, and Internet to track down names of hiring managers.
The worst-case scenario is that your letter will begin "Dear Hiring Manager for [name of position]:" It's not the best approach, but if you absolutely cannot find a name, this salutation does at least provide some specificity.
3. Telling the employer what the company can do for you instead of what you can do for the company.
This mistake is particularly common among new college graduates and other inexperienced job-seekers. In most cases, employers are in business to make a profit. They want to know what you can do for their bottom line, not what they can do to fulfill your career dreams. Tell the employer how you can meet his or her needs and contribute to the company.
4. Leaving the ball in the employer's court.
Too many cover letters end with a line like this: "I look forward to hearing from you." Proactive cover letters, in which the job-seeker requests an interview and promises to follow up with a phone call, are far more effective. Don't be vague about your desire to be interviewed. Come right out and ask for an interview. Then, take your specific action a step farther and tell the recipient that you will contact him or her in a specified period of time to arrange an interview appointment. Obviously, if you say you will follow up, you have to do so. If you take this proactive approach and follow up, you will be much more likely to get interviews than if you did not follow up. This follow-up aspect is another good reason to obtain the specific name of the hiring manager. Here's a sample closing paragraph requesting specific action and describing the writer's planned follow-up.
I would like to be considered for a sales position in which someone of my background could make a contribution. I will contact you soon to arrange for an interview. Should you require any additional information, I can be contacted at the phone numbers listed above.
5. Being boring and formulaic.
Don't waste your first paragraph by writing a boring introduction. Use the first paragraph to grab the employer's attention. Tell the employer why you are writing and summarize the reasons you are qualified for the position, expanding on your qualifications in later paragraphs. Read more. Don't use such cliches as "Enclosed please find my resume" or "As you can see on my resume enclosed herewith." Employers can see that your resume is enclosed; they don't need you to tell them. Such trite phrases just waste precious space. Write a letter that will make the employer want to get to know you better.
6. Allowing typos, misspellings, or incorrect grammar/punctuation into your letter.
Your letter reflects your ability to write and communicate. Be sure your document is letter-perfect before sending it out. Proofread your letter. Put it down and proof it again a few hours later with a fresh eye. Then enlist a friend to review it for errors.
7. Rehashing your resume.
You can use your cover letter to highlight the aspects of your resume that are relevant to the position, but you're wasting precious space -- and the potential employer's time -- if you simply repeat your resume.
8. Failing to specifically tailor your letter to the job you're applying for.
If you're answering an ad or online job posting, the specifics of your cover letter should be tied as closely as possible to the actual wording of the ad you're responding to. In his book, Don't Send a Resume, Jeffrey Fox calls the best letters written in response to want ads "Boomerang letters" because they "fly the want ad words -- the copy -- back to the writer of the ad." In employing what Fox calls "a compelling sales technique," he advises letter writers to: "Flatter the person who wrote the ad with your response letter. Echo the author's words and intent. Your letter should be a mirror of the ad." Fox notes that when the recipient reads such a letter, the thought process will be: "This person seems to fit the description. This person gets it."
A particularly effective way to deploy the specifics of a want ad to your advantage is to use a two-column format in which you quote in the left-hand column specific qualifications that come right from the employer's want ad and in the right-hand column, your attributes that meet those qualifications. The two-column format is extremely effective when you possess all the qualifications for a job, but it can even sell you when you are lacking one or more qualification. The format so clearly demonstrates that you are qualified in so many areas that the employer may overlook the areas in which you lack the exact qualifications. See a sample letter in a two-column format.
9. Rambling on too long and telling the story of your life/career.
Keep you letter as brief as possible. Never, never more than one page. Keeping to four or five paragraphs of no more than three sentences each is a good guideline. Using bullet points in the letter is a good way to break up blocks of text and interest the reader. Some job-seekers tend to use their cover letters to provide a narrative of their life or career. That's not what the letter is all about; it's a marketing tool that should focus on the qualifications that will sell you to the employer. Your letter should answer the question that the employer will be asking while reading the words you've written: "Why should I hire this person?" Answer with your Unique Selling Proposition. Use simple language and uncomplicated sentence structure. Ruthlessly eliminate all unnecessary words.
10. Using wimpy language.
Avoid such phrases as "I feel" and "I believe." Your statements will be much stronger without them. It's best to either leave off the qualifier or use a stronger qualifier, such as "I am confident," I am convinced," or "I am positive." Read more.
Questions about some of the terminology used in this article? Get more information (definitions and links) on key college, career, and job-search terms by going to our Job-Seeker's Glossary of Job-Hunting Terms.
Your cover letter shows employers how well you express yourself. It can also demonstrate that you are savvy in the ways of marketing yourself and selling your best qualifications. A good cover letter can entice the recipient to review your resume. A bad cover letter, on the other hand, can nip your chances in the bud. Here are 10 mistakes that contribute to bad cover letters.
To ensure that your cover letter is effective, avoid these mistakes:
1. Sending your resume without a cover letter.
Sure, there are some employers that don't read them or place much importance on them. But since you don't know whether the employer you're writing to reads and values cover letters or not, you must include a letter.
2. Failing to address the letter to the specific name of the recipient.
Addressing the letter to "Dear Personnel Director/HR Director," "To Whom It May Concern," "Dear Sir or Madam" (or worse, "Dear Sirs") instead of a named individual are all lazy approaches that show the employer that you were not concerned enough to find out the name of the person with the hiring power. It's not always easy to find the name of the specific hiring manager, but try to do so if at all possible. Usually, you can just call the company and ask who the hiring manager is for a given position. Tap into your personal network to learn the names of hiring managers. Let's say a company post an opening online. You know someone who works at the company. Ask your contact to find out the name of the person hiring for that position. Also use the library, phone book, and Internet to track down names of hiring managers.
The worst-case scenario is that your letter will begin "Dear Hiring Manager for [name of position]:" It's not the best approach, but if you absolutely cannot find a name, this salutation does at least provide some specificity.
3. Telling the employer what the company can do for you instead of what you can do for the company.
This mistake is particularly common among new college graduates and other inexperienced job-seekers. In most cases, employers are in business to make a profit. They want to know what you can do for their bottom line, not what they can do to fulfill your career dreams. Tell the employer how you can meet his or her needs and contribute to the company.
4. Leaving the ball in the employer's court.
Too many cover letters end with a line like this: "I look forward to hearing from you." Proactive cover letters, in which the job-seeker requests an interview and promises to follow up with a phone call, are far more effective. Don't be vague about your desire to be interviewed. Come right out and ask for an interview. Then, take your specific action a step farther and tell the recipient that you will contact him or her in a specified period of time to arrange an interview appointment. Obviously, if you say you will follow up, you have to do so. If you take this proactive approach and follow up, you will be much more likely to get interviews than if you did not follow up. This follow-up aspect is another good reason to obtain the specific name of the hiring manager. Here's a sample closing paragraph requesting specific action and describing the writer's planned follow-up.
I would like to be considered for a sales position in which someone of my background could make a contribution. I will contact you soon to arrange for an interview. Should you require any additional information, I can be contacted at the phone numbers listed above.
5. Being boring and formulaic.
Don't waste your first paragraph by writing a boring introduction. Use the first paragraph to grab the employer's attention. Tell the employer why you are writing and summarize the reasons you are qualified for the position, expanding on your qualifications in later paragraphs. Read more. Don't use such cliches as "Enclosed please find my resume" or "As you can see on my resume enclosed herewith." Employers can see that your resume is enclosed; they don't need you to tell them. Such trite phrases just waste precious space. Write a letter that will make the employer want to get to know you better.
6. Allowing typos, misspellings, or incorrect grammar/punctuation into your letter.
Your letter reflects your ability to write and communicate. Be sure your document is letter-perfect before sending it out. Proofread your letter. Put it down and proof it again a few hours later with a fresh eye. Then enlist a friend to review it for errors.
7. Rehashing your resume.
You can use your cover letter to highlight the aspects of your resume that are relevant to the position, but you're wasting precious space -- and the potential employer's time -- if you simply repeat your resume.
8. Failing to specifically tailor your letter to the job you're applying for.
If you're answering an ad or online job posting, the specifics of your cover letter should be tied as closely as possible to the actual wording of the ad you're responding to. In his book, Don't Send a Resume, Jeffrey Fox calls the best letters written in response to want ads "Boomerang letters" because they "fly the want ad words -- the copy -- back to the writer of the ad." In employing what Fox calls "a compelling sales technique," he advises letter writers to: "Flatter the person who wrote the ad with your response letter. Echo the author's words and intent. Your letter should be a mirror of the ad." Fox notes that when the recipient reads such a letter, the thought process will be: "This person seems to fit the description. This person gets it."
A particularly effective way to deploy the specifics of a want ad to your advantage is to use a two-column format in which you quote in the left-hand column specific qualifications that come right from the employer's want ad and in the right-hand column, your attributes that meet those qualifications. The two-column format is extremely effective when you possess all the qualifications for a job, but it can even sell you when you are lacking one or more qualification. The format so clearly demonstrates that you are qualified in so many areas that the employer may overlook the areas in which you lack the exact qualifications. See a sample letter in a two-column format.
9. Rambling on too long and telling the story of your life/career.
Keep you letter as brief as possible. Never, never more than one page. Keeping to four or five paragraphs of no more than three sentences each is a good guideline. Using bullet points in the letter is a good way to break up blocks of text and interest the reader. Some job-seekers tend to use their cover letters to provide a narrative of their life or career. That's not what the letter is all about; it's a marketing tool that should focus on the qualifications that will sell you to the employer. Your letter should answer the question that the employer will be asking while reading the words you've written: "Why should I hire this person?" Answer with your Unique Selling Proposition. Use simple language and uncomplicated sentence structure. Ruthlessly eliminate all unnecessary words.
10. Using wimpy language.
Avoid such phrases as "I feel" and "I believe." Your statements will be much stronger without them. It's best to either leave off the qualifier or use a stronger qualifier, such as "I am confident," I am convinced," or "I am positive." Read more.
Questions about some of the terminology used in this article? Get more information (definitions and links) on key college, career, and job-search terms by going to our Job-Seeker's Glossary of Job-Hunting Terms.
Thursday, June 12, 2008
Design Data Access Layer
Creating a Data Access Layer in .NET - Part 1 By Wayne Plourde
.NET Application Architecture: the Data Access Layer by Damon Armstrong
Using the Visual Studio 2005 DataSet Designer to build a data access layer by Brian Noyes
The whole story of Data Access in ASP.NET - Data Access Tutorials by Scott Mitchell.
.NET Application Architecture: the Data Access Layer by Damon Armstrong
Using the Visual Studio 2005 DataSet Designer to build a data access layer by Brian Noyes
The whole story of Data Access in ASP.NET - Data Access Tutorials by Scott Mitchell.
Monday, June 9, 2008
VSTS: Distributed System Designer Walkthroughs Part 1
Introductory Distributed System Designer Walkthroughs
Walkthrough: Defining Applications on Application Diagrams
Walkthrough: Defining Applications on Application Diagrams
This walkthrough guides you through defining and configuring reusable applications that you can use to design an application system in Visual Studio Team System Architecture Edition. You can later use these application definitions to design application systems. You can configure each use of an application definition within a system for deployment. Subsequent walkthroughs demonstrate how to design an application system and evaluate the deployment of that system against a logical representation of a datacenter.
In this walkthrough, you will complete the following tasks:
-
Create a distributed systems solution that contains a blank application diagram.
-
Add application definitions and a database reference to the application diagram.
-
Specify communication pathways between application definitions by connecting them through their endpoints.
Saturday, May 31, 2008
RFP - Hangzhou
可维护性 - http://web.nuist.edu.cn/courses/glxxxt/mis_files/sys_realize_4_3.htm
Glossary
Maintainability—"The ease with which a software system or component can be modified to correct faults, improve performance, or other attributes, or adapt to a changed environment" [IEEE 1990].
Manageability—How efficiently and easily a software system can be monitored and maintained to keep the system performing, secure, and running smoothly.
Supportability—How effectively a software system or component can be kept running after deployment, based on resources that include quality documentation, diagnostic information, and both knowledgeable and available technical staff.
Friday, May 30, 2008
ASP.NET MVC Framework
Global Bank: A Scenario for Visual Studio Team System 2008
Visual Studio 2005 Technical Articles
Visual Studio 2005 Technical Articles
Model-Driven Development of .NET Enterprise Applications
Visual Studio 2005 Technical Articles
The ADO.NET Entity Framework Overview
Visual Studio 2005 Technical Articles
ADO.NET Tech Preview: Entity Data Model
Microsoft ASP.NET MVC
Welcome to ASP.NET @Codeplex
ASP.NET MVC
Tuesday, April 29, 2008
Components and Tiers in Applications and Services
It has become a fairly widely accepted tenet of distributed application design that you should divide your application into components providing presentation, business, and data services. Components that perform similar types of functions can be grouped into layers, which in many cases are organized in a stacked fashion so that components "above" a certain layer use the services provided by it, and a given component will use the functionality provided by other components in its own layer and other layers "below" to perform its work.
Friday, April 25, 2008
Layers of a Windows Application
A Windows application can be divided into a number of logical layers. Your decision on which layers to implement and enforce typically depends on your quality of service (QOS) requirements.
For example, if your application is a stop-gap, possibly throwaway, system with low scalability and maintainability concerns, you might choose to implement only a couple of layers (UI and database). If, on the other hand, you are optimizing your architecture for varied physical deployments, high scalability, multiple user interfaces (Smart Client, Mobile, Reports, and so on), and a high degree of reuse, then you will opt to abstract your application into many more logical layers—you might even decide to create a framework that supports your layers. Most enterprise-level applications written today employ some version of the three primary layers:
user interface, middle tier, and database. Each of these layers might then be divided into additional layers. The following discussion presents each of these layers and some of their common divisions. Any combination of these layers may make up a Windows application.
User Interface A user interface layer provides a window to the application for users. This
layer is typically responsible for getting data from the middle tier and displaying it to the user.
It is also responsible for controlling how a user interacts with that data. This includes data
entry, validation, creating new elements, search, and so on. The UI layer is also in charge of getting the user’s modifications back to the middle tier for processing. The user interface layer is
often a layer by itself. However, it is also sometimes divided into one or more of the following
additional layers:
■ Presentation (or user experience) This layer defines only the presentation portion of the
user interface. This is the portion responsible for laying out the user interface. Think of
this code as the code inside of the FormName.Designer.cs, InitializeComponent method in
C#. Visual Basic hides this code from the developer. In both cases, Visual Studio is trying
to abstract the code for the forms engine and promote the use of the form designer tools.
■ User interface code This layer is where developers place the code to interact with the
user interface. The layer is typically embedded with the form. There is a partial class
associated with each form in both VB and C#. You put your code in this class and it gets
compiled with the form. The code that goes in this layer is to respond to events such as
loading a form or clicking a button. You might decide to abstract the code to respond to
these items into a separate user interface interaction layer. The code that would get compiled
with the form would then simply delegate calls to this layer. This will increase your
reuse if you intend to implement different forms that do the same thing or a new user
interface.
■ Business logic interaction code You might create this layer if you do not wish to tie the
code used to interact with your business layer (middle tier) to the user interface code.
This can be helpful if you intend to plan for the replacement of your user interface. For
example, you might create a Windows-based client today but have a plan to move to
Extensible Application Markup Language (XAML), an Office Client, or something even
further out.
Middle Tier The middle tier is where you house your business logic. This is often referred
to as just the business layer. However, this tier typically includes a lot more than just business
logic. It might include components for handling caching, logging, error management, and so
on. You might use the Microsoft Enterprise Library (or a similar library) in this tier. The middle
tier typically runs on an application server such as Windows Server and Internet Information
Services (IIS). However, you can create your own middle tiers (using things like Windows
services and sockets). The middle tier is sometimes divided into one or more of the following
additional layers:
■ Business layer (or business services) This layer is where you put your domain objects
and their business rules. You might be writing stateless components that work with
Enterprise Services, real object-oriented business objects that run in process, or simple
data transfer objects (DTOs) with processing services that work across remoting channels. In any case, most applications define a business layer. This isolates the business
logic so it can be reused, remain stable (as UIs get rewritten and modified), be
easier to change, and so on. As an example, a business layer object might be an Invoice
class. It might contain properties that define an invoice and methods that save and
load the object. These methods and properties will define the business rules for the
given object. These rules should be validated before the object is sent to another layer
for processing.
■ Application layer (or application services) This layer represents the plumbing to make
your application work. This plumbing typically solves QOS requirements such as “the
application must log errors or cache data for performance.” You want to keep this code
isolated from your business logic. Sometimes this code gets put into a framework. You
can also consider the Microsoft Enterprise Library as part of the application layer. Examples
of an application layer might include a Log class that contains methods to log certain
events, such as errors.
■ Database layer (or database services) This layer abstracts the retrieval and storage of
data in your database. This code is sometimes combined with the business layer. However,
this tight coupling can make the code harder to understand, more brittle to change,
and less reusable. As an example, the database layer might contain static (or shared)
methods that work to save and retrieve data from the database on behalf of the business
layer. An example might include an InvoiceData class with a method like GetInvoice that
returns a DataSet with invoice data. The database abstraction layer is often part of the
database layer. However, it typically does not reside on the database server but on the
middle-tier application server. That is why it is discussed here.
Database Layer The database layer represents how you manage the data in your application.
For most enterprise applications this means a relational database, such as Microsoft SQL
Server. The database layer is responsible for saving, retrieving, and ensuring the integrity of
your data. The database “tier” is sometimes divided into one or more of the following additional
layers:
■ Database layer See the previous “Middle Tier” section.
■ Stored procedures This layer represents the SQL or managed code used to select,
insert, update, and delete data with the database. It also includes any database-defined
functions you might create.
■ Integration services This layer represents how the database works with other data
sources for integration purposes. In SQL Server this is SQL Server Integration Services
(SSIS) or the older Data Transformation Services (DTS).
■ Database tables, log, and indexes This layer represents the actual data in the system,
the log of activity, and the indexes used by the database software.
For example, if your application is a stop-gap, possibly throwaway, system with low scalability and maintainability concerns, you might choose to implement only a couple of layers (UI and database). If, on the other hand, you are optimizing your architecture for varied physical deployments, high scalability, multiple user interfaces (Smart Client, Mobile, Reports, and so on), and a high degree of reuse, then you will opt to abstract your application into many more logical layers—you might even decide to create a framework that supports your layers. Most enterprise-level applications written today employ some version of the three primary layers:
user interface, middle tier, and database. Each of these layers might then be divided into additional layers. The following discussion presents each of these layers and some of their common divisions. Any combination of these layers may make up a Windows application.
User Interface A user interface layer provides a window to the application for users. This
layer is typically responsible for getting data from the middle tier and displaying it to the user.
It is also responsible for controlling how a user interacts with that data. This includes data
entry, validation, creating new elements, search, and so on. The UI layer is also in charge of getting the user’s modifications back to the middle tier for processing. The user interface layer is
often a layer by itself. However, it is also sometimes divided into one or more of the following
additional layers:
■ Presentation (or user experience) This layer defines only the presentation portion of the
user interface. This is the portion responsible for laying out the user interface. Think of
this code as the code inside of the FormName.Designer.cs, InitializeComponent method in
C#. Visual Basic hides this code from the developer. In both cases, Visual Studio is trying
to abstract the code for the forms engine and promote the use of the form designer tools.
■ User interface code This layer is where developers place the code to interact with the
user interface. The layer is typically embedded with the form. There is a partial class
associated with each form in both VB and C#. You put your code in this class and it gets
compiled with the form. The code that goes in this layer is to respond to events such as
loading a form or clicking a button. You might decide to abstract the code to respond to
these items into a separate user interface interaction layer. The code that would get compiled
with the form would then simply delegate calls to this layer. This will increase your
reuse if you intend to implement different forms that do the same thing or a new user
interface.
■ Business logic interaction code You might create this layer if you do not wish to tie the
code used to interact with your business layer (middle tier) to the user interface code.
This can be helpful if you intend to plan for the replacement of your user interface. For
example, you might create a Windows-based client today but have a plan to move to
Extensible Application Markup Language (XAML), an Office Client, or something even
further out.
Middle Tier The middle tier is where you house your business logic. This is often referred
to as just the business layer. However, this tier typically includes a lot more than just business
logic. It might include components for handling caching, logging, error management, and so
on. You might use the Microsoft Enterprise Library (or a similar library) in this tier. The middle
tier typically runs on an application server such as Windows Server and Internet Information
Services (IIS). However, you can create your own middle tiers (using things like Windows
services and sockets). The middle tier is sometimes divided into one or more of the following
additional layers:
■ Business layer (or business services) This layer is where you put your domain objects
and their business rules. You might be writing stateless components that work with
Enterprise Services, real object-oriented business objects that run in process, or simple
data transfer objects (DTOs) with processing services that work across remoting channels. In any case, most applications define a business layer. This isolates the business
logic so it can be reused, remain stable (as UIs get rewritten and modified), be
easier to change, and so on. As an example, a business layer object might be an Invoice
class. It might contain properties that define an invoice and methods that save and
load the object. These methods and properties will define the business rules for the
given object. These rules should be validated before the object is sent to another layer
for processing.
■ Application layer (or application services) This layer represents the plumbing to make
your application work. This plumbing typically solves QOS requirements such as “the
application must log errors or cache data for performance.” You want to keep this code
isolated from your business logic. Sometimes this code gets put into a framework. You
can also consider the Microsoft Enterprise Library as part of the application layer. Examples
of an application layer might include a Log class that contains methods to log certain
events, such as errors.
■ Database layer (or database services) This layer abstracts the retrieval and storage of
data in your database. This code is sometimes combined with the business layer. However,
this tight coupling can make the code harder to understand, more brittle to change,
and less reusable. As an example, the database layer might contain static (or shared)
methods that work to save and retrieve data from the database on behalf of the business
layer. An example might include an InvoiceData class with a method like GetInvoice that
returns a DataSet with invoice data. The database abstraction layer is often part of the
database layer. However, it typically does not reside on the database server but on the
middle-tier application server. That is why it is discussed here.
Database Layer The database layer represents how you manage the data in your application.
For most enterprise applications this means a relational database, such as Microsoft SQL
Server. The database layer is responsible for saving, retrieving, and ensuring the integrity of
your data. The database “tier” is sometimes divided into one or more of the following additional
layers:
■ Database layer See the previous “Middle Tier” section.
■ Stored procedures This layer represents the SQL or managed code used to select,
insert, update, and delete data with the database. It also includes any database-defined
functions you might create.
■ Integration services This layer represents how the database works with other data
sources for integration purposes. In SQL Server this is SQL Server Integration Services
(SSIS) or the older Data Transformation Services (DTS).
■ Database tables, log, and indexes This layer represents the actual data in the system,
the log of activity, and the indexes used by the database software.
Optimistic Concurrency (ADO.NET)
In a multiuser environment, there are two models for updating data in a database: optimistic concurrency and pessimistic concurrency. The DataSet object is designed to encourage the use of optimistic concurrency for long-running activities, such as remoting data and interacting with data.
Pessimistic concurrency involves locking rows at the data source to prevent other users from modifying data in a way that affects the current user. In a pessimistic model, when a user performs an action that causes a lock to be applied, other users cannot perform actions that would conflict with the lock until the lock owner releases it. This model is primarily used in environments where there is heavy contention for data, so that the cost of protecting data with locks is less than the cost of rolling back transactions if concurrency conflicts occur.
Therefore, in a pessimistic currency model, a user who updates a row establishes a lock. Until the user has finished the update and released the lock, no one else can change that row. For this reason, pessimistic concurrency is best implemented when lock times will be short, as in programmatic processing of records. Pessimistic concurrency is not a scalable option when users are interacting with data and causing records to be locked for relatively large periods of time.
Monday, April 7, 2008
Visual C++ Multithreading
Visual C++
Multithreading
Visual C++ allows you to have multiple concurrent threads of execution running simultaneously. With multithreading, you can spin off background tasks, manage simultaneous streams of input, manage a user interface, and much more.
In This Section
- Multithreading with C and Win32
-
Provides support for creating multithread applications with Microsoft Windows
- Multithreading with C++ and MFC
-
Describes what processes and threads are and what the MFC approach to multithreading is.
- Multithreading and Locales
-
Discusses issues that arise when using the locale functionality of both the C Runtime Library and the Standard C++ Library in a multithreaded application.
Unicode and MBCS
There is a topic about this title in MSDN.
It can be searched at http://msdn2.microsoft.com/en-us/library/default.aspx.
It can be searched at http://msdn2.microsoft.com/en-us/library/default.aspx.
Thread issue 1
- How to rework the code to make it meet multiple thread
- Make out a caller side code
NamedPtr int g_counter = 0;
void IncCounter()
{
g_counter++;
}
Prefer initialization to assignment in constructors
(From Item 12 of Effective C++)
Consider a template for generating classes that allow a name to be associated with a pointer to an object of some type T:
(In light of the aliasing that can arise during the assignment and copy construction of objects with pointer members ( see Item 11), you might wish to consider whether
Consider a template for generating classes that allow a name to be associated with a pointer to an object of some type T:
template
class NamedPtr {
public:
NamedPtr(const string& initName, T *initPtr);
...
private:
string name;
T *ptr;
};
(In light of the aliasing that can arise during the assignment and copy construction of objects with pointer members ( see Item 11), you might wish to consider whether
NamedPtrshould implement these function. Hint: it should (see Item 27).)
Subscribe to:
Posts (Atom)
