As developers do you ever seek out contract work in addition to your full-time job? I am considering pursuing some additional part-time opportunities and I'm curious how common it is among full-time software engineers.
|
I did that from the very beginning of my career, and I would do it again, despite all the problems I got because of it (legal & health). In addition of legal aspects
I suggest you to work on one project at a time (or one customer at a time), and no more than 2h a day in addition of your 8h work day. For a maximum total of 50h per week. Now positive things:
|
|||
|
|
|
I freelance from time to time, and work on personal projects that I release too. I keeps me interested in doing what I do - working for one employer for a long period of time can have detrimental effects on your motivation, skills (don't forget this is a very fast paced, rapidly evolving industry), etc. If you can freelance or contract then do; you might find it very rewarding (as I and many do), but be prepared for:
Also even with all the will in the world there will be days where you just can't do it. You know those days when you get up to go to work and it hurts? Well double it if you have a freelance gig on. You've got to be committed, you need a strong work ethic and be willing to get things done, even when you'd sooner not. |
|||||||
|
|
I don't, however, I want to. You need to go over several things when considering contract work which you need to be mindful:
|
|||||||
|
|
I've been a consultant/contract programmer for the last 30 years or so, and generally have always had more than one contract going on at a time. I do mostly embedded hardware/software design, but also do some website stuff. I have always been careful about avoiding conflicts of interest. I currently have one full-time contract with a startup company. I also have five other small jobs (usually don't have this many). The CEO at the startup knows I am working on other contracts. That's one reason I insist on being a contractor there too instead of an employee (if they want me to come in on Saturdays, I get paid for it). Most of the jobs I am getting paid for on an hourly basis. Two of them I am working for equity or barter. My wife is out of town right now visiting our daughter's family so I'm currently working about 6 1/2 days a week to get caught up a little. I'll cut back when she returns. |
|||
|
|
|
I do, but I am a junior trying to get as much of a portfolio as possible, my 4 day a week job is limited to wordpress sites, and simple ones, so I branch out in my spare time. One day, I won't. Spare time is too precious. |
|||
|
|
AlwaysYou aren't limited to one job (unless by contract). I take every oppertunity I can manage to increase my skill set and networking connections. Even if you don't end up with work at the end of it you meet people that are helpful later on. |
|||
|
|
|
A few principles that guide my decision-making about things like this:
I've tried part-time freelance programming but I felt stressed and tired and wished I had my free time back. On the other hand, working on my own personal projects has been invigorating and has been a chance to learn new things. I would take on part-time freelance jobs -- preferably, those with flexible timelines or scope -- if they offered a chance to learn something new. The money alone is not a significant source of motivation. One thing I've thought about is that being a full-time freelancer would be easier than trying to moonlight. It's just I would rather not worry about where my next paycheck will come from. The pillar of stability provided by a primary job gives me a base from which I can explore new technologies, work on my side projects, and do other things that don't immediately translate into money. |
||||
|
|
|
I know people who have done it and it has always negatively affected their day job. Either they spend time during the day doing stuff related to their night job, telephone calls, email (or worse actually coding) or they just can't focus and get nothing done. IMO, If you are going to put yourself through the hassle why don't you do something that can actually lead to some big reward in the future. Work on something that can turn into a product that can result in a big payday someday. Sure the extra money from a contract job will be nice but that may be an illusion. It's almost a guarantee that your primary job is going to suffer because of your night job. This very well may end up hurting you in your pocketbook from a raise perspective, a reputation perspective and a stress perspective. Any of which could end up costing you more than the extra money you make on the side job. If you're going to risk that then you should be going for the home run (ie. your own business) and not just a few extra bucks from some side job. But that's just my humble opinion. |
|||
|
|
|
I do, but they tend to be writing and related things, not coding. I also make sure to talk to my bosses before I signed the contract for the book. |
|||
|
|
