By Ron Steiner

Online dating is something that more and more people are looking into because it is relatively risk free dating. Instead of wasting your time out on the town with a date that may or may not work out, you can now look for people online and choose to interact with them for a period of time before you actually meet! Online dating is fun, safe, and a dating resource that can get you maximum exposure with minimum effort. Young and old are having a great time with online dating because you can make it a customized experience.

Online dating is usually done through dating websites, of which there are hundreds. A couple of the most popular dating websites are Yahoo Personals and www.match.com both of which have thousands of users that can all post profiles about themselves, what they are looking for, as well as the ability to interact with one another until they find a person that is just right for them. The great thing about these websites is that everyone can find someone here, as you dont have to be looking for a long term relationship to fit in, youll find people that are looking for serious and not so serious relationships on these websites.

What is great about online dating is that even when you are not online you are promoting yourself. Once you post your profile and set up your membership, your information will be available to others that are looking for a date 24 hours a day. This means that even if you and your Mr. or Ms. Right would have never crossed paths before, youll have a great chance of checking out one anothers profiles and getting to know one another online. You could be living just miles away from the one but because you dont hang out in the same places or with the same crowds, you might not meet if it werent for online dating.

While many relationships today progress much faster than most of us are comfortable with, with online dating you can choose to advance your interactions as quickly or as slowly as you are comfortable with. If you like to take your time and want to get to know people really well, you can take your time simply exchanging emails with possible online matches as long as you want, and then you can move to the phone, and then eventually you can meet in person. Online dating is a high tech and modern way to date, but it brings back some old school elements because the relationships dont advance so quickly.

Online dating doesnt cost a lot of money or take a lot of time, which makes it appealing for many. If you want to date more but you dont have time to hit the bars and clubs to meet people, meeting people online is a great way to meet people and even create lasting relationships. With so little to lose and potentially so much to gain, it is no wonder why online dating has become so popular.

a long time ago, my teacher has told me that I should go to watch the movie”closer” while I was watching another movie of Natalie Portman. Seriously, I pretty appreciate the actress and I think that she’s kind of different from any other actrees (one of the reason is that she graduated from Havard). Anyway. so happy that I finally got a chance to watch it.

At the beginning of the movie, a song sung by Damien Rice suddenly serves as a sorrowful background of the whole story,then the two main actors comes out. Somehow, they fell in love with each other.By the way, the most part that I don’t really satisfied with is no one /nothing preshow the next step of the story. And London, before the movie, I bet that I dislike it.However, from the movie, the emotion hidden in the movie, the sadness, the romance, the abandoness, the love ,the hate, the selfishness,everything seems so serene but amazingly warm.I don’t know why but this is the real feeling for the movie. London is safe, conceal yourself in trillions of people and walking on the street lonking for the one. I mean this is a fantastic natural movie though I don’t really prefer the complex relationship between four of them and some obscene stuff (maybe only to convey some sort of mind or Alice’s characteristics). In all,I like it..really cool one!

I love Ely’s DragTile component (demo). However, I have always wished that it were easier to extend its behavior to encompass different layouts. To me, that immediately suggests a (big) refactoring. For those of you who have never done refactoring or who don’t refactor as often as you should, I thought it might be fun to walk through this step by step.

What is refactoring?

Refactoring is the process of incrementally changing the structure of your code without changing the outward functionality. It may seem silly to focus on not changing the functionality, but it is actually pretty important.

The idea is that there are two distinct phases of work: coding and refactoring. During coding, you add new functionality. During refactoring, you restructure your code while making sure that it continues to work properly. Not changing functionality during refactoring gives you a strong reference point as you make lots of iterative changes to the structure. You know your refactoring was successful if the new code still does what the old code did.

Refactoring for better reuse

Usually, you refactor code so that it can be more flexible or more reusable that it currently is. Sometimes, the change that is required is obvious. In other cases, you have to think a little before figuring out how to transform your code.

In this particular case, we want to make it easier to change layouts. Looking at the DragTile code, there is quite a bit that would be the same no matter what the layout is, and relatively little that needs to change with each new layout algorithm. Because the layout algorithm is something that is likely to change in various use cases, it is probably a good idea to isolate this functionality into a separate class.

Tip 1: Cleanly separate out the code that you think will need to change often into a separate class.

The most obvious way to divide up the DragTile layout code from the rest of the DragTile code is through inheritance:

Splitting things up in this way allows us to create a new subclass with a different layout (say, a circle) while reusing the logic that might be common to both, such as the code to talk to item renderers and do animation.

The other main way to split things up is through composition:

In this case, the container delegates to another object in order to do layout. There are a number of advantages to this approach:

1. Using delegates often makes it possible to modify behavior at runtime. After we are finished with this particular refactoring, we should be able to change the layout of one of our containers without reparenting. Woohoo!!
2. Decomposing larger classes into smaller classes can make it easier to evolve different parts of the system separately as needs change. For example, let’s say we later decide to split up FlexibleContainer into two classes: one that is lightweight for easy download, and another that is robust, to handle caching, localization, etc. Should “DragTile” inherit from the light one or the robust one? If layout is handled through delegation, you may not need to choose.
3. Composition often allows for greater decoupling. For example, let’s say you are building a photo organizer module. With the inheritance approach above, it would be difficult to create the module in such a way that the photo module knows absolutely nothing about the layout. With the composition approach, you could provide a default layout (say, Tile), while allowing the user of the module to pass in a different layout if needed.

All of this leads to the next tip, which is:

Tip 2: Think hard before using inheritance. Composition is almost always a better way to separate out the flexible part of a class from the invariant part.

So now we have a general idea of what we want to separate out, and how we want to do it. We’ll start digging into actual code in the next post.

[via kuwamoto.org]

Related Posts,
Jiehoo Bookmark,
Google Sitemap Generator,
Ultimate Tag Warrior 
WP-PostRatings

Here are the lists of top 10 seo blunders people make i have collected from other sites, and i will love to share these facts with Hb members.
Please give your valuable feedbacks.

1. Non-Relevant Linkage.
External links to your site play a large part in most of the major search engine algorithms and can be considered an endorsement of your site. But if you are being linked to from sites that have no relevance to your content, then that is now considered a negative endorsement and will not raise your ranking in the search engines. Ensure all links to your pages are from relevant sites. Be wary of link builders who acquire links from gambling, pharmaceutical or adult themed sites, especially if your site is not of the same theme. Link building is as much a science as it is an art, one we take very seriously.
2. Untargeted Keywords.
The people who use search engines are ‘normal’ people who are not likely to use words used in advertising brochures. Get to know how your customers ask for your servicesproducts and use these in your content. Often times, actual keyword research will surprise you.
3. Excessive Graphics and Flash Content.
This looks good on a web page, but to search engine crawlers it means little. Search engines are looking for content, keywords, and relevancy to the search terms. By all means have some graphics, but don’t forget the meat. This doesn’t mean Flash designed websites are bad necessarily. In fact, some big businesses do use it. For most webmasters though, Flash sites are best avoided. Unless your Flash designer does high-end websites and knows how to integrate the content and keywords within the Flash, hybrid sites combining Flash headers with HTML content will be a good option.
4. Believing all search engines are the same.
What pleases Yahoo might not necessarily please MSN or Google. Optimize your content, keywords, inbound links, and internal linking structure so that there is something for at least one of the three top search engines.
5. Multiple Search Engine Submissions.
In the very early days of search engines, this technique may have had some success, but now it can lead to slower indexing and rankings. A site with inbound links from other sites will get indexed naturally and search engine submission is not necessary. In fact, multiple submissions may be construed as an attempt to spam the search engines. The top 5 engines account for more than 90% of all activity so it is wise not to ruin your chances of ranking naturally in the search results. (comScore Media Metrix qSearch data, August 2005)
6. Incorrect Use of Title Tags.
Most people consider the title to be for their company name or product. Not so. You must include your most important search phrases within your title tag and if you do want your company name there, keep it for the end. Keep the title tag to less than 65 characters long to avoid the appearance of title tag keyword-stuffing.
7. Use of ‘Black Hat’ techniques.
Techniques such as doorway pages, hidden text, and overstuffing keywords may have had success in the past but now they will earn you penalties and could even get you banned. Avoid them altogether if you are seeking long term success. Some black hat techniques can work on a short term basis, but in the long run prove very costly.
8. Expecting Immediate Results.
SEO is an ongoing process and should be treated as such by your SEO company. Good optimization will involve building good links with quality sites and this takes time.
9. Use of Unethical SEO Consultants.
Beware the consultant that guarantees rankings with no past clients to back it up with or claims of special relationships with search engines. Many such “consultants” or “experts” will probably take your money and run. Choose a reputable SEO consultant, one who will keep in regular contact with progress reports and updates.
10. Decide to do optimization in-house.
Probably possible in the past, but now with ever increasing sophistication of search engine algorithms, this is an area best left to an expert. Furthermore, the good SEO experts usually have other income streams from their online marketing activities and a regular paycheck to work full-time simply doesn’t justify their time invested. We’ve yet to meet a good SEO who doesn’t have virtual real estate bringing in a nice chunk of cash.

How do you recognise good programmers if you’re a business guy?

It’s not as easy as it sounds. CV experience is only of limited use here, because great programmers don’t always have the “official” experience to demonstrate that they’re great. In fact, a lot of that CV experience can be misleading. Yet there are a number of subtle cues that you can get, even from the CV, to figure out whether someone’s a great programmer.

I consider myself to be a pretty good programmer. At the same time, I’ve spent a fair amount of time on the business side of the fence, filtering technical CVs for projects, interviewing people, etc. Thanks to this, I think I have a bit of experience in recognising good programmers, and I want to share it in this article, in the hope that it may help other “business guys” to recognise good programmers. And, who knows, perhaps some programmers who have the potential to be good but haven’t really exploited this can also read this and realise what they need to do to become good (although, as I’ll argue, that’s definitely not accessible to all programmers!).

In his article The 18 mistakes that kill startups, Paul Graham makes the following point:

“… what killed most of the startups in the e-commerce business back in the 90s, it was bad programmers. A lot of those companies were started by business guys who thought the way startups worked was that you had some clever idea and then hired programmers to implement it. That’s actually much harder than it sounds—almost impossibly hard in fact—because business guys can’t tell which are the good programmers. They don’t even get a shot at the best ones, because no one really good wants a job implementing the vision of a business guy.

In practice what happens is that the business guys choose people they think are good programmers (it says here on his resume that he’s a Microsoft Certified Developer) but who aren’t. Then they’re mystified to find that their startup lumbers along like a World War II bomber while their competitors scream past like jet fighters. This kind of startup is in the same position as a big company, but without the advantages.

So how do you pick good programmers if you’re not a programmer? I don’t think there’s an answer. I was about to say you’d have to find a good programmer to help you hire people. But if you can’t recognize good programmers, how would you even do that?”

I disagree with Mr Graham on this one. I think there are a number of very strong indicators of a “good programmer” (and, conversely, strong indicators of a “not-so-good programmer”) that even a business guy can recognise. I’ll summarise some key indicators and counter-indicators in a list at the end of the article.

#1 : Passion

In my corporate experience, I met a kind of technical guy I’d never met before: the career programmer. This is a person who’s doing IT because they think it’s a good career. They don’t do any programming in their spare time. They’re shocked when they find out I have a LAN and 3 computers at home. They just do it at work. They don’t learn new stuff unless sent on a training program (or motivated by the need to get a job that requires that technology). They do “programming” as a day job. They don’t really want to talk about it outside of work. When they do, they talk with a distinctive lack of enthusiasm. Basically, they lack passion.

I believe that good developers are always passionate about programming. Good developers would do some programming even if they weren’t being paid for it. Good programmers will have a tendency to talk your ear off about some technical detail of what they’re working on (but while clearly believing, sincerely, that what they’re talking about is really worth talking about). Some people might see that as maladapted social skills (which it is), but if you want to recognise a good developer, this passion for what they’re doing at the expense of social smoothness is a very strong indicator. Can you get this guy to excitedly chat up a technology that he’s using, for a whole half hour, without losing steam? Then you might be onto a winner.

#2 : Self-teaching and love of learning

Programming is the ultimate moving target. Not a year goes by without some new technology robbing an old, established standard blind and changing half the development universe. This is not to say that all good programmers pick up these changes and ride the bleeding edge. However, there’s a class of programmers that will never, ever pick up a new technology unless forced to, because they don’t like learning new stuff. These programmers will typically have learnt programming at university, and expect to get by on whatever skills they picked up there, plus whatever courses their company is willing to send them on.

If you’re thinking of hiring someone as a programmer, and he ever utters the words “I can work with that, just send me on a training course for a week and I’ll be good at it”, don’t hire that guy. A good programmer doesn’t need a training course to learn a new technology. In fact, the great programmer will be the one talking your ear off about a new technology that you haven’t even heard of, explaining to you why you must use it in your business, even if none of your staff knows how to use it. Even if it’s a technology he doesn’t know how to use yet.

#3 : Intelligence

Some business people assume that lack of social tact and lack of intelligence are the same. Actually, intelligence has several facets, and emotional/social intelligence is only one of them. Good programmers aren’t dumb. Ever. In fact, good programmers are usually amongst the smartest people you know. Many of them will actually have pretty good social skills too. The cliché of the programmer who’s incapable of having a conversation is just that - a cliché. I’ve been to a few meetings of the London Ruby User Group and I can say that with only a very few exceptions, most people there are smart, talkative, sociable, have varied interests, etc. You wouldn’t look at them chattering away in the pub and think “what a bunch of geeks!” - at least until you approach a group and realise they’re talking about the best way to design a RESTful application with a heavy UI frontend.

This doesn’t mean that they’ll all feel comfortable in every social context. But it does mean that if the context is comfortable and non-threatening enough, you’ll be able to have as great a conversation with them as you would with the most “socially enabled” people (perhaps better, since most good programmers I know like their conversation to revolve around actually useful topics, rather than just inane banter).

Don’t ever hire a dumb person thinking they’re a good developer. They’re not. If you can’t have a great conversation with them in a relaxed social context, they’re very likely not a good programmer. On the other hand, anyone who’s clearly very smart at the very least has a strong potential to be a good or great programmer.

#4 : Hidden experience

This is correlated with the “Passion” point, but it is such a strong indicator that I’d like to emphasise it with its own point.

I started programming when I was about 9, on a Commodore 64. I then migrated onto the PC, did some Pascal. When I was 14 I wrote a raycasting engine in C and Assembler, spent a large amount of time playing with cool graphic effects that you could get your computer to do by messing directly with the video card. This was what I call my “coccoon stage”. When I entered that stage, I was a mediocre programmer, and lacked the confidence to do anything really complicated. When I finished it, I had gained that confidence. I knew that I could code pretty much anything so long as I put my mind to it.

Has that ever appeared on my CV? Nope.

I strongly believe that most good programmers will have a hidden iceberg or two like this that doesn’t appear on their CV or profile. Something they think isn’t really relevant, because it’s not “proper experience”, but which actually represents an awesome accomplishment. A good question to ask a potential “good programmer” in an interview would be “can you tell me about a personal project - even or especially one that’s completely irrelevant - that you did in your spare time, and that’s not on your CV?” If they can’t (unless their CV is 20 pages long), they’re probably not a good programmer. Even a programmer with an exhaustive CV will have some significant projects that are missing from there.

#5 : Variety of technologies

This one’s pretty simple. Because of the love of learning and toying with new technologies that comes with the package of being a “good programmer”, it’s inevitable that any “good programmer” over the age of 22 will be fluent in a dozen different technologies. They can’t help it. Learning a new technology is one of the most fun things a programmer with any passion can do. So they’ll do it all the time, and accumulate a portfolio of things they’ve “played around with”. They may not be experts at all of them, but all decent programmers will be fluent in a large inventory of unrelated technologies.

That “unrelated” bit is the subtle twist. Every half-decent java programmer will be able to list a set of technologies like “Java, J2EE, Ant, XML, SQL, Hibernate, Spring, Struts, EJB, Shell scripting”, etc.. But those are all part of the same technology stack, all directly related to each other. This is possibly hard to recognise for non-programmers, but it is possible to tell whether their technology stack is varied by talking to them about it, and asking them how the different technologies they know relate to each other. Over-specialisation in a single technology stack is an indicator of a not-so-good programmer.

Finally, if some of those technologies are at the bleeding edge, that’s a good positive indicator. For instance, today (November 2007), knowledge of Merb, Flex, RSpec, HAML, UJS, and many others… Please note that these are fairly closely related technologies, so in a couple of years, someone who knows all these will be equivalent to someone familiar with the Java stack listed in the previous paragraph.

Update: As a clarification to this point, there’s in fact two indicators here: variety and bleeding edge. Those are separate indicators. A good variety of technologies across a period of time is a positive indicator, whether or not the technologies are bleeding edge. And bleeding edge technologies are a positive indicator, whether or not there’s a variety of them.

#6 : Formal qualifications

This is more a of non-indicator than a counter-indicator. The key point to outline here is that formal qualifications don’t mean squat when you’re trying to recognise a good programmer. Many good programmers will have a degree in Computer Science. Many won’t. Certifications, like MCSE or SCJP or the like, don’t mean anything either. These are designed to be accessible and desirable to all. The only thing they indicate is a certain level of knowledge of a technology. They’re safeguards that allow technology recruitment people in large corporations to know “ok, this guy knows java, he’s got a certification to prove it” without having to interview them.

If you’re hiring for a small business, or you need really smart developers for a crack team that will implement agile development in your enterprise, you should disregard most formal qualifications as noise. They really don’t tell you very much about whether the programmer is good. Similarly, disregard age. Some programmers are awesome at 18. Others are awesome at 40. You can’t base your decisions about programmer quality on age (though you might decide to hire people around a certain age to have a better fit in the company; please do note that age discrimination is illegal in most countries!).

As a final note to this, in my experience most average or poor programmers start programming at university, for their Computer Science course. Most good programmers started programming long before, and the degree was just a natural continuation of their hobby. If your potential programmer didn’t do any programming before university, and all his experience starts when she got her first job, she’s probably not a good programmer.

Disclaimer

None of the indicators above or below are sure-fire indicators. You will find great programmers who break some of those moulds. However, my view is, you’ll rarely find a great programmer that breaks all of them. Similarly, you may find poor programmers that meet (or appear to meet) some of these criteria. But I do strongly believe that the more of these criteria a programmer meets, the more likely they are to be one of those elusive “good programmers” that, as a business guy, you need to partner with.

The criteria in bullets

So, in summary, here are some indicators and counter-indicators that should help you recognise a good programmer.

Positive indicators:

• Passionate about technology
• Programs as a hobby
• Will talk your ear off on a technical subject if encouraged
• Significant (and often numerous) personal side-projects over the years
• Learns new technologies on his/her own
• Opinionated about which technologies are better for various usages
• Very uncomfortable about the idea of working with a technology he doesn’t believe to be “right”
• Clearly smart, can have great conversations on a variety of topics
• Started programming long before university/work
• Has some hidden “icebergs”, large personal projects under the CV radar
• Knowledge of a large variety of unrelated technologies (may not be on CV)

Negative indicators:

• Programming is a day job
• Don’t really want to “talk shop”, even when encouraged to
• Learns new technologies in company-sponsored courses
• Happy to work with whatever technology you’ve picked, “all technologies are good”
• Doesn’t seem too smart
• Started programming at university
• All programming experience is on the CV
• Focused mainly on one or two technology stacks (e.g. everything to do with developing a java application), with no experience outside of it

I hope these help. Let me know below if you have any comments, or anything to add to them!

Thanks for reading.

Source:http://www.inter-sections.net/2007/11/13/how-to-recognise-a-good-programmer/

By Barbara J. Crocker

My grandmother became a widow in 1970. Shortly after that, we went to the animal shelter to pick out a puppy to keep her company. Grandma decided on a little terrier that had a reddish-brown spot above each eye. Because of these spots, the dog was p
romptly named Penny.

Grandma and Penny quickly became very attached to each other, but that attachment grew much stronger about three years later when Grandma had a stroke. Grandma could no longer work, so when she came home from the hospital, she and Penny were constant companions.

After her stroke, it became a real problem for Grandma to let Penny in and out because the door was at the bottom of a flight of stairs. So a mechanism using a rope and pulley was installed from the back door to a handle at the top of the stairs. Grandma just had to pull the handle to open and close the door. If the store was out of Penny’s favorite dog food, Grandma would make one of us cook Penny browned beef with diced potatoes in it. I can remember teasing my grandmother that she loved that dog better than she loved her family.

As the years passed, Grandma and Penny became inseparable. Grandma’s old house could be filled to the brim with people, but if Grandma went to take her nap, Penny walked along beside her and stayed by her side until she awoke. As Penny aged, she could no longer jump up on the bed to lay next to Grandma, so she laid on the rug beside the bed. If Grandma went into the bathroom, Penny would hobble along beside her, wait outside the door and accompany her back to the bed or chair. Grandma never went anywhere without her faithful companion by her side.

The time came when both my grandmother and Penny’s health were failing fast. Penny couldn’t get around very well, and Grandma had been hospitalized several times. My uncle and I lived with Grandma, so Penny was never left alone, even when Grandma was in the hospital. During these times, Penny sat at the window looking out for the car bringing Grandma home and would excitedly wait at the door when Grandma came through it. Each homecoming was a grand reunion between the two.

On Christmas Day in 1985, Grandma was again taken to the hospital. Penny, as usual, sat watching out the window for the car bringing Grandma home. Two mornings later when the dog woke up, she couldn’t seem to work out the stiffness in her hips as she usually did. The same morning, she began having seizures. At age fifteen, we knew it was time. My mother and aunt took her to the veterinarian and stayed with her until the end.

Now the big dilemma was whether to tell Grandma while she was still in the hospital or wait. The decision was made to tell her while she was in the hospital because when we pulled up at the house, the first thing Grandma would look for was her beloved Penny watching out the window and then happily greeting her at the door. Grandma shed some tears but said she knew that it had to be done so Penny wouldn’t suffer.

That night while still in the hospital, Grandma had a massive heart attack. The doctors frantically worked on her but could not revive her. After fi

teen years of loving companionship, Grandma and Penny passed away within a few hours of each other. God had it all worked out – Penny was waiting at door when Grandma came Home.

Download Advanced ActionScript 3 with Design Patterns
RIAbook Rank：★★★★

Book Description:
Today’s ActionScript-based applications require increasingly sophisticated architectures and code. This book aids intermediate and advanced ActionScript developers in learning how to plan and build applications more effectively. You’ll learn how to apply design patterns as solutions to common programming scenarios. Beyond a reference, Advanced ActionScript with Design Patterns is a practical guide complete with sample mini-applications illustrating each design pattern.

Summary of Contents

Part I - Successful Projects
1. How to Design Applications
2. Programming to Interfaces
Part II - Patterns
3. MVC
4. Singleton
5. Factory (Abstract Factory and Factory Method)
6. Proxy
7. Iterator
8. Composite
9. Decorator
10. Command
11. Memento
12. State
Part III - Advanced ActionScript Topics
13. Working with Events
14. Sending and Loading Data
15. E4X (XML)
16. Regular Expressions

About the Author
Joey Lott works with ActionScript during the day and by night he’s a super-secret international man of mystery, rescuing animals and children from harms way, righting wrongs, and working for global peace, the rights of all living beings, and environmental responsibility. Joey is the author (or co-author) of a veritable arsenal of ActionScript and Flash-related titles, including the ActionScript Cookbook, Programming Flash Communication Server, and the Flash 8 Cookbook. In his free time he likes to write poetry, pursue competitive origami, and train in the art of aikido. Danny Patterson is a Consultant specializing in Flash and Web technologies. He also works with Schematic as a Senior Flash Architect. He is an Adobe Community Expert and has contributed over 40 articles to Community MX and the MX Developers Journal. He is also the co-author of the Flash 8 ActionScript: Training from the Source book by Adobe Press. He has spoken at many conferences and user groups including Flash in the Can and Flash Belt. Danny is certified in both Flash and ColdFusion and has worked on web projects for many large companies including Microsoft, IBM, Dell, Adobe and Starz. You can check out his blog at DannyPatterson.com.

rapidshare http download :Advanced ActionScript 3 with Design Patterns

Tags: DesignPattern  AS3  chm

Report Dead Link:
Please leave a comment to report dead links, so that we can update new links quickly.

The Dean & Deluca Cafe is a great place to rest your feet and have a warm cup of apple cider after exploring Tokyo Midtown.

The offerings you’ll get in this Dean & Deluca Cafe Roppongi branch extend the culinary excellence that emanates from their parent New York SoHo store, with a variety of the best coffees, teas and pastries.

Also, it’s a beautifully designed cafe!

A: Hi, Jane, how are you doing this morning?

B: I’m all right, thanks. Just a little tired.

A: You worked overtime last night?

B: Yeah, I got home at about 2.

A: Hi, Tim. How are you? I haven’t seen you for a long time.

B: I’m fine. I’ve been out of town. I just got back.

A: Where did you go?

B: I went to New York for a meeting.

A: Hi there! My name is Terry. You’re new around here, huh?

B: Yes. My name is Mark. I just started a couple of weeks ago.

A: Well, if there’s anything I can do for you, let me know.

B: Thanks. I really appreciate that!

A: Excuse me, Christina?

B: Yes, Mark?

A: Could you tell me where the copier is please?

B: Sure. You just walk down this hallway. The copy room is the second room on the right.

A: Excuse me.

B: Yes, can I help you?

A: Yes, please. I’m looking for Mr. Emory’s office. Do you know where it is?

B: I’m sorry. I don’t know. But the guard over there should know.

A: Mr. Emory’s office. Can I help you?

B: Yes. My name is Walter Parker. I need to book some time with Mr. Emory this morning.

A: I’m sorry, but Mr. Emory is pretty booked up today.

B: I realize that. But we’ve got to work fast on the new plan and our deadline is tomorrow.

A: Let me see …..Umm maybe I can put you down in lunch break. Could you make that?

B: No problem. I’ll come again at 12. Thanks a lot.

A: Would you please take a seat over there, Sir? I’ll let Mr. Emory know that you are here.

B: Thanks. I can wait here.

A: Well, it may take some time. Mr. Emory is in a meeting at the moment. It would probably be more comfortable over there.

B: I see. All right, then. Thanks.

A: Terry? I need the file you took yesterday.

B: I’m sorry, Jane. I left it at home. I’ll bring it back tomorrow.

A: Terry, I told you yesterday that I’d be using the file this afternoon.

B: I know, Jane. I just walked out and it completely slipped my mind. I’ll go home and get it at noon, all right?

A: Hey Terry, do you have the number for that restaurant on the street corner?

B: Yeah, hold on a sec. Here it is. 6407-1553.

A: Great. Thanks.

B: Are you getting take-out?

A: Yeah. Do you want something?

B: Umm…Could you pick me up a chicken salad sandwich and a large diet coke?

A: No problem. But do you have any cash on you? I don’t think I have enough.

A: Christina, can you give me a hand?

B: Sure. What’s wrong, Mark?

A: Well, I think I’ve got the copier running. I pressed the button but nothing came out.

B: Let me have a look. Oh, the machine is running out of paper.

A: Mr. Emory, I’d like to take this afternoon off if it’s all right with you.

B: But Sam, you’ve called in sick 5 times in the last three weeks.

A: I know, Mr. Emory. I’m sorry. But I really need to see the doctor this afternoon. I feel dizzy and I can’t concentrate on my work.

B: All right, then. But don’t forget to bring a doctor’s note in tomorrow.

A: Hello, Mr. Black? This is Christina in Mr. Emory’s office. Mr. Emory would like to set up an appointment with you to talk about buying a new fax machine.

B: Sure. I’d be glad to. What time?

A: He’d like to see you as soon as possible. How about tomorrow at 2pm?

B: Yes. That’ll be great. Tell him I will see him then.

A: Tim, I need to work out a time to get together with your people to discuss the new project.

B: Does everybody need to be there? Jason is on vacation this week.

A: It would be best if everybody could be there. How about sometime next week?

B: Let me take a look at the schedule first. I’ll get back to you this afternoon.

A: Hey Tim. I heard you got a promotion!

B: Yes. I’m going to be running the Walker Avenue Branch.

A: Congratulations! We should have a drink on it. I know a good place in the city. Let’s go together after work.

B: That’s a good idea. It’s my treat this time.