Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
rutee07247612dHuman sacrifice except not human.
"The people who are supposed to help me with the codebase don't know what any of the code does at all"
More people = more results though, ignoring any of the practicalities, which we never need to worry about, that's a dev job.
"I'm also not a mind reader."
You should be a mind reader with the other devs. You devs are like one big cohesive brain right? I sure as hell don't understand you, so I assume you must understand each other.
"I cannot perform hypnosis or some fantastical witchcraft to tap into memories they cannot remember themselves."
What *do* you do then?! Call yourself a dev?
In all seriousness though, good luck with it all, and you're doing the right thing by nagging people and documenting *everything*. Get to a point where you can get things up and running and understand the codebase enough to work on it, make sure you have it in writing whenever someone says something like "oh I've been working on x for months but I just haven't committed yet so don't touch that please" and "oh we don't use that code anymore but it's there just in case we break anything", and make sure the stuff *you* write is watertight.
This has all the hallmarks of a failing project. Make sure that if / when it fails, you have a paper trail showing you were a positive impact, and not the reason for its failure. Don't let yourself get set up as the fall guy.