4 ms·
I've just recently been thinking about "working" 20-30 hours a week, so I have time to work on some projects of my own. I find there are two main obstacles to
by kozmikyak 14y ago
I've just recently been thinking about "working" 20-30 hours a week, so I have time to work on some projects of my own. I find there are two main obstacles to reducing my paid "work" load.
1. I currently rely on contract work, and I find that I don't have contacts that want to employ a contractor for 20-30 hours a week, or even a set of contractors who want to employ for a combined 20-30 hours a week. Usually when people hire contractors, they want something done as soon as possible, without distractions.
To obtain my desired work hours per week, I will have to greatly extend my contacts list. Which I should do anyway, but it won't happen overnight.
2. Health insurance. I have mild schizophrenia which, untreated, makes it hard for me to reason logically. With the proper medication and care I remain gainfully employed as a dev/sysadmin/devops role. On top of that I have Tourette syndrome.
Insurance for anyone with these kinds of pre-existing conditions is expensive; laws changed such that very soon they won't be able to _deny_ it to me, but they can price it as high as they like. Despite having substantial savings, long periods of not having any income is out of the question for me. Therefore, either traditional corporate employment, or full-time contract work at a high enough wage to pay for high-quality insurance, are the way to go.
I don't mention these things in a "waaaa, waaaaa, I'm so helpless" way--far from it. I've attained more than the average person in my career, in terms of skills and pay.
Rather, I think people on this site forget sometimes that not everyone is suited to risk it all on a startup, and not everyone is cut out to be an entrepreneur, and not everyone has to be an A+++++ level developer to get by, and it's not a sin to seek some stability.