I'm a bit tired of folks saying older devs are not resistant to change. Reality - with experience some stuff just seems faddy at times over the course of longer career arcs. So yes, older devs can be bit resistant to jumping onto the latest bandwagon.
Funny, that's exactly what I did.
> I'm reiterating the opinion they provided
So am I.
I repair and modify things, typically light commercial vehicles and the equipment mounted to or towed by them. I work on the economic low end of the market so I get all the stuff that real shops want nothing to do with and have had to consider how liable I am for my work. I have had these sorts of discussions in a non-professional context (i.e no money changed hands) with an attorney who specializes in businesses in social services settings (so the advice is probably biased toward whatever he finds his clients defending against most often) and aside from the typical disclaimers[0][1][2][3][4][5] that any responsible lawyer will give you I feel confident enough in my analysis that I put my money where my mouth is making similiar repairs in my day to day life.
The general gist of things is that for a successful lawsuit there has to be some evidence that the work you performed caused the injury and even if so there then also needs to be a precedent of strict liability or you would to have had to do something negligent or check the boxes for some other tort, but I've been advised negligence is the one you really have to watch out for in a professional setting. Negligence is a fuzzy concept but it suffices to say that proving it to the standard required for a civil suit would be a very uphill battle for a reasonably standard repair procedure performed in a reasonably standard setting.
Strict liability scares me far more than a lawsuit arising out of alleged negligence. I can do good, defensible work and stand by it. I cannot know all the areas of law where strict liability may be an issue. I cannot control whether my customers use the things I have repaired for them in a strict liability context (e.g. fumigation, overhead lifting) which could make my party to a lawsuit.
No I didn't pay for the advice but for the volume and riskiness of work I do I'm content.
[0] if you're not paying for it it's not legal advice
[1] nobody can make guarantees about what will happen in court
[2] you have the wrong demographics to get sympathy from judges in this state, they'll expect you to know better than to cut corners so don't cut corners
[3] bad facts, bad case law, hope your malpractice kills a skinhead and not a single mother or you'll be the case law
[4] just defending yourself can be no more than a consultation fee or it can be ruinously expensive
[5] if a megacorp or the state sues you everything goes out the window because the playing field is so unlevel.
CA is a joint and several liability state. Joint and several liability is the legal doctrine that each defendant in a personal injury claim may be held responsible for ALL the victim's economic damages. Importantly this can occur if you are fractionally at fault.
You've parked 10 feet off the side of the freeway, 16 feet away from any lane. Someone is going 80 miles an hour, passing cars, then (likely) falls asleep and veers sharply off the road, then along the side of the road and hits your parked truck.
Even though you are fractionally at fault you are on the hook for everything.
From actually seeing cases first hand
1) If you have money
2) you have a connection to an accident however small, particularly a fatal one, and very particularly with any kind of sympathetic angle (wife and children bereaved and at risk of being homeless etc
then you will be named in the lawsuit. And at least in CA - even if the husband was 90% at fault (to a normal person the one who did things wrong). YOU could pay out everything