7 Rules of Successful Freelancer

I have been a freelance programmer, web developer and system administrator for three years now. Not so much, you might say, maybe you’re right. You may also be wrong. In any case, if you’re 21, three years doesn’t seem short.

I started at the age of 18. I worked part-time in a dental clinic (from then on I was very afraid of dentists, although I was not afraid of that), and my salary was just enough to cover my internet costs (in a small town, the price of an ISP is very high and the student does not earn a lot of money), leave some extra money, which in the future can be spent on the birthdays and New Years parties of friends and parents. One day I will tell you the full story. Now I just want to say that I started with nothing, and today I can only get money from freelancers. There is no full-time office job.

1. Work regularly. Don’t rely on your mood. You have to choose the time when you work, for example you have to work every day. From 6:00 pm to midnight you can do nothing but work during this time. Yes, it’s tempting to take a break, read the forum, chat, play earthquakes, have sex, go skating, etc., then finish work the next morning. This is a totally wrong attitude. You work from home, it gives you more freedom and more flexibility, but it still works.

Of course, if you feel tired, you should take a break. Make coffee, smoke, clean the litter box, but don’t start with time-consuming and fun things – you will lose a working day.

If you don’t want to do anything now, force yourself to do it. You want money? Do you want to complete this project? So work, motherfucker! Start with simple things and do some everyday things you didn’t want to do the day before.

In addition, let your family understand that this is also very important for work and that they should try not to disturb you while you are working.

It’s hard at first, but soon you get used to working on time and become more efficient than ever before.

2. Don’t lie to your customers. “Of course I didn’t!” – you would say. lie! Terrible lies. I know three ways to lie to customers:

1. If you don’t have a job or haven’t done something, but you say you have or have done it.

Of course you don’t want to look lazy. But you’re not, right? What are you afraid of? Tell your client honestly that you lost a few days and tell them why this happened. Don’t let him mistrust you. Tell him what you plan to do to make up for lost time.

2. When you encounter problems in some part of your job, but you say that everything is fine, or that there are some difficulties, but you have overcome them.

Are you afraid of not looking good enough? Then you are not. I’ll tell you more later. Remember that no one can know everything, no one can overcome every difficulty. You understand? So why do you think your customers don’t? Don’t make him think you’re a liar. Tell him that you are not very familiar with “XXX” but that you can solve it, and explain how much time it will take you to complete it.

3. It is easy to do something, but you say it is a great achievement and you have to endure terrible difficulties to realize the function.

Are you afraid of getting less money than you can get? If you want a higher price, work harder. Every work must pay its value. And do you really want to look so bad that you can barely do simple things? Customers are not programmers, but in most cases they know what is easy and what is not.

3. Don’t think you’re smarter than your customers. If you’re that smart, where did you get the money? You’re not smart, and he’s not smart either. How do you code now, he will know how to make money. Everyone is an expert in their own field, so cooperate. Ask him why he needs the position he needs. Know what the priorities are. Tell him why you think “XXX” is bad and how you can improve it. Extreme programming experts call it a “planning game.” to collaborate. You will see the result.

4. Communication. Yes, this is obvious, but many people underestimate the importance of communication. In the beginning, people liked that you were open and communicative. Be a good person. Let them enjoy working with you. Of course you meet for work, not to chat, but a few lines in IM are okay. Just let the customer know what you’re doing now. life. You can say “come back now and make some coffee.” You are a coder. As we all know, coders drink a few liters of coffee every day. This is considered fun, use it. Be a nerd and a normal person at the same time. But don’t talk too much, you should be working. Your customer also needs to

s. They’re not just about letting customers know how much to pay you. They are also suitable for you. Without them, you can lose your sense of progress and start working slowly and inefficiently. I made that mistake recently and now I’m finishing this project. If I report regularly, I’ll finish it two months ago.

5. Do what you can and go a little further. If you’re afraid you’re not good enough, you aren’t. We are programmers. We can do anything. If we don’t know something, we read the manual, look at the examples and run it. But on the other hand, you must clearly know what you are not good at. Never do work you know you can’t do. But if you’re dealing with new things, don’t be afraid. Ask for more. gain experience. There is no other way to gain experience than through work.

6. Love your job. Clear. Never deal with things you don’t like. Be good at what you are interested in. Find your niche market, but make sure it isn’t too narrow. Discover new areas of expertise yourself, but always remain interested. Enjoy your job, programming is like sex, don’t you know? If you don’t like your job itself, maybe you should try to find something more suitable and happier for you?

7. Don’t back down. Never ask for less money/hour than previous projects. No, I’m not saying I should keep asking for more. Then you will lose all your customers. But work has to pay for its value. So don’t take jobs that are too cheap for you. Be professional.


Article source: http://EzineArticles.com/544517

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *