4 ms·
I get the angst, and share it, on the other side of the table is a company paying you for your "full time" employment, they want to believe they have paid for a
by ChuckMcM 11y ago
I get the angst, and share it, on the other side of the table is a company paying you for your "full time" employment, they want to believe they have paid for all your time.
So the angst arises when you aren't really giving them all your time, you are keeping some for yourself to do things that are of interest to you and not in your employer's interest[1].
That is why they want you make a choice, either commit or don't, all in, or not. If you want to parcel out your time, then contracting is a much better way to do that, neither side feels like they are being taken advantage of.
Of course there are IP issues, and one which I hope will someday be rationalized by a better IP policy and framework[2] but contracting helps there too. You take ownership of your own "overhead" (benefits, vacation plans, etc) and then you sell the time you have to work on things either to someone else for direct payment, or to yourself as an investment in a future revenue stream.
[1] They would argue that if you have time to work on that you could have used that time to work further on your project they assigned you. Vacation and leisure, keeps you balanced so is in the employers interest.
[2] And realize that currently 'time to exhausting all the hydrogen fuel in the Sun' is looking like it will happen first.
- joosters 11y agoThe time I am committing to a company is in the hours per week that I am paid to work. There's 168 hours in a week, if you're not paying me for all of them, I can do what I like in the remaining time. Dedicating your whole waking life to a company is plain stupid.
- btilly 11y agoThere are different classes of employee. Your attitude is appropriate if you clock in, clock out, and are paid different amounts in different weeks if you show up for different lengths of time. However I'm guessing that you are paid a fixed salary and aren't clocked. And you aren't a contractor. In that case you're a professional employee. You legally have a working relationship with them 24x7. Which is why you're not paid overtime to take clients out to dinner, or answer a page in the middle of the night. But if that relationship always exists, who owns the intellectual property that you create away from the office? This is up to a combination of the contract you signed, and local laws.
- joosters 11y agoSorry, I was unclear. I was expressing my view, and not trying to explain any kind of legal position. What I was saying was that I cannot see how a company can justify owning everything I do outside of my work hours. Whether or not that is in my contract is a different matter. I would urge any potential employee to negotiate any such bad contract if they can. If my job involved taking clients out to dinner or answering pages in the middle of the night regularly, I would damn well want to be paid for it. Not per-call, but the additional workload would have to be reflected in my salary. Put it this way: If you are a programmer who never has to do any out-of-hours support, and then suddenly your boss says that you need to be on call 24x7, you'd be a fool not to ask for more pay.
- btilly 11y agoThe point is that "outside your work hours" is undefined. If you're receiving a page, is that work hours? If you're thinking about work during your shower, is that work hours? Most people do a lot of productive work outside regular work hours and outside of the work place. It would be a real problem if they could then tell their employer, "This thing you're depending on? It is actually mine! You have to negotiate for it!" So laws are passed to guarantee that it is clear who owns the brilliant solution to a work problem that you dream up in the shower. The question is how much other stuff gets swept up in that net.
- ChuckMcM 11y agoExactly this. If you are a professional, and in the US, this also called an "exempt" employee, you are paid a fixed salary (nominally higher than an hourly employee makes) and you don't "clock in" and "clock out", you are always on the clock. That is the nature of the employment relationship you have with your employer. Contrast that with say Lawyers or contractors, or checkout clerks at the market who sell an hour's worth of work for $x. This is really important to understand and internalize as an engineer. It is important because it is the way employment law looks at the relationship and that is the law which you are compelled to obey if you want to continue working/living where you are.
- 11y ago
- myth_buster 11y agoI don't think full time means 24hrs/day as that would be against labor laws! Also if a developer is earning 100K it would amount to $11.5/hr.
- lg 11y agoMy pay stub helpfully lists my 'pay rate', that number * 40 * 52 = my salary. If my employer expects me to work 168 hrs/week then I'd certainly be willing to have that conversation but I expect the appropriate change of multiplier :)
- deleted 11y ago[deleted]
- simmons 11y agoThis is great advice. I sympathize with some of the concerns in the original post, which is a big part of why I haven't been a full-time employee in 16 years. From reading the comments of others, it sounds like going back to being an FTE would be quite a shock.
- ryandvm 11y agoI disagree entirely. Indeed I find the suggestion that your employer owns the fruits of all your free time to be absolutely asinine. Employees aren't indentured servants. Full time, salaried employment in the United States is de facto 40 hours. If you work less than that (without prior agreement), you can expect repercussions. If you work more than that, you can expect... nothing. Ergo what is being purchased under a full-time agreement is clearly the customary amount of work. Anything beyond that is being done so at the beneficence of the employee (or more likely as part of a long-term strategic play). In any case, it is the very definition of "above and beyond the call of duty".