XV and Crisis core are the best FF games just because they aren't turn based.
And well, I guess everybody can make mistakes. But SE really do need testers for all this. As a programmer myself I know sometimes you just say "yeah this is fine" and don't even try what you did. That's what the testers are for. To validate your work. I'm sure this developer just had a little mistake in his/her code, but this happend instead. I wish the best luck for him/her.
I doubt this was a developer pushing out code that they believe works. At the very least it wouldn't have deleted all the game files. I think it's a bit more than this, and it leaves me to believe there are multiple points where this failure would have been caught and prevented, and each point failed to do their job.
Could be a bad line of code that worked independently but caused the entire project to fail being recompiled, and instead of someone noticing and sending it back, they simply pushed out the new update, and deleted the old files in the process, which of course with the failed project means nothing was replacing the deleted files. And whoever would have sent the files to be published onto Steam didn't check the files, or even bother to look at the size of the archive, as they would have noticed either the entire archive is 0kbs big or seen there were no files to begin with.
And that's all assuming it's not so easy to just pushed an update and delete files without adding in replacements. So really there are a bunch of points in all of this that should have prevented this kind of failure, and each point failed to do it's job, resulting in this, an epic failure. Heck, even if some random person managed to hack into either their systems or steam and deleted everything, this should have been noticed.
Plus the fact SE had to fix this by pushing out an older version of their software doesn't help the matters either, because it shows they don't keep backups of their source code, a reason why the original FF7 for Windows 9x was based on their Beta of the PSX release and not the full release. SE doesn't save their source code or use some sort of revision management system like git or svn. Once they believe they have something that works, they remove all old versions of their software/code, and then try to push out the updated version, only to realize after they've destroyed their means of undoing all this they broke their stuff and have to hope at least one of their employees kept an offline copy of all their work.