Part Two: Technical Self-Employment For All
MoNickels writes "I've posted
part two of the article series encouraging the unemployed to take up freelance technical support, including advice on knowing if this work is right for you, marketing yourself, learning on the job, handling and educating clients, managing the business, the temperament required, and the negative aspects of the work." See part one if you missed it.
What do you do about health insurance?
I'm not the devil.. just his advocate.
The personality checklist fits the bill of both a technician and an entrepenuer very well.
I'd also say it is a pretty decent description of the typical slashdot reader, IMHO
I didn't study non-stop for the last 11 years just to join the ranks of technical support. The whole reason for me to get into technology and eventually into IT was to 'build cool sh...t' - not to listen to some technophobe bitching about why her/his system got corrupted after opening some suspicous email attachment. Seriously, is that all we'll be relegated to do? Hey, I rather start laying bricks then - at least I have something productive to look as the fruits of my work. Just my two cents, I bet many will disagree - but I'm not wired that way...
"2. Never admit that you don't know something - act like you know everything that has to do with computing" Terrible idea. Every dweeb out there has enough ego to support pretending that they know everything. I keep my clients by being able to admit I don't know, then find out. They appreciate the honesty, instead of the pseudo-consultants that talk up a storm.
2. Never admit that you don't know something - act like you know everything that has to do with computing
2a. Never get caught in a lie. Admitting you don't know something might be a negative, but it's better than proving yourself to be deceitful.
2. Never admit that you don't know something - act like you know everything that has to do with computing.
Interviewers can smell bullshit from a mile away.
100% Insightful
...an unemployed (God knows the real reason why), person off the street working on my network... while he is learning his job via OJT.
Wonderful.
I am very small, utmostly microscopic.
Glamour my @$$. There is nothing remotely glamorous about doing tech support for small businesses. It's all about showing up, getting things to work, and getting the heck out. He runs a one person consulting business. At the end of the day his stuff either works, or he doesn't get paid. Yes, talking to people is a requisite part of being in business for yourself, but that doesn't mean that he doesn't have to actually fix his clients problems.
$50 to $100 may sound "glamorous" to someone who has never been in business for themselves, but the fact of the matter it is that this fee is so low that larger consulting firms can't even pretend to compete. Those prices simply don't leave any room for overhead. Once you take into consideration that you only get paid for "billable" hours, and the fact that you get to do all the bookkeeping, billing, tax work, etc. it isn't nearly the deal that it appears to be. Being a plumber or an electrician is probably more lucrative.
It's definitely doable, and there really is plenty of work. However, it's hard work, without paid vacations (or respite of any kind :).
Snag a local non-profit & help them, get them going with all the latest :))
slickest stuff from novell and what opensource has to offer as a show of what you can do.
http://www.giftsinkind.org/ has a great Novell product donation policy, &
http://www.techsoup.org/ has some other good stuff too (i want that 24port
cisco switch, can i be a nonprofit too?
Also check out www.computerclub.org/nonprofit.htm, that has some good links
on it also, & had good luck with members of www.cristina.org too like reboot
from Atlanta.
Plunk a couple of these very satisfied not-for-profit companies up as testimonials to your work & you may very well be off & running with your own consulting biz. Just dont forget about the nonprofits once you actually have paying clients.
if that were true, I wouldn't be sitting next to a guy with '5 years' of .net experience.
The Kruger Dunning explains most post on