Contracting/Freelancing
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
It depends on what you've got on your CV. If you're not long into your career you might be better off bidding for work to try and build up your profile. If, on the other hand you've got some experience and maybe a certification or two, recruitment parasites consultants should be fighting each other to place you somewhere. Try posting a comprehensive profile on something like linkedin and see what happens. Contract recruiters trawl there all the time.
-
Well...I have heard there's good money to be made down at the docks... doing..."favours" for sailors...
Every man can tell how many goats or sheep he possesses, but not how many friends.
Cleaning their kit, doing a bit of needlework, etc. He'll have to apply to join the Guild of Seamstresses first though.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
loctrice wrote:
I don't know which term to use [contracting/freelancing].
They are basically the same thing; as a freelancer you would work for yourself by fulfilling a contract between yourself and your customer.
loctrice wrote:
I've no idea where to start.
Read Pete O'Hanlon's Articles[^] on the subject. Find out which agencies in your area deal with contract work. Try some local businesses to see if they have any requirements for freelance work.
loctrice wrote:
I've tried a website or two where you bid on jobs.
It never will; they expect the moon on a stick for a few dollars.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
-
loctrice wrote:
I don't know which term to use [contracting/freelancing].
They are basically the same thing; as a freelancer you would work for yourself by fulfilling a contract between yourself and your customer.
loctrice wrote:
I've no idea where to start.
Read Pete O'Hanlon's Articles[^] on the subject. Find out which agencies in your area deal with contract work. Try some local businesses to see if they have any requirements for freelance work.
loctrice wrote:
I've tried a website or two where you bid on jobs.
It never will; they expect the moon on a stick for a few dollars.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
If you want to do contracting, you just go to normal job sites (like careerbuilder or dice.com) and look for contract jobs in your area. They are usually offered by recruiters, and if you apply for one, the recruiter will usually tell you about other jobs they have available, too. Contracting has its plusses and minuses, but if you're not very good at getting along with people, you won't do well with contract or full-time work. You might want to first consider just getting another regular job if your current one is not working out. The bidding-on-jobs websites are worthless for people who live in first-world countries, both for developers and people posting work; they inevitably degrade into places where the most incompetent developers and the most clueless job offerers can jointly make each other's lives miserable. If you want real work, go to a real job website.
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
I've written a few articles on contracting[^] which is a little different from freelancing. Contracting: you work for a single company for a set period and, very often, get paid through an agency. Freelancing: you pitch for as much work as you can do with a variety of companies and work on your own, at home. You may find it easier to contract first whilst building up contacts and knowledge.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
I started in vworker making one job for $5 and now i have a paid for time job of $22 for hour, the thing is if you like to work as a freelancer you will have to spend some time building up a reputation until you can bet for important works.
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
If you go it alone, do not forget to charge for overhead. Stating out on your own is where the term networking comes in. My suggestion would be try consulting through an agency for a while, noting how the agency handles things. But that is just me. Good luck.
-
Richard MacCutchan wrote:
It never will; they expect the moon on a stick for a few dollars.
I've noticed that. I can't believe what they put on there for a budget less than $250. Even worse, they get tons of bids.
If it moves, compile it
loctrice wrote:
Even worse, they get tons of bids.
From people who immediately post in Q&A.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
-
loctrice wrote:
I don't know which term to use [contracting/freelancing].
They are basically the same thing; as a freelancer you would work for yourself by fulfilling a contract between yourself and your customer.
loctrice wrote:
I've no idea where to start.
Read Pete O'Hanlon's Articles[^] on the subject. Find out which agencies in your area deal with contract work. Try some local businesses to see if they have any requirements for freelance work.
loctrice wrote:
I've tried a website or two where you bid on jobs.
It never will; they expect the moon on a stick for a few dollars.
Binding 100,000 items to a list box can be just silly regardless of what pattern you are following. Jeremy Likness
Richard MacCutchan wrote:
It never will; they expect the moon on a stick for a few dollars.
If it makes things any easier, Vilmos has a stick[^].
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
Well...I have heard there's good money to be made down at the docks... doing..."favours" for sailors...
Every man can tell how many goats or sheep he possesses, but not how many friends.
And squrrie the squirrel went neep neep neep and they all went to bed.
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
-Or-
A Dead ringer for Kate Winslett[^] -
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
-
I've made my decision I think. I think I've worn out my welcome here at the office and I want to get into working for myself. I don't know which term to use [contracting/freelancing]. anyone point me in the right direction to find this type of work? I've no idea where to start. -edit- I've tried a website or two where you bid on jobs. Seems like nothing comes from it. -end edit-
If it moves, compile it
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
All excellent advice. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
Very good advice.
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi
Right on track!!!!
-
I'v been doing both contracting on the side and freelancing (for a year) for the past 17 years. Some observations: 1) Clients don't know what the want. They do know, however, that what you gave them isn't it. Lesson: Be VERY explicit in your documentation. Assume nothing. Document everything. 2) ALWAYS use a contract, regardless of the project scope or size, including work for 'friends'. Don't work without a signed contract. 3) Work out payment details in advance. Again, be very explicit in your contract. 4) For large projects, work in phases. Deliver phase 1, get paid for it, start on phase two, ect. 5) Manage change request carefully. Changes can muddy the waters and cause scope bloat. Be explicit on the time and cost for even the smallest change. 6) Deliver on time. Being late can damage your credibility. 7) If you fail to get paid, stop working. Don't assume the "check's in the mail". 8) Get feedback often. Get the customer involved in testing early on and throughout the project. You want it to go smooth and don't want stoppages becuase something's not right. 9) Create a project schedule, including deliverables - both from you and the client. State when they will send you documents, when they'll start testing, end testing, when you'll start, and when you'll end. 10) If it's ambiguous, it's unenforcable. If either you or the client are unsure on something, get clarification before you proceed. 11) Research your potential client. If they hava a bad rep, avoid them. Yout don't want to get ripped off or into legal hassles. 12) State in the contract who ownes the code. Research this. Here in CA, when a contractor writes code for a client its called a Work For Hire[^], the contractor ownes the code. I write in a release clause granting the client either full, sole ownership, or the right to use code forever. From the article "anyone you hire independently to do your SEO work (which is considered copyrighted material) not only gets to keep full copyrights to their creations, but cannot legally transfer their rights to you unless certain conditions are met." 13) Disclaimer. Write one in. As soon as they finish testing, they should hold you harmless. 14. Use common sense. If it sounds too good to be true - it is. Just my two cent.
Everythi