29 July 2009

10 ways IT departments waste money

IT is often a popular target for corporate cost-cutting. So the more you can identify and control unnecessary spending, the better youĂ‚’ll be able to fend off the budget axe.

Back in the golden days of IT, when companies had plenty of money to throw around, it didn't matter so much if there was a little wastage here and there.

Today, however, budgets are tight and there aren't many dollars to spare. That means IT departments need to take a good, hard look at where the money is going and where cuts can be made--before someone higher up does it for you.

In this article, we look at 10 ways you might be letting precious dollars slip right through your fingers. Some of these may seem to be just common sense, but there are organizations out there right now that are wasting money in all these ways.

1: Wasting energy
Despite some reduction in power costs over the last year, rates appear to be headed back up. The electric bill is still a large expense for most companies--and the IT department is a big user of energy.

You can save more money than you might suspect by adopting some energy-saving policies. Sure, most of the servers need to be accessible all the time. But IT personnel are often careless about leaving workstations running when they aren't doing anything and won't be accessed remotely or substituting the use of a screensaver for turning off the monitor (you should do both).

With the power settings available in modern operating systems, there's really no excuse for it, but some IT pros turn off power-saving features in favor of higher performance.

How about the practice of leaving lights on in offices and server rooms when no one is there? Most people don't think about the cost, but it can add up. Using more energy-efficient lighting and buying Energy Star rated equipment can also save big bucks over the long run.

2: Spending too much on mobile technology
Mobile phones and devices are "fun toys" for IT pros, but company-provided equipment and plans may be costing more than necessary.

A recent survey showed that only one out of four employees uses 75 percent or more of the voice minutes that their companies are paying for and almost half (48 percent) have services on the plan that they never use at all. As this article explains, many companies don't have viable policies regarding mobile device use.

3: Not allowing employees to work from home
Company managers sometimes fail to recognize the significant cost benefits--to both employer and employee--of allowing employees to telecommute all or part of the time.

One reason they oppose such an arrangement is that they won't have as much control over workers who aren't on site. IT departments sometimes support this position for fear that remote workers will present a security threat. However, with modern technologies such as NAP/NAC and DirectAccess, you can ensure that remote systems connecting to the company LAN are properly configured and protected and that the connections are secure.

Allowing more employees to work from home enables the company to save money on office/parking space and heating/air conditioning. Employees save money on clothes, lunches, and transportation. They also often enjoy work more, so they end up putting in extra hours that raise productivity and benefit the company. Many IT-related jobs, such as those of in-house developers and Web designers, can be done from home.

4: Using consultants when the job could be done by staff
It's a common scenario: Employees have been telling management for months or years that changes need to be made, but they've been ignored. Then the company hires a consultant, who charges tens or even hundreds of thousands of dollars to do a "study" and arrives at the same conclusion, providing the same advice staff members were trying to give away free.

If you have people on staff who have expertise in a particular area and have the time to do a job, it's generally more cost effective to allow them to do it than to bring in an outsider who has to spend many (billable) hours getting up to speed on how your company operates and what its specific needs are.

If you do find that you need to bring in a consultant, check credentials and references carefully. There are many good, hard-working IT consultants. The field is also a great target for rip-off artists who talk over your head about specialized technologies and try to push the latest and greatest on you--whether you need it or not--or attempt to sell you on specific products that you may not really need.

5: Hiring full-time employees when contractors would be more cost effective
The flip side of the previous item involves being afraid to use consultants or contractors when it's appropriate. Hiring full-time employees to handle a workload that's likely to be temporary leaves you with idle workers who end up costing you money because there's not enough for them to do to warrant their salaries--or forcing you to go through the pains (to those employees as well as to the company) of layoffs.

In these situations, when you don't have the current manpower or expertise on staff to get the job done, it's often more cost effective to hire independent contractors. Not only can you limit the duration of the commitment, but you don't generally have to pay for fringe benefits, such as insurance and vacation/sick time. You also don't have the administrative overhead of withholding taxes and filing the paperwork that's associated with regular employees.

6: Making unnecessary upgrades
There are good reasons to upgrade your software and/or hardware. When new operating systems or applications provide functionality that your users need or that can help them get their jobs done more easily or more rapidly, it makes sense to upgrade. When existing hardware won't run those programs you need, it may be necessary to buy new computers.

However, some companies follow a set upgrade schedule whereby they replace old systems every X number of years. Or they migrate to the new operating system or major application version X number of months after it's released, or as soon as service pack 1 comes out, or in response to some other arbitrary trigger--much like the old timer who "takes a bath every Saturday night, whether he needs one or not".

It makes more sense to carefully evaluate how the systems and software are being used and whether there's a real need to upgrade. You can save the cost of new licenses and administrative overhead costs--and often, make users happier and avoid deployment headaches--by sticking with what you have now if it's still working fine for your company's purposes.

This applies to servers, too. It's nice to have the latest and greatest running on the most powerful machines, but will it make a real difference in terms of productivity, security, and other important factors or do you just want it so you'll have a new toy to play with?

7: Failing to upgrade old, inefficient equipment
On the other hand, some companies are going overboard when it comes to squeezing every last drop of use out of their current systems.

If the computers are getting so old that they regularly break down and require repairs, if your servers go down so often that users of the network can't get their work done or customers can't access your site, if you're putting sensitive data at risk because you're depending on old software that's full of vulnerabilities, if the hardware costs considerably more to operate than more modern machines because it's so energy inefficient, it may be time to think about investing some capital to lower operating costs and save money over the long run.

Remember that neither software nor hardware upgrades have to be an "all or nothing" proposition. Some departments or individuals may need to be upgraded while others can get along for a while longer with what they have. And when you're considering a major upgrade, such as a new OS, it's often smart to roll it out with a pilot group first so you can work out any unanticipated problems before deploying across the entire organization.

8: Overspending on hardware
While buying new hardware can save you money, too much of a good thing can waste it. Some companies are still not utilizing virtualization to the extent that they could to reduce both capital and operating expenditures.

Instead of buying multiple mid-priced servers to run Web services, mail services, collaboration and communications services etc., you may be able to save substantially by purchasing one or two more powerful machines and consolidating servers with virtualization technologies. Not only is the total capital outlay often less, but you reduce the cost of extended warranties and maintenance contracts since they apply to fewer machines, and operating costs are often lower because the total power usage is less.

Another way some companies waste money is by purchasing equipment for a project that requires very intensive computing resources--but only for a limited time. When the project is over, you're stuck with the expensive equipment. An alternative is to use services such as Amazon's Elastic Compute Cloud (EC2) and similar cloud-based services that allow you to purchase capacity that can quickly scale up or down to fit your needs. Then, at any given time, you're paying only for the resources you actually use.

9: Not using the training budget effectively
Technology is always changing and it's important for IT personnel to stay current, but some departments waste money on training that could be done as effectively for much less.

Do employees really need to travel to a distant site for training or can it be done on-site less expensively? Perhaps instead of sending several employees, one can attend and then come back and share what he/she learned with the others. Or the same training may be available on DVD or through live online instruction at a fraction of the cost.

Is the department paying for certifications that may not be necessary? Certification provides assurance of a certain level of knowledge and in some cases, having certified employees on staff enhances the company's reputation or allows it to participate in vendor partner programs. But some IT professionals collect multiple certifications--at company expense--that may not benefit the company at all (although they may benefit the employee in looking for a new job).

Ongoing training is important, and having well-trained personnel can save a company money in the long run. But when budgets are tight, it's also important to get the most for every training dollar and cut out the waste.

10: Wasting money on travel expenses
Training isn't the only reason employees travel on the company dime. Members of the IT department may be called upon to attend meetings at company headquarters or give presentations at another branch office or go to a different location to help set up equipment or troubleshoot software problems. In a tight economy, it's smart to examine whether this things can be done via online meetings or through remote control software.

Sometimes, though, travel can't be avoided. In those cases, you can still save money by staying in more reasonably priced hotels, putting a cap on meals reimbursements or instituting a per diem, and even taking shuttles instead of cabs for small savings that add up.

When traveling only a few hundred miles, consider driving instead of flying. Given the hassle factor at airports today, it may not take much longer and can be a more pleasant experience, and the savings really accrue when two or more people travel together by car instead of plane.

27 July 2009

Add Information and Image in My Computer

hen you open properties of My computer, what all information do you see? Most common things are OS details under System, Registered to "Your name", and Processor and Ram details under Computer.


What if you want to add more information? Yes, more information can be added to the My Computer properties. How?


Well I must tell you it is very very easy to do this, and believe me this is as simple as Cut Copy Paste


Here is what you need to do
Open Notepad, and type in the following.
[General]
Manufacturer= "You can type any information here"
Model="You can type any information here"
[Support Information]
Line1="You can type any information here"
Line2="You can type any information here"
P.S. - All the characters are case sensitive
You can add upto 10 lines in the Support Information section
Name this file as "OEMINFO.INI", and place it in System32 Folder
Just refresh and open My Computer Properties, and you will see additional information
To add an Image, follow these steps
Create any image of 125 X 125 pixel
Save it by name of "OEMLOGO.BMP"
Place this file in System32 folder
Refresh and you are done
If in case you want to undo these changes, just delete these files from system32 folder, and you will be back to normal.

23 July 2009

Mohandas Karamchand Gandhi - Special

Mohandas Karamchand Gandhi, Mahatma Gandhi, the apostle of peace and the Father of the Nation was born on 2nd October 1869 at Porbandar in Gujarat.



Gandhi Jayanti is celebrated on the very day every year as the birthday of Mahatma Gandhi, Father of India.


In his autobiography My experiments with Truth Gandhi recalls that his childhood and teen age years were characterized by education in a local school, marriage to Kasturba at the age of 13 and an intrinsic love for’ truth’ and ‘duty’.



Gandhi, as he was popularly called, proved that non-violence is the most effective instrument of social change. His teachings are promoted even today to avoid violence and find peaceful solutions to conflicts.


Through his sheer dedication and self-belief, Gandhi freed India from the British Raj (British Rule). He proved to the world that freedom can be achieved through the path of non-violence.


For Gandhi ‘Non-violence’ and truth were two inalienable virtues. He summed up the entire philosophy of his life as: "The only virtue I want to claim is truth and non-violence. I lay no claim to super human powers: I want none".


The United Nations General Assembly announced on 15th June, 2007 that October 2nd will be celebrated as the International Day of Non-Violence.


The soul of India : Mahatma Gandhi


Some of the famous quotes by Mahatma Gandhi have been listed below:


· Live as if you were to die tomorrow. Learn as if you were to live forever.

· Fear is not a disease of the body; fear kills the soul.

· The principle of majority does not work when differences on fundamentals are involved.

· Freedom is not worth having if it does not include the freedom to make mistakes.

· It is better to be violent, if there is violence in our hearts, than to put on the cloak of nonviolence to cover impotence.

· It is unwise to be too sure of one's own wisdom. It is healthy to be reminded that the strongest might weaken and the wisest might err.

· You must not lose faith in humanity. Humanity is an ocean; if a few drops of the ocean are dirty, the ocean does not become dirty.

· Honest differences are often a healthy sign of progress.

· Whatever you do may be insignificant, but it is very important that you do it.

How to develop Leadership Skill

1. Know your people. Take time to offer a friendly greeting at the beginning of each workday. You will be amazed at how your greeting in the morning can set the tone of an employee’s attitude all day. A “grumpy” boss will most likely have “grumpy” employees. Let employees know that you care about them as individuals. So, talk to them occasionally about their outside interests.


2. Give plenty of feedback. Let people know you really do notice the work they do. Make specific comments about the work they do. For example, instead of just telling a person they did a good job, be specific about what was really good about their work. You might say, “I really liked the amount of detail you put into that report.” If it is details you want, give feedback on the amount of details they give. Also, expect inexperienced workers to make some mistakes. So, when mistakes are made with new tasks, assume first that your instructions were not clear, and take the time to clarify the expectations.



3. Never ignore non-performance. When you recognize someone is not meeting job expectations, check to see what’s happening. Identify and discuss the problem performance with the employee and let the worker know that you expect performance.


4. Praise workers who do what’s expected of them. Remember, a paycheck is not sufficient recognition for satisfactory job performance. Just praising the exceptional performance will mean few employees will be praised. It’s easy to praise top performers, but don’t forget the rest. Take the time to show those who regularly perform their work adequately that you appreciate their efforts. Remember, good performance gone unrecognized will diminish. If you don’t show you care about what they do, why should they care? If you don’t show you appreciate them, why should they appreciate you? I could go on, but you get the idea.


5. Remember the work atmosphere. The most important part of the work climate is a healthy sense of self-esteem. When employees feel good about themselves and they feel good about what they do it is much easier for them to be cooperative and display a willingness to go the extra mile for you. When you think about it, the attitude of the boss is the most important attitude of all. You set the tone.

Increase your hard disk speed....


To speed up your hard disk speed we need to configure a special buffer in the computer's memory in order to enable it to better deal with interrupts made from the disk.


This tip is only recommended if you have 256MB RAM or higher.

Follow these steps:


1) Run SYSEDIT.EXE from the Run command.


2) Expand the system.ini file window.


3) Scroll down almost to the end of the file till you find a line called [386enh].


4) Press Enter to make one blank line, and in that line type
Irq14=4096


Note: This line IS CASE SENSITIVE!!!


Click on the File menu, then choose Save.


Close SYSEDIT and reboot your computer.


Done. Speed improvement will be noticed after the computer reboots.

22 July 2009

Folder option missing? Find Solution here

Many of us sometimes find the folder options missing in windows explorer.

Here's the solution—>


Open Run and then type "gpedit.msc" .
Now goto User Configuration > Administrative templates > Windows Component > Windows Explorer.


Click on Windows Explorer you will find the 3rd option on the right side of screen "Removes the Folder Option menu item from the Tools menu"
Just check it, if it is not configured then change it to enable by double clicking on it and after applying again set it to not configured.

I hopes that you will find the option after restarting windows.

09 July 2009

Keep project scope small for success

Negativity can kill a project, but the opposite is also true: You can stuff a project with so many features that it's crushed by its own weight.

A common objection to a project plan is that it doesn't do enough--it doesn't have all the features that users will inevitably request, or it doesn't take certain situations into account.

Or as TechRepublic member biancaluna recently put it, it "does not solve world hunger nor does it wash my car or bake a pecan pie". But in my experience, those omissions argue for it rather than against it. Certainly, you don't want to preclude features that will be needed in the future, but if you try to anticipate all of those features in the initial design, you'll never complete that phase.

Rather than designing in everything from the top, start small but make your design modular and extensible.

In my response to biancaluna's comment I said: "In the future, whenever someone tries to shoot down an idea because it doesn't do enough, I'll say 'DNSWH'." Does Not Solve World Hunger. It's also a good response when someone is trying to pile on the features.

A company I used to work for had a long history of cowboy coding--that is, "we need feature X, so just go code it up." Naturally, after several years, this resulted in an unmaintainable mess; they got design religion and began requiring a lengthy design process before any code could be written.

To insure that nothing important was ever left out, they held daily design meetings involving a dozen or more people--each of whom was trying to impress everyone else with how many nits they could pick. Only a handful of projects ever emerged from this phase after months of bickering, and those projects went on to become bloated applications with so much feature noise that they were almost unusable.

What's even worse is that the projects didn't solve the original problem, which was to keep existing customers happy and to draw new customers in; instead, they focused on solving world hunger.

A number of times in my consulting career I've had clients want to ditch their product and start over from scratch. Perhaps the UI looks "old" and needs to be redone; or the code is so mangled that they think it is beyond hope; or they've hired someone who thinks that a certain language or framework is the philosopher's stone that will magically turn their applications to gold. These projects almost never succeed.

Why? Because they're too big. Yes, you can certainly recreate that application in Ruby on Rails in a fraction of the time spent on it to date, but do you realize how much time has actually gone into it? Chances are it's in the hundreds of thousands or even millions of hours. Even if you can develop ten times faster than the original, do you have several years to do this?

Sometimes it's easy to mistake how big these projects really are because their requirements aren't fully known. The projects have evolved over many years, and features are sometimes added without being documented; yet users rely on that behavior, and if you take it away, you're going to end up pasting it back in. Do that enough times, and your new, pristine version will end up being the same mix of baling wire and bubblegum that comprised the original.

It's almost always a better idea to make incremental improvements instead. That requires long-term vision of where you want to get someday, without trying to do it all at once. Lay out a general plan for the future, and then create a specific project to do just the first step. That helps to minimize the risk of failure and keep the project scope manageable.

It's easier to agree on the design for something that does only one thing well--and it's easier to tell when it doesn't. More importantly, you can get user feedback before you proceed to the next stage.

Trying to do too many things at once multiplies your chances of project failure. One company I worked for back in the 80s provided turnkey solutions--that is, they wheeled the system in, and all the user had to do was turn the key. The vendor provided the hardware, the operating system, and the software.

One bright day, the vendor decided to upgrade their database architecture. To do so, they needed a new version of the programming language and its runtime environment. That version was only supported on certain operating systems, so an OS upgrade would also be required for most users. The applications (mostly accounting) still needed regulatory changes, and they felt that they couldn't go a whole year without adding some enhancements as well.

To keep things "simple", they decided to do all this at once--to more than 1,300 supported users. It would be great--what could possibly go wrong?

The OS upgrades ran into hardware support issues. The language runtime was still pretty green on some platforms and introduced a massive number of failures--none of which showed up in QA, of course. But certainly a redesign of the database architecture should have been a simple task, right? No. Application bugs abounded due to touching just about every module.

The support lines were overwhelmed. Extra people manned the phones, including all the programmers. As a result, it took a long time to fix the issues. Meanwhile, we'd go home at night only after we attempted to call back every customer who had logged a call, but by then it was so late that they had given up on us--this added up to more than 700 users every night for months.

Did we keep all of our customers? No. Did we add any new ones? No, we tried to solve world hunger instead.

In retrospect, we should have taken on only one thing at a time. Upgrade the language runtime on one platform only where we already had users who wouldn't need an OS upgrade. Don't touch the database or the code until that's stable. Continue one platform at a time until the new runtime version is gold. Then look at changing the database--but only a portion of an application at a time.

Taking this sort of measured approach, we would have been able to slip in regulatory changes and even some small enhancements along the way, without breaking the customer's back.

For us consultants, limited scope is one of the key benefits of short-term contracts. In, done, out. But we can apply the same principle to long-term engagements as well by dividing each project into bite-sized chunks.

When a project looms massively before you, ask how you can cut it up so you won't choke on it. Identify the optional features and move those to the end, where they can be lopped off if you run short. Don't try to solve world hunger--feed one user need at a time.

01 July 2009

Writing text file in UTF-8 encoding


fopen(sample.txt", "wb");
// adding header
$text="\xEF\xBB\xBF".$text
;
fputs($f, $text
);
fclose($f
);
?>