Re: Datasheet-flation?

On 12/2/2024 6:16 AM, Carlos E.R. wrote:

Besides, I would tell my boss not to pay him or to sue.

>
That assumes you have someone competent to review the original work.
Often, folks hire "outside talent" because they don't have the
skills, internally.

 Correct, that's why they hired me ;-)

I was apparently hired at my last 9-to-5 to "make the other guy redundant".
I guess he had tried to "hold up" (extort) the employer and they didn't like
being on the weak side of that "negotiation".

And, such "evaluations" are always subjective; you can't POINT to
some particular thing and say "this is bad" -- even if the whole
thing is bad!  The boss weighs that against "Yeah, but does it WORK?
If I don't pay him, will I have to find someone else to solve MY
problem??  And, how long will THAT take?"

 There is that. He would have to pay that programmer in the future for any small modification of the program, though. And he did want a few modifications (the specs from the client got modified as they saw the result)

IME, it's in BOTH parties' best interests for the "transaction"
to be fair and equitable.
I've always tried to "not be needed" at the end of a project.
First, this is a deliberate (over?)compensation to avoid being
the sort of guy who effectively extorts the client by keeping
them "needy".
But, more importantly, I want to move on and do something else.
Making a *second* (of ANYTHING), to me, is incredibly boring.
You learn comparatively little for a shitload of time invested!
By knowing that I've not left a client dependant/reliant on me
(my services), its morally easier to "move on".