What if I want to replace you as my developer? Back
My clients are everything. I work very hard to make you so happy you will never want to replace me, but life is life. The application is yours. You may do with it what you want. If you move to another part of the country, if I get hit by a car, or for some other reason you want to change developers you certainly have the freedom to do so.
I bring this up only because it is an important business principle that, as much as is possible, you never allow yourself to be too dependent on any one entity. You will not be too dependent on me. In a worst case scenario, if you want to replace me, another developer should be able to take over with relative ease.
I do not write in a proprietary framework. That is, sometimes development companies create their own framework (a way of doing things) that is very proprietary or unique to themselves. I do not write in ways that are proprietary. I use simple Microsoft Access methods and procedures that other developers will readily understand.
Back
My clients are everything. I work very hard to make you so happy you will never want to replace me, but life is life. The application is yours. You may do with it what you want. If you move to another part of the country, if I get hit by a car, or for some other reason you want to change developers you certainly have the freedom to do so.
I bring this up only because it is an important business principle that, as much as is possible, you never allow yourself to be too dependent on any one entity. You will not be too dependent on me. In a worst case scenario, if you want to replace me, another developer should be able to take over with relative ease.
I do not write in a proprietary framework. That is, sometimes development companies create their own framework (a way of doing things) that is very proprietary or unique to themselves. I do not write in ways that are proprietary. I use simple Microsoft Access methods and procedures that other developers will readily understand.
Back