Right. But he/she will have the time to study it and accept or decline the offer from the customer holding the code. I want to put in touch two parties: the customer and the new programmer. They may like each others or not. They may find an agreement or not. Absolute freedom for both parties.But in this way.. the developers will not have the training needed
The source code will be exclusively mine until that "fatal" day. Or, in those cases where the customer buys the source code from the beginning, rules will be set up in the agreement between us. In my case, one key point is that I have to like the customer as much (or even more) than he/she likes me.if the code is on hands of end-customer - that means can bypass you anytime... you are loosing...
Not the kind of customers I have and who I look forwhat about if the customer is gangster ?
So it should be for a custom job, even without supplying the source code.yes.. this a solution... but a high cost solution too..
An interesting point, indeed. Price is not all, obviously, but this point is somewhat valid.I read once that if 50% of your potential customers aren't put off by your price then you're too cheap.
But in this way.. the developers will not have the training needed... only will know the end-result, how the customer works... and not the background... will be a "Kinder" suprise (this is not an ad) At the other hand is someway secure... But if the code is on hands of end-customer - that means can bypass you anytime... you are loosing...
edit: I am thinking that you mean have the code after death or accident or disappear.. hmmm.. what about if the customer is gangster ?
View attachment 128096
I am sorry telling that.. A g r e e ! hope not but it is true - b4x not spread a lot - need universities to use it...
I love your idea for smaller applications. All in one place - Very neat ! One of my application's source code zips down to about 5.5GB which requires special treatment - I like Aeric's suggestion to lodge the code on GitHub Private Repository.This is a very interesting topic. It's something I've been thinking about since I started developing, and that was in 1985, so I've been thinking about it for a long time.
I've always had that conversation with every new client and I've always told them that the source code goes in a compressed file in the "source code" directory, inside the application.
Nobody, as far as I know, has ever "hacked" the code and sold it elsewhere.
I think that the day I am not available because... I hit the lottery, I will keep the software, except the day I end up in hell (or heaven, who knows), then the customer will have to look for another software and try to transfer the data.
I doubt very much that someone else, another developer, will have the time to try to learn what my software does, it will always be easier for them to try to retrieve the core data (customers, suppliers, items, sales, etc.) and adapt it to their software.
To have an effective contributor to our software it should be someone who has been working with that code for a long time, because they tend to be very customised for each client. It is very difficult for anyone to open our code and find the solution to a problem or add a new functionality to it, it takes a lot of time and I don't know if that is worth it for most people. Even if you are a great developer, like all of you.
Translated with www.DeepL.com/Translator (free version)