|
I'm going to pass on helping them after everyone's advice. the industrial equipment I controlled was mostly for controlled atmosphere fruit storage warehouses; a single room could be between 1/2 to 2 million dollars in fruit multiply that times say 20 rooms at a customer facility, same system code runs on almost 200 facility's, that's a lot of liability.
while yes, an LLC is an option, it also seem like a lot of work to setup when I just want to sever ties with the previous place and move on.
Thanks for your advice, I'll keep it in mind if I ever decide to go solo.
|
|
|
|
|
IYDMA, what is "cheap enough" and how much coverage does that get you?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Matt McGuire wrote: I'm concerned with protecting myself against any sort of liability or longer term support
As others have said:
- Consult a good lawyer about liability!
- If you take this on, get liability insurance!
Matt McGuire wrote: I've got some guilt on leaving them without another programmer to pick up the load.
As you didn't walk out without notice, this is not your problem. Your ex-manager gets paid in order to worry about what happens if you quit / walk under a bus / run off to join an ashram / whatever.
Unless they will accept a contract that (a) protects you from liability at the level you had as an employee and (b) is limited to the work done - no long-term support, I would pass.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Thanks, It's looking like too much of a hassle so, I'm going to let them know that I'm passing. Before I left, I said I could give some limited support until they got a new dev; like questions over the phone or emails while my memory still held.
I'm pretty sure I never said anything about touching the code, likely they just assumed it; which is odd, because that usually required being on a customer's site to test changes to the software in how it interacts with all the equipment, no simulating that.
|
|
|
|
|
Matt McGuire wrote: now that I'm no longer employed by them I'm worried if something did go wrong, I would get it in the end.
If you're doing this make sure you have a signed contract that states you're not liable for any damages, etc.
Matt McGuire wrote: But I've got some guilt on leaving them without another programmer to pick up the load.
That's their problem, you're not responsible for their hiring process.
Or you could just say your new employer doesn't like you doing freelance work on the side.
It's actually part of a lot of employment contracts where I live (you might want to check that anyway).
Or even simpler, you're fully booked and can't take on any new assignments for the time being 
In any case you're not leaving them hanging.
You've done your job, if I read between the lines you weren't that well compensated for it, and they ultimately failed to hire a replacement.
|
|
|
|
|
they had actually promised me another developer 12+ years ago to take some of the load off, but they never seemed to get around to looking.
Anyway, thanks for the advice. I think I'm going to use what you said and say my current employer has some issues with this, and for legal reasons I can't touch the code (still all technically true).
|
|
|
|
|
Matt McGuire wrote: there's a lot of liability real quick if something went wrong
If that's the case, then IMO it really looks bad on them that they'd still rather hand that work to a freelancer (how seriously are they taking the risks?)
Leave it to them to find a suitable replacement. You quit for a reason.
|
|
|
|
|
Thanks. With everyone's advice, I think I'm going to pass, I really don't need this headache right now. before I left I let them know I could give limited support; as in: training the next dev on the software structure, and answering basic questions by email, while my memory on that system still held. Really didn't think they would be calling me in for code changes.
|
|
|
|
|
As a developer and business owner, I'm going to disagree with the prevailing opinion of 'look after yourself only and ignore the ex employer's interest completely'. These are the issues as I see them:-
-You were primarily responsible for the development of the control software over 18 years.
-Your employer clearly trusts your skills and integrity.
-Employing another developer will take months if not longer for them to get up to speed.
-There is a danger of a new developer corrupting the code.
-Burning bridges can be a costly mistake. new positions often turn out to be worse than the previous. People often go back to previous jobs.
-Protecting yourself is not a big deal. All you need is a signed letter from the empolyer setting out exactly what they want you to do and a clause which indemnifies you against any liability whatsoever. I recommend you give them the 'no liability clause', if you don't want to pay legal fees, there are plenty templates on the internet OR use one from one of the major cloud platform EULAS and adapt for dev work.
As developers we also carry an unsaid responsibility for the products we create. You did say you would provide support before leaving. If you are a developer 'support' means code. How would you like it if all support for a product you relied on simply stopped one day.
Of course you are free to set your own rates.
There are always two sides. It pays to consider both.
PostScript
There is one thing I should add. Professional Indemnity Insurance is a necessity. DerekTP123 has some good advice on this.
Good luck with whatever you decide.
modified 21-Jun-18 19:33pm.
|
|
|
|
|
As others have pointed out, you need Professional Indemnity insurance. Don't do a THING for money as a freelancer without it; you could potentially end up bankrupt. It doesn't cost a fortune, and you can claim the cost as an expense for tax purposes. And oddly enough, the insurer never seems to require any sort of evidence whatsoever that you're even vaguely competent, when it comes to software. Most policies do, though, have some sort of clause that only gives protection if you are following "industry best practice" so if you're negligent then even the insurance won't cover you.
PI insurance is just another reason why freelancer rates have to be higher than employee rates; we have more costs, and take higher risks.
|
|
|
|
|
First, you already left them. So if they are hanging, it is not your fault.
Second, when being asked back to consult, they are asking to use your most valuable time... Your free time... Weekends.
I look at it this way. If you made $80K/yr ($40/hr) before you left, then as a consultant, you have to start at TRIPLE that ($120/hr). Next, if they want you after you are already working full-time, DOUBLE THAT rate, getting you to $240/hr. Next, if they are the shady type, you make them buy your time, in 10hr chunks, in advance.
Finally, they pick up the cost of the lawyer, up front that will indemnify you and make sure the company will take full responsibility with the ownership of the code.
So, in writing you put those points. Simply put, I am not interested in doing this unless you are willing to pay $250/hr, up front in 10hr increments, and pay the expenses involved in me getting a lawyer to write up a contract that indemnifies me against any damages.
At this point, you are "real estate". You have a specific location in the knowledge of the environment that makes you like a Michael Jordan. You can pick up the ball and move it down the court with ease... You charge "RENT" for that kind of knowledge/ability... And frankly, depending on the size of the company, I wouldn't be against asking for $500/hr...
Why? Because then it becomes them saying no. One of the things I learned (much too late in life), is that if you don't ask, you wont get. When I learned this... I found 1 in 10 will literally take the offer. And if they say NO THANKS... Then there is nothing to feel guilty about!
Now, if they agree, you have to really be ready to do that work for that amount of money... So keep increasing it, until you will GLADLY do the work!
|
|
|
|
|
Matt McGuire wrote: But I've got some guilt on leaving them without another programmer to pick up the load.
That's the problem. You should have no guilt about moving along.
It's nice that you want to help out, but you have no obligation. If you don't want to do it, say so and wish them luck in their endeavors.
Maybe it's smarter of you to have them find another developer, then take on a contract to help bring that person up to speed. Be a mentor to the new person, but don't actually do any of the development. So your knowledge gets passed along, but you shouldn't have any liability for the actual code.
|
|
|
|
|
That's what "service contracts" are for.
And you can put anything in the contract that you want; as long as both parties sign and are of age and sane.
Some institutions require $5,000,000 in liability insurance.
And never promise it will be "bug free" (even if you believe it).
Set limits on response times, response windows, client responsibilities (testing!!!!), etc.
(And say you will work WITH them; not FOR them ...).
AND ... add that agreement can be ended at any time, by either party, for no particular reason.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
modified 21-Jun-18 14:50pm.
|
|
|
|
|
Or lighting up with more people trying their hand at the 20 min Arduino Binary Counter challenge. And some of our members are participating in more than 1 challenge - we love that enthusiasm!
Congrats to our spot prize winner of the day - Florian. We hope you enjoy your new Arduino starter kit!
|
|
|
|
|
Does Captain Obvious shave with Occam's Razor?
|
|
|
|
|
|
If he shaves and if he has Occam's Razor and if it's sharp enough...
|
|
|
|
|
Yes, and he buys new blades with common cents.
|
|
|
|
|
|
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS.
The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on.
It didn't work out and it broke the application, as I have told them many times before.
But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that.
Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
|
|
|
|
|
You did the right thing. But the next time this happens you should find somebody on "your side" to insist on your line. But maybe that function is missing from your organisation 
... such stuff as dreams are made on
|
|
|
|
|
Yeah, basically all my co-workers are on another country, including the scrum master and pm. My boss here just deal with things like contracts, hiring and etc.
|
|
|
|
|
Yeah but such requests should pass the scrum-master, regardless of location.
... such stuff as dreams are made on
|
|
|
|
|
It sounds like you did your job and warned them of the consequences like a professional should. They are the managers and should be practiced with risk management. They made the mistake and are the accountable ones, not you; you did things correctly.
|
|
|
|
|
You did ok.
Good to keep records.
You could have gone to your manager and tell him the requested changes would break the application before doing them.
I'd rather be phishing!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
