While operating a web system or business system, it is common to lose contact with previous developers. I've done this several times.
There is something I want to fix, but I can't handle it. I don't know the server or domain information. The cause cannot be investigated even though there is an error. This can also affect your day-to-day work.
The first thing I want to check is the information I currently have.
Server login information. Domain and DNS management information. Presence or absence of source code. Database information. Accounts on the admin screen. Usage of payments and external APIs.
The more of these, the easier it is to investigate and take over.
Even if you don't have the source code, you may still be able to check it if you have access to the server. Even if you don't know anything, you can handle it by rebuilding it, but by knowing it, you can reduce costs and risks.
Next, organize what you want to do with your current system.
You want to fix some of it? Do you want to fix the problem? You want to rebuild the old system? Do you want to add new features?
Depending on the purpose, the way the survey is conducted and the way the estimates are issued will change.
I think there is a lot of anxiety about systems that can't get in touch with developers. However, if you organize and check the information, you may be able to take over.
At Makoto Tejima, we can help you investigate, refurbish, and remake your existing systems. First of all, you can contact us for as much information as you can understand.
