What is the problem will actually happen that year? I'm scared to talk about it, but don't worry, it's not a doom's day. I also don't know when it will happen to our beloved old earth. Ok, we leave that matter first. Now we will discuss the more serious problem beside the Doom's Day.

I go straight to the point. It was believed that certain software will stop working and failed to operate because of “rounding error”. This error happens when the certain software which is developed by C++ programming language, using the time_t functions. time_t is a datatype (which is defined from time.h) which is certified by C++ programming language which is stated to count from 1st January 1970.

Inside C++ Programming language, the maximum value for signed integer (32-bit) is 2,147,483,647 (hex: 0×7FFFFFFF). So, the problem is, when the year is come (int a = 0×7FFFFFFF), which is on 3:14 a.m, 19th January 2038. The second of the clock, which is at a+1, a will become 0×80000000, but because of it's over the maximum limit for integer, “DateTime” will be reset back to year 1901 (because of the value of a now become -2,147,483,648).

Most of the system that run UNIX 32-bit system will facing this problem because of almost all of the application are built based on C++ programming.

But, not to worry. The entire programs that are built with .NET application are safe from this problem. It is because of DateTime (the structure to hold time) will return data type long (maximum values for long/int64 are 9,223,372,036,854,775,807) - Unless those guy who is using the date script with COM object.

For further reading, please refer to Wikipedia or 2038 Bug Website. One thing for sure is, your computer's date will change to year 1901. By that time, almost all the software and hardware maybe, will face the “extinction” of it.

 

Yet the high road needs signposts and ramps, drains and runoffs. It needs tunnels and bridges, and a surface that won't wash away in the first rainstorm, or crack with the first frost. Technology is the hard and practical solution to problems. Technology is dirty hands, ripped fingernails, and bruised knuckles. It is a necessary, sometimes imperfect solution to specific obstacles.

Which is a long way of saying that technology is all about problem solving.

We all encounter problems. Generally, a little effort will fix things, but in this increasingly complicated world, we are sometimes faced with barriers which seem impossible to vault. Over many years of working with computers, I've learnt a few simple tricks for problem-solving. I've used these methods mostly at work, specifically in the area of Systems Analysis. However, they can be applied to any large task, at work or at home. These are the basics. You can use them to renovate a house, design a computer system, start an e-business, anything.

• Start on the problem. This may seem self-evident, but some tasks seem so complicated that we just won't tackle them. The problem does not go away when we freeze up. Almost anything is better than inaction.
• Write the problem down. This will at least help you to focus on it.
• Write it down again, in a slightly different way

Are you still in total darkness? Maybe, but you have taken a step forward. You have begun to work.

• Is the problem too big for you? Chop it up into smaller pieces. Or if you can't do that, worry away at one little bit. Problems are sometimes like a tangled ball of wool. Pull at one end, and the whole thing untangles.
• In my work experience, I've been told to design whole systems for a large company, from scratch. There was no help, no documentation. Somebody, however, wanted this, and was willing to pay me pretty well. He or she presumably had an idea of what was required when I was hired. My first task was to talk to that someone. So, go to the source.
• Don't be afraid to ask for help. Better to look confused now than to seem like an idiot a month from now, when you still haven't got a clue.

By the time you've talked things over a little, written a couple of sentences, a few points should emerge. There won't be anything tidy or final (unless you're very good), but there will be some more sub-tasks to work on.

• Document the sub-tasks. At this stage, they don't have to be in any timeline or priority order. Start working on them. If you get stuck, start working on another area. Come back to your sticking point later. You will find that completing one small task leads to another. Gradually, you will learn, and things will begin to fall into place.
• You'll probably feel more confident now. If you still can't visualize the big picture, try attacking from a different direction. Look at what the end product is supposed to be and work backwards.
• Don't forget to communicate with anyone who can help you. You should now have enough knowledge to accept good advice/information and reject bad.
• Take a break. Let your mind rest. Get some sleep, and try to take a few days off. It's amazing what your subconscious can sometimes come up with. Many times, after deliberately forgetting a problem for a few days, I find myself working on a clear, simple and elegant solution to a problem which has dogged me for weeks.
• At some stage, you can start to look for the big picture. Write down your information in some sort of logical order. Put it in boxes. Flowchart it if you know how. Use your computer to organize what you have already produced.
• Now you can start to organize your efforts, jotting down time-lines, deliverables, and expected results. I know that many times, in the work arena, you are handed this sort of information at the beginning of a task. What this means is that someone had to go through the mental effort described above. All you have to do in this case is follow orders. Unfortunately, life is not always that easy.
• No-one is going to be lucky enough to always be thrilled and stimulated by problems and adversity. If you're recovering from the "flu, or a large meal, or a late night, you may not have that consummate evangelical enthusiasm and energy that we all wish for. Recover. Start the day slowly. Tidy your desk. Read your email. But make sure that what you do is connected with your work.
• Some writers will advise you to use every scrap of time. Thirty seconds to dash off an email, a couple of minutes to read a manual. A quick phone session with a colleague. This is great if you can do it. I get frustrated, and my energy dissipates. If I finish a task 10 minutes before I"m due to leave, I can happily stretch and scratch and go glassy-eyed. On the other hand, if I'm in the middle of a task, and have some hard-earned momentum, I'm not going to shut my mind down at 5:30pm exactly. So I don't feel guilty for goofing off for five or ten minutes.
• Unless we are extremely lucky, we all have to work. One last tip - average working life can be thirty, forty, fifty years, and we're not always going to be supremely happy in what we're doing. Make it a habit to always work to solve your problems. You won't be ecstatic, but you will be a whole lot happier than the person who spends all his time bemoaning his fate and the impossible tasks he is called upon to perform.

This is a very general outline of an approach toward problem solving. I'm sure you all have tips and techniques for completing simple and difficult tasks. Indeed, problem solving seems to be a very American accomplishment. The United States is the most technologically advanced society in the world, not because Americans are cleverer, or better educated than anyone else. Rather it is because there is still a "can do" attitude in this country, passed down through the years from the hardy pioneers to a still youthful and optimistic nation.

After running disk clean up you could also run “disk defragmenter” which is located in the same position as the “disk clean up” program. This will take and re-arrange the files on your computer to help it run more smoothly.

Of course, another alternative is to manually delete all unnecessary files you have stored on your computers…that being said, “un-necessary” could be anything from a program you haven't used in forever to that picture you mean to touch up but just haven't gotten to. It's not exactly the preferred solution, after all who wants to wade through all there stuff to determine what's junk and what's not?

The Best Solution

Now these methods all work yes, but it's not exactly the best thing in the world to have to do them every so many hours just to get your computer to run at a decent speed. The most optimum solution then, is to increase your computers actual memory size. There are a number of computer stores you can go to which will sell it. Most should also offer a service to install the memory as well, one which I know does offer this service is Best Buy, but there are surely others; you will simply have to bring the processor to them so they can install the memory.

Here are solutions to some common problems people experience while they are learning to program

Problem: You get stuck.

You just got a pile of books, went through several tutorials, created several programs, and were feeling really good about your skills, when you come across a problem that you are having a hard time resolving, and you feel like giving up.

Solution: A never give up attitude is beneficial in most tasks in life, and this is especially true for programming.

Luckily there are a lot of helpful people out there and if you find the right forum to post your question you will probably receive the answer you were looking for. But if after several attempts you cannot find a solution, leave it aside for some time and come back to it. Maybe after you have created several other programs and gained new skills, you can come back to this problem and find that the solution was pretty simple after all. Remember, when the going gets tough the tough get going, so don't quit too early.

Problem: Everyone else seems so much more accomplished.

While you are struggling with some beginner questions, all the forums you visit are full of people using highly advanced technical jargon and talking about high level concepts. It is like an alien language and you think you will never be good enough. These people seem to be eating and breathing computers and programming seems to be innate to them.

Solution: Don't be scared.

Through your quest you may come across people who make it look so easy, only when you try it, it is not. Don't be afraid. They are humans just like you and me. Have a positive attitude, and keep taking small steps forward. Soon you will go from your first "Hello World" program to learning concepts of inheritance and polymorphism. After you have written several dozen programs, you will look back and wonder how you could have let such easy stuff almost dissuade you from your quest for knowledge.

Problem: I am a little cheap!

I looked into several books and compilers and the cost is adding up to several hundred dollars. I don't have that kind of money!

Solution: Programming does not have to be expensive.

You can get started with readily-available, no-cost compilers, and tutorials that will have you programming in no time. If you can, find a local library where you can gather books on the particular language you are trying to master.

Problem: I will work my own way!

You just read five different and wonderful books and have now sat down to write your first program, thinking you are an expert. Turns out you are having trouble getting your first program to compile.

Solution: Practice, practice, practice.

Bad idea! Don't think you can first read a whole book and then begin programming. You will only learn by writing programs while you are learning new concepts. The more you program, the better you will get. Keep experimenting. Find problems and seek solutions. Compare your code with others and see how you can make improvements.

Problem: I wasn't safe, now I am sorry.

You really got into programming and wrote several dozen programs, then just lost interest and forgot about it. Several months later you remember all the good times you had writing those programs and went back to search files on your computer for those programs. Only when you do, you have no idea what your programs do and what all that code means. You feel like a beginner again.

Solution: Comment!

Learn good programming practices early. Pay attention to advice on good coding practices and don't just avoid them thinking that it is not important to accomplishing the particular task you have in hand. This will help you in the future. Comment your code heavily. Even if you decide to leave your quest for a while, you may end up coming back and you will be happy to have all those comments to guide you. Taking classes at a local college can provide you with the strong foundation you need to build your skills on.

Your attitude and determination will determine your success in the programming world. With hard work will come great success.