Repair research C code
Support memory issues, array sizes, file I/O, training-data conversion, Visual Studio support, and Windows GUI conversion.
Legacy AI / C Repair
I read, run, repair, and document old C, C++, Java, SWT, Tomcat, Windows GUI, and legacy AI or neural-network code. Before new development, I diagnose the value and repair risk of existing assets.
What I Repair
Publicly shareable experience includes C neural-network repair, Java/SWT search clients, Tomcat/Web migration, and Docker/YOLO/Flower environment setup.
Support memory issues, array sizes, file I/O, training-data conversion, Visual Studio support, and Windows GUI conversion.
Read old Java screens, XML/XSD/JAXB configuration, search clients, and server communication logic.
Organize Docker, Python, image data, and federated-learning environments into repeatable procedures.
Separate what is worth repairing by checking screens, DBs, CSV, logs, batches, shells, and test steps.
Repair Flow
Instead of starting a large rewrite immediately, first check whether the code can be read, run, and repaired, and whether repair has value.
First Packages
Review one source folder and summarize structure, build status, risks, and repair policy.
Guide price: from 15,000 yenRestore old C/Java/Python environments toward a runnable state on Windows, Linux, or Docker.
Guide price: from 30,000 yenFix known errors, convert input data, add logs, and prepare run instructions.
Guide price: from 50,000 yenPublic Case Types
Without exposing confidential details, the solved problem type can become strong sales material.
Consultation
A source folder, executable, error screenshot, specification, or old memo is enough to start.
Official contact
mou@wataobao.org
080-3094-1588
Fields
C / C++ / Java / SWT / Tomcat / Python / Docker / YOLO / Flower / Windows / Linux