Slashdot Mirror


Is Finding Part Time Work In IT Unrealistic?

I like my current job writes "Having worked full-time in IT for the past 12 years, I would really like to work less and focus on other goals and priorities in my life. I asked my current employer and was shot down. It seems like everyone I know in IT works full-time except for entry-level help desk staff. Striking out on my own seems to be the only way to control the ball and chain around my ankle. However, my experience with independent consulting is a 'feast or famine' situation, with work coming all at once, thus making part-time impossible, or the other extreme (which is even more likely). Is part-time work a pipe dream in IT? Maybe a career in toilet cleaning is calling me."

4 of 396 comments (clear)

  1. The Boss Decides... so be the Boss by alain94040 · · Score: 5, Insightful

    One reason corporations don't like part-time is that as long as you are full-time, you actually tend to work way past 40 hours a week. You do whatever it takes to get the job done, under impossible deadlines.

    Once you are part-time, you start saying no to crazy demands. Corporations just hate that.

    My answer? Be your own boss. It comes with a caveat: starting your own business alone is a bad idea. Guess what? It takes more than one person to provide something of value. It doesn't take an army of hundreds, but a small dedicated group of friends can do amazing things. The sum really is larger than the parts.

    Take a look at fairsoftware.net. It was designed for exactly that purpose: geeks starting a side business together.

    1. Re:The Boss Decides... so be the Boss by plover · · Score: 5, Insightful

      There's always a catch.

      I have several friends who have tried this over the years, and know other people who have tried this. The bottom line is: friendships can fail under the strain of a business relationship, and when the friendship fails, the business is not far behind. My wife has worked for three of these ventures over the last 15 years, where two friends created a business, had a falling out, and the business collapsed as a result. All three times. In none of those cases were the owners able to remain friends. She is now with a family owned business who are having their own difficulties right now, but there's no risk of a partnership collapsing here to accelerate it.

      Being in it with a friend at a stressful time, when you have one idea about how to save the company, and your friend has a different-and-incompatible idea, and there's just enough money left to try one of your ideas, that's a pressure cooker not many relationships can survive.

      Now, you may have a "less permanent" idea about business. Maybe you just want to start a company for the purpose of working, but don't care if it stays together longer than three years or so. As long as you and your partners agree up front, that may work for you.

      One other piece of advice -- hire an independent person to do the books, someone you both can trust. Not just an external accountant, but a bookkeeper who sees the day-to-day spending, and lets you both know that the other isn't spending money foolishly.

      I will say that family owned businesses seem to be the exception to the rule, as long as Dad or Mom or Grandpa is the "boss" and everyone else understands that.

      --
      John
  2. On the right track by BadAnalogyGuy · · Score: 5, Insightful

    If you are involved in the development of software then you will be on the treadmill. The only way out is to either strike out on your own or to give up on the industry altogether.

    Personally, I wouldn't do it. But I can see how leaving the industry completely is attractive for some. Just be prepared for the paycut.

    But then again, money isn't everything, and if you can improve your quality of life, even with a paycut, then more power to you.

  3. Re:I did it by murdocj · · Score: 5, Insightful

    So you were only available 2 days a week, and you're upset that your boss couldn't somehow schedule all of the work to occur those 2 days? You say "he placed another employee to deal with issues that came up while I was out of the office"... what was he supposed to do? Put the problem on hold 4-5 days till you were available?

    It's one thing to say "this is my code, my system, no one else touches it without talking to me first" if you are available normal working hours. If you aren't available, guess what, someone else is going to have to deal with the "issues" that come up while you are out of the office. Where I work, people are nervous if there's only one full time employee who understands how to do something, having a part-timer be the only one would be utterly unacceptable, unless the function is pretty marginal to being with.