I recently started helping with a project for large volunteering organization that uses a large code base to process all the administrative duties of the organization. The entire code base is completely undocumented. Zero comments, zero explanation, I don't even know what all it does are and the interface is a maze. All the code up to this point has been written by one guy who works on it every once in a while in Java. This is all volunteer work and I work a full time job so I can't exactly tell the guy to stop being a shitty developer nor do I have the time to do a complete rewrite. Still want to help fix this project. Wat do? Also unmaintainable code stories
Nigga thats why its work. If it wasn't volunteer work you'd be getting paid a decent amount for it. You don't understand the code because you haven't spent the time to understand it, not because its not documented. Just because you're not actively programming doesn't mean it's not part of your job.
>Wat do?
Git gud and deal. Once you understand it document it yourself
>>55804381
Rewrite it from scratch in a decent language and document as you go. It's easier to rewrite most Java projects since they're generally so poorly written.
I had a similar story. I just resigned and didn't want to lost time arguing with people that couldn't code properly.
>>55804595
Wouldn't it being poorly written make it more difficult to rewrite?
>>55804381
Unless you're willing to rewrite it there's nothing you can do. Most Java developers have irreparable brain damage. Just walk away now.