I.T.Girl!

Archived Posts from this Category

Fri 11 Apr 2008

JRE vs JDK

Posted by mimi under I.T.Girl!
No Comments 

The distinct between jdk and jre:

The JDK includes a Java compiler (javac), a Java virtual machine (java), and all of the standard Java library components — in other words, everything you need to write Java programs in a wide variety of problem domains, and more than enough firepower for the assignments we’ll be giving you. (The JRE is the Java Runtime Environment, which includes the necessary code to allow you to run Java programs, but not to write and compile them! The JRE will not be sufficient for our work in this course.)

the job of the PATH and classpath environment variable:

You can execute programs from a Command Prompt (or, as Windows 95/98 call it, an "MS-DOS prompt") by simply typing their names, such as javac or java. But there’s a catch: Windows has to know where it can find these programs. This is the job of the PATH environment variable. PATH is a list of folders, separated by semicolons, in which Windows will look for a program whenever you try to execute one.

Similarly, whenever the Java compiler or Java virtual machine need to be able to use a Java class (such as when you import a class from the Java library), the compiler or virtual machine needs to be able to know where to find it. This is the job of the CLASSPATH environment variable. CLASSPATH is a list of folders, separated by semicolons, in which the Java compiler or virtual machine will look for a Java class whenever it’s trying to find one.

So, to make the JDK work, you have to modify the PATH and CLASSPATH environment variables on your system, so that Windows will be able to find javac and java, and so that javac and java will be able to find all of the necessary Java classes.

from:http://www.ics.uci.edu/~thornton/ics23/LabManual/SettingUpJava.html

 

有关java(TM) plug-in 　（作者置顶）

       前几天整理机子，不小心把c盘program files下面的一个jre给删掉了，结果浏览器不支持applet.

于是就想去一个有关java 的网站，让它自动下载一个，网速太慢，也没下载成

然后去sun.com网站看了一下，才知道。原来需要下载一个jre(java runtime environment 1.*版)。因为在jre中包括两个组件：jws(java虚拟机)和java(tm) plug-in（即支持浏览器的一个java插件）。

       The Java Runtime Environment (JRE) provides the libraries, the Java Virtual Machine, and other components to run applets and applications written in the Java programming language. In addition, two key deployment technologies are part of the JRE: Java Plug-in, which enables appletsto run in popular browsers; and Java Web Start, which deploys standalone applications over a network.

Java Plug-in technology, included as part of the Java 2 Runtime Environment, Standard Edition (JRE), establishes a connection between popular browsers and the Java platform. This connection enables applets on Web sites to be run within a browser on the desktop.

   从浏览器这个角度来看，jdk和jre不同点在于，jdk里面虽然有java应用程序的开发，运行环境以及jws，但并没有java Plug-in 插件。所以无法为浏览器中的applet提供支持。我感觉其实java Plug-in就是浏览器和java虚拟机中间的一个适配器。

http://gwdjx.bokee.com/index.html

 

 

Mon 10 Mar 2008

IT

Posted by mimi under I.T.Girl!
No Comments 
之前，对IT 几乎完全丧失了兴趣的我，被某BLOG改变，回心转意了
这里介绍的事迹，人物，五一不让我为IT 是高科技而喝彩。
 
随便铁一个，牛仁的光荣事迹，这才叫IT – 多一份对高科技的追求，少一点急功近利，自己的付出更多人生活更美好，这些是无法用金钱来很亮的！！
 

One man writes Linux drivers for 235 USB webcams

Face to Face Michel, the pipe-smoking French Linux guru

By Fernando Cassia: Monday, 30 April 2007, 3:40 PM

 

Sun 9 Mar 2008

UNIX tips: Learn 10 Good UNIX Usage Habits

Posted by mimi under I.T.Girl!
No Comments 

Adopt 10 good habits

Ten good habits to adopt are:

  1. Make directory trees in a single swipe.
  2. Change the path; do not move the archive.
  3. Combine your commands with control operators.
  4. Quote variables with caution.
  5. Use escape sequences to manage long input.
  6. Group your commands together in a list.
  7. Use xargs outside of find.
  8. Know when grep should do the counting — and when it should step aside.
  9. Match certain fields in output, not just lines.
  10. Stop piping cats.

Make directory trees in a single swipe

Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.

For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

Change the path; do not move the archive

Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.
Back to top

Combine your commands with control operators

You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status

Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status

Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
Back to top
 

Sun 9 Mar 2008

UNIX tips: Learn 10 Good UNIX Usage Habits

Posted by mimi under I.T.Girl!
No Comments 

Adopt 10 good habits

Ten good habits to adopt are:

  1. Make directory trees in a single swipe.
  2. Change the path; do not move the archive.
  3. Combine your commands with control operators.
  4. Quote variables with caution.
  5. Use escape sequences to manage long input.
  6. Group your commands together in a list.
  7. Use xargs outside of find.
  8. Know when grep should do the counting — and when it should step aside.
  9. Match certain fields in output, not just lines.
  10. Stop piping cats.

Make directory trees in a single swipe

Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.

For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

Change the path; do not move the archive

Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.
Back to top

Combine your commands with control operators

You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status

Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status

Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
Back to top
 

Sun 9 Mar 2008

Nintendo Wii and Linux

Posted by mimi under I.T.Girl!
No Comments 

Nintendo Wii and Linux

Filed under: 3. Other Distros, Hardware, HowTos/Tutorials/Tips — E@zyVG @ 1:00 pm

Nintendo Wii has been a bit tougher to crack than hacker-friendly hardware like the PS3, which even has a Sony-approved Linux distro. But now the Wii hacking community has figured out how to run homebrew applications on Nintendo’s latest console, and that includes a rather unpolished “proof of concept” version of Linux that can run on the Wii. Few days ago this news came from the GameCube Linux Wiki:

24 Feb 2008: Long time, no see Although we haven’t posted any news in the last 2 years, we have silently continued our work keeping the kernel patches up to date. With the latest 2.6.24 release we have added support for the USB Gecko adapter as a console and terminal, so you can now logon into your gc-linux distro using minicom or HyperTerminal (TM). And last but not least, we have finally run natively Linux on the Nintendo Wii through Team Tweezers’ twilight-hack. We have released a small usbgecko-enabled Proof of Concept mini-distro to prove it. Did I say have fun? :)

Now, keep in mind, the hacking process is not simple. You need an SD card, SD card adapter for the Wii, a copy of Zelda: Twilight Princess, the ability to follow complex instructions, infinite patience, and the willingness to completely muck up your video game console if things go wrong.

Wii Technical Specification:

  • CPU (Central Processing Unit): IBM ‘Broadway’ 729MHz

  • Internal Storage: 512MB Flash Memory

  • USB 2.0: 2 Ports
  • System Memory: 256MB
  • Memory Expansion: 2 SD Memory
  • GPU (Graphics Processing Unit): ATI ‘Hollywood’
  • Optical Disc Drive: 8cm GameCube / 12cm Wii (DVD discs)
  • Supported Resolution: up to 480p
  • 12 cm Disc Capacity: 4.7GB (single) / 8.5GB (dual)
  • Wii Controller Ports: Wireless (4 maximum)
  • GameCube Controller Ports: 4 Ports
  • Internet Connectivity: WiFi 802.11b/g
  • Disc Compatibility: GameCube
  • GameCube Memory Expansion: 2 Ports

Links for running Linux on Wii:

 

Thu 27 Dec 2007

10 signs that you aren’t cut out to be a project manager

Posted by mimi under I.T.Girl!
No Comments 

10 signs that you aren’t cut out to be a project manager

You’ve all seen top 10 lists of the best traits of a project manager or the top 10 skills of a project manager. However, project management is not for everyone. Many people have some of the traits to be a good project manager, but they also have many traits that make them a bad fit for the position.Here’s my list of indications that you may not be well suited to be a project manager. Note: These are not in any ranked order.

Note: This information is also available as a PDF download.

#1: You are a poor communicator

It is said that more than 50% of a project manager’s time is spent in some aspect of communication. This includes meetings, status reporting, e-mails, phone calls, coordinating, talking to people, and completing documentation. Some studies have shown that verbal and written communication takes up 80% of the job. If you are not an effective communicator (and you don’t care to be), don’t go down this path.

#2: You don’t work well with people

If you prefer to stay in your office and focus on your own work, you probably don’t have the collaborative ability to be a good project manager. Good project managers need to spend a lot of time with clients, stakeholders, and team members.

#3: You prefer the details

Many people like to work on the project details. We need people like that. But when you are a project manager, you must rise above the details and become more of a delegator and coordinator. You must rely on others for much of the detailed work when you are a project manager.

#4: You don’t like to manage people

You don’t have much of a project if you’re the only resource. If you want to be a good project manager, you need to be able to manage people. You will not have 100% responsibility for people, but you will need to show leadership, hold them accountable, manage conflict, etc. Some project managers say they could do a much better job if they did not have to deal with people. If that’s how you feel, project management is probably not for you.

#5: You don’t like to follow processes

Yes, I know no one wants to be a slave of processes. But you need good processes to be effective as your projects get larger. If you don’t want to follow good project management processes, you are not going to get too far as a manager.

#6: You don’t like to document things

Of course, all things in moderation. I am not proposing that you have to love documenting to be a good project manager. But you can’t hate it, either. Many aspects of project management require some documentation, including status reporting, communication plans, scope changes, and Project Charters.

#7: You like to execute and not plan

When a client gives you a project, what is your first inclination? If your first thought is to get a team together to start executing the work, you probably don’t have a project management mindset. If you do not want to spend the appropriate amount of time to make sure you understand what you are doing, you are probably not cut out to be a project manager.

#8: You prefer to be an order taker

If you think your job is to take orders from the customer and execute them, you may not be a good project manager. Project managers need to provide value on a project, including pushing back when the client is asking for things that are not right. If the client raises a request that is out of scope, you also need to invoke the scope change management process. If your reaction to scope change is saying, “Yes sir, we’ll do it” instead of going through the scope change management process, project manage is going to be a struggle for you.

#9: You are not organized

People who have poor personal organization skills and techniques usually do not make good project managers. If you’re going to manage multiple people over a period of time, you need to be well organized to make sure that everyone is doing what he or she needs to do as efficiently as possible.

#10: You think project management is “overhead”

 

Thu 27 Dec 2007

10 things you should do if you get laid off October 24, 2007

Posted by mimi under I.T.Girl!
No Comments 

Version 1.0
10 things you should do if you get laid off October 24, 2007
By Suzanne Thornberry
When faced with a layoff, you have two kinds of needs. The first is to live within your means until you get a new job. The second is to get that new job. Here are some ways you can pursue both goals.
Get everything the company owes you
Tie up lose ends to collect any money the company owes you. If you’re still on the job for a couple of weeks, be sure to file any remaining expense reports. To make sure you receive any remaining vacation or PTO pay for which you are eligible, compare your time-off records with those of the HR department and iron out any discrepancies.
If you have stock options, the company may vest more of your shares in the event of a layoff. Read the fine print on exercising these options. There could be a window of time when you must exercise the options or lose them.
Get your resume updated and out the door
You’ll be sending out some unsolicited resumes as you notify your network that you are available. Brevity and relevance are most likely to catch the eye of busy people. Tailor your cover letters to the needs of hiring managers. Emphasize that you are a self-starter who’s ready to get back to work.
These TechRepublic resources can help:
Nineteen words that don’t belong in your resume
10 things you should know about creating a resume for a high-level IT position
Resume do’s and don’ts for IT consultants
3 things your resume could do without
Search company Web sites
Not all jobs are advertised on the big boards or in newspapers. One way to find these jobs is to go to the Web sites of companies where you’d like to work, then look for a Careers or Jobs link. Although it’s more likely that internal candidates will compete for these jobs, it’s still a good idea to monitor them. Find out about good companies by word of mouth, researching regional business publications for "top companies."
List your sources of income
4
3
1
2
Companies that lay off employees rarely contest unemployment claims. Unemployment insurance programs are administered by the states, and companies usually provide you with the basic rules and contact information for the program.
Think about these questions when you assess your potential income:
How far can you stretch your severance package (remaining pay, unused vacation pay, etc.)?
If applicable, how far will your spouse’s income go in covering expenses?
If your cash will be scarce and your expenses high, should you take any job — even flipping burgers — to head off more a serious shortfall? At what point would you have to make that decision?
Page 1
Copyright ©2007 CNET Networks, Inc. All rights reserved.
For more downloads and a free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html
10 things you should do if you get laid off
Prioritize expenses
Do you have the proverbial liquid savings to meet six months of expenses? If so, congratulations — you’re avoiding a major stress of losing a job. If not, well, you’re in good company.
Mortgage companies are foreclosing with glee these days, so if you have house payments, do your best to keep up with them. Water, power, and insurance are usually the largest and most critical expenses after house payments or rent. After all, getting a utility cut off and paying to be reconnected will cost you more money than paying the bill in the first place.
Try to save by cutting out services and purchases that may be nice but aren’t necessary. The usual suspects include dining out, cable TV (especially premium channels), and $5.00 coffees.
Don’t forget insurance
Ned Flanders doesn’t have insurance because it’s a form of gamb-diddly-ambling, but you shouldn’t take as much risk as the prudish Simpsons character. You might be surprised to find that your employer contributed so much to your health insurance. A $45 deduction on your biweekly paycheck might end up costing you a monthly payment of $400 or more if you elect to continue your current coverage through COBRA. With family plans, of course, the cost is even higher.
Even if you feel you can’t afford COBRA, don’t do without basic health insurance. Get quotes on individual coverage from several companies. If you don’t need expensive medications, you probably don’t need prescription coverage. Choosing a higher deductible — $1,000 or more — will save on your monthly payments and prevent a financial catastrophe if you (or members of your family) have a serious illness or injury before you find a new job.
Don’t burn bridges
If you have an exit interview, it’s tempting to vent about the company, your boss, even your former co-workers. It also may be tempting to slack off in your final days of employment rather than documenting your system or finishing other tasks. Don’t give in to your urge to get even. You may end up working with or for some of the people who were left behind.
Avoid raiding your investments
8
7
6
5
Yes, you can borrow money from your 401(k), but in practice, you’ll almost certainly end up losing money. When you pay the money back, you’ll be using after-tax dollars. So you’ll pay tax on the money twice — once as you pay back the loan and again when you make retirement withdrawals. You also may miss out on gains while the money is out of the market. And even if you borrow the money with the best intentions of paying it back, it may take a lot of self-discipline to follow through. If you fail to repay the loan in the time required (usually five years), you’ll pay an additional 10% penalty.
If you have investments in a regular (non-retirement) brokerage account, you could sell some stocks, bonds, or mutual funds. Again, think about taxes. If you make a profit on what you sell, you’ll pay capital gains taxes. The rates are usually lower than on other income, but cashing in profitable holdings can cause a hardship when it’s time to pay your taxes. On the other hand, you could choose to sell investments that have lost value and claim up to $3,000 per year as a net capital loss on Schedule D.
Page 2
Copyright ©2007 CNET Networks, Inc. All rights reserved.
For more downloads and a free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html
10 things you should do if you get laid off
Get out
Playing a first-person shooter game in your pajamas doesn’t count as dealing with stress. Exercise, working on home projects, and helping others can give you the sense of accomplishment you miss from your job. Remember that free things can be fun. Check into meetings you’ve wanted to attend. In addition to reading the help wanted section, check out your area’s free and cheap festivals.
Keep up with your debt
Anyone who has listened to a personal finance show probably knows how expensive it is to pay interest on credit card balances. For example, paying the minimum each month on a $1,000 credit card balance will take 153 months — and you’ll pay $1,115.41 in interest. Even if money is very tight, try to do without before you add to your credit card debt. Get the payments in on time to avoid high late fees and do your best to pay off the monthly balance.
Again, with the rise in foreclosures, don’t put your house in jeopardy by skipping payments If you rent and are having difficulty paying, carefully read your contract to see how late you can be before the landlord can evict you.
Like your home, your car can be repossessed, so it’s a priority if you’re making payments.
Pay attention to your feelings
Here’s a bonus tip:
Although most folks working in IT are relentlessly logical on the job, an unexpected layoff can cause even the most Vulcan employee to show anger or sadness. Even if the job loss is in no way your fault
—say, your company is moving jobs offshore to cut costs—it’s easy to get down on yourself. Unfortunately, searching for a job is much more difficult when you lack self-confidence. Not only is it difficult to speak comfortably in a job interview when you lack confidence, but it’s also difficult to deal with the nearly inevitable rejection that is part of a job search. After all, only the luckiest job seekers are offered a perfect job after a single interview.
Along with problems of self-confidence, job loss may also precipitate clinical depression. Symptoms of depression include feelings of sadness, problems with sleeping, weight loss or gain, and loss of interest in favorite activities. Men, in particular, may feel anger rather than sadness. If the feelings drag on longer than two weeks, it’s wise to discuss it with a counselor or physician. Untreated depression is likely to sabotage your job search with feelings of hopelessness, low self-esteem, and procrastination.
9
10
11
Page 3
Copyright ©2007 CNET Networks, Inc. All rights reserved.
For more downloads and a free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html
10 things you should do if you get laid off
Additional resources
• TechRepublic’s Downloads RSS Feed
• Sign up for TechRepublic’s Downloads Weekly Update newsletter
• Sign up for our IT Career NetNote
• Check out all of TechRepublic’s free newsletters
• Career blog: View from the Cubicle
• Six ways to shoot yourself in the foot during an IT job interview
• Seven warning signs that you should turn down a job offer
Version history
Version: 1.0
Published: October 24, 2007
Tell us what you think
TechRepublic downloads are designed to help you get your job done as painlessly and effectively as possible. Because we’re continually looking for ways to improve the usefulness of these tools, we need your feedback. Please take a minute to drop us a line and tell us how well this download worked for you and offer your suggestions for improvement.
Thanks!
—The TechRepublic Downloads Team
Page 4
Copyright ©2007 CNET Networks, Inc. All rights reserved.
For more downloads and a free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html

 

Wed 26 Dec 2007

10 things you can do to get better customer service

Posted by mimi under I.T.Girl!
No Comments 

10 things you can do to get better customer service

you to name the practices that annoyed you as customers. I was shocked at the number of responses, and they’re probably still coming in. We get bad customer service, unfortunately, far too often. What can we do about it? Sometimes, things are out of our control and there’s nothing we can do. Other times, however, we may be able to tilt the odds in our favor.Below are some tips that could help increase the chances of your getting better service. As IT professionals, you may benefit from these tips when you need support from a higher level group or from a vendor. Your own customers may benefit as well if you share this list with them. And if they follow these tips, your job will be easier, too.

Note: This information is also available as a PDF download.

#1: Be clear about your expectations

直到自己想要得是什么。是要解决问题，还是要知道问题真相，是要防范为让，还是解燃眉之急。

The clearer you are to the service provider about what you are expecting, the smaller the chance that you’ll be unpleasantly surprised. When explaining your expectations, try to be as specific as possible. Frederick Brooks, in his classic The Mythical Man-Month, said that project milestones should be “defined with knife edge sharpness.” Think about the Ws: What do you want, when do you want it, where…, etc. Make your expectations quantifiable if you can. That way, there’s less question about whether the service provider fulfilled the job.

#2: Separate the person from the problem

对事不对人

Did you ever feel like yelling at the front-line person who tells you that your flight is sold out, the hotel is booked solid for the night, or that he/she can’t find your trouble ticket? Go ahead and yell, but it probably won’t do any good. It will only alienate the other person, making it even more difficult for you to get what you want. Chances are, he or she had nothing to do with the problem but are only the unfortunate ones listening to you.

I know it may be hard, but try to separate that person from the problem. If you have to complain about the company, use the third person. Instead of, “You guys are all messed up” or “You messed up my reservation,” try, “It’s frustrating how messed up they are” or “They messed up my reservation.” When expressing your aggravation, say, “I’m frustrated by this problem.” Even better, try the good cop/bad cop approach. Say to the front-line person, “They really messed this up, but I’m hoping you can help me by straightening it out.” Speaking this way helps get the other person on your side.

#3: Find a decision maker

找到查fit人

Despite all the recent talk about empowerment, chances are that front-line person lacks authority to make decisions. If so, ask who can make the decisions you need to be made. When confronted by the dreaded statement, “I don’t have the authority…,” ask in response, “Who does have the authority?” When the person says, “We can’t; that’s a violation of policy,” ask in response “Who can change the policy?”

#4: Make sure they’re listening to you

让别人听你说。

If the service provider misheard you, chances are he or she will make an error and you’re going to be unhappy as a result. Therefore, if you’re explaining something, ask that service provider questions to see if he or she understands. Consider asking that person to paraphrase what you said, as a test.

#5: Ask about alternatives

山穷水尽的时候懂得寻求变通

I mentioned earlier about asking, “Who does have authority?” or “Who can change the policy?” Always think and ask about alternative solutions. In fact, simply ask that very question: “What alternatives do I have?” The other person may not even be thinking of alternatives, but if you have ideas, one or more of them might work out.

For example, the restaurant you want to visit right now has a long line. When you ask about alternatives and more details, you learn that the nonsmoking section has a two-hour wait, but the window seats in the smoking section have only a 45-minute wait, and the nonwindow seats in the smoking section are available right now. Depending on your priorities, you may wait for the nonsmoking section, sit in either of the smoking sections, go to another restaurant, or just come back to this one another day.

#6: Distinguish between means (methods) and ends (objectives)

会区分过程和结果，方法和目标

When asking for a service or product, distinguish between the result you want and the way that result is achieved. Be careful, in particular, about trying to dictate the latter. In doing so, you may unconsciously sway the service provider into a less than optimal solution.

Suppose you’re on a business trip to a remote office and are trying to print a document from a shared folder you need for a meeting. Of course, the remote print capability isn’t working. Before demanding that the IT department resolve that capability, ask yourself if you really need remote print or if you really need only the document. If it’s the latter, can you get it some other way? For example, could someone print it for you, then fax it to you? It’s not elegant, but it gets the job done. In this example, rather than say, “I need to be able to print remotely,” try saying, “I need a copy of document X for a meeting.”

#7: Develop self sufficiency

自救是硬道理

Sometimes, rather than relying on others, it’s quicker and easier if you can do something yourself. After a problem is resolved, whether it’s with your car, computer, or sink, ask the person two questions: “Could I have fixed this myself?” and “How can I keep this problem from happening again?”

#8: Know their procedures

知道vendor的办事流程

Face it: Sometimes the people who work for the service provider don’t know all they’re supposed to. In that case, if you know their procedures, you can help them give you the service you’re seeking. A few years ago, I went into a suburban branch of my bank to change foreign currency into U.S. currency. I had done such an exchange before, but at a downtown branch, and I remembered some of the details. So when I was at the suburban branch, I volunteered to them the name of a form to use and the particular department they were supposed to call. My supplying that information saved me (and them) time.

#9: Keep track of names and ticket numbers

追踪名字和TK号

Keep a record of everyone you talk to and a record of every ticket number you receive. I know that a good help desk/trouble ticket system should be able to look up a ticket by name, not just by number. However, those alternate searches might take longer. The more information you keep, the easier it will be to get your problem resolved.

#10: Recognize good service

对优秀的服务要表扬。

If a support person helps you, let that person (and his or her supervisor) know. It’s the right thing to do, and in the future, it could help you if you get that same person.

 

Wed 26 Dec 2007

10 Things lists: Best of 2007

Posted by mimi under I.T.Girl!
No Comments 

10 Things lists: Best of 2007

10 ThingsTechRepublic’s handy 10 Things tech lists break down need-to-know information in all areas of IT. Here are the most popular 10 Things lists from the last year.

1. 10 Windows XP tips and tools to simplify your work
Whether you’re trying to iron out problems with users’ systems or you just want to optimize your own PC, these tips will help you work more efficiently with Windows XP.

2. 10 tech skills you should develop during the next five years
If you want a job where you can train in a particular skill set and then never have to learn anything new, IT isn’t the field for you. But if you like to be constantly learning new things and developing new skills, you’re in the right business. Deb Shinder looks at some of the skills you should be thinking about developing to keep on top of things in the tech world in the next five years.

3. 10 tips for remotely administering workstations
Relying on various technologies to remotely administer workstations can save you a significant amount of time and money. Seasoned IT pro Rick Vanover offers these pointers to help you get the most out of remote administration tools and tactics.

4. Steer clear of these 10 illegal job interview questions
Many illegal questions are easy to avoid for just about anyone with elementary social graces, but others might surprise you. Here are 10 questions that you should be sure to strike from your interview repertoire.

5. Take charge of Windows XP with these 10+ power tips
his collection offers tips on everything from disabling XP’s Error Notification message to creating a custom Control Panel to speeding up the Search Companion.

6. 10 things you should do if you get laid off
When faced with a layoff, you have two kinds of needs. The first is to live within your means until you get a new job. The second is to get that new job. Here are some ways you can pursue both goals.

7. 10 things you can do to increase performance in Vista
If you find Vista’s performance lagging, take heart. Windows expert Deb Shinder has put together this list of steps you can take to make it run faster.

8. 10 tech certifications that actually mean something
Deb Shinder offers this look at 10 of the technical certifications that actually mean something in today’s IT job market.

9. 10 dirty little secrets you should know about working in IT
TechRepublic executive editor Jason Hiner put together this list, aimed at network administrators, IT managers, and desktop support professionals. See if these secrets sound familiar.

10. 10 annoying Word features (and how to turn them off)
If you’ve gotten more than your share of support calls from users trying to wrestle Word into submission (or pulled out your own hair on a few occasions), this list will help you quickly cut Word down to size.

 

Tue 20 Feb 2007

w03

Posted by mimi under I.T.Girl!
No Comments 
 
today
 
携帯向けサイトを見るには
 
Ladio
 

« Previous Page — Next Page »