Gameboy dev kit has parts like these in it's documentation...

Worst documentation? I have seen worse than that.

I should really write documentation for my old projects...
Meh. I'll do it tomorrow...

Our documentation is currently stored in a VM image after the host died, meaning we have no access to anything - good times!

Coldfusion.

That shit gave me nightmares.

Worst documentation I've dealt with? It's cute that you think the other devs document jack shit.

What's that "documentation" you're talking about?

Hitbox.tv chat roles... ¯\_(ツ)_/¯

My coworkers are great; they actually manage to solve problems in really unexpected ways.

Problem: documentation is not up-to-date with latest changes.
My fix: update it, make sure it has all the latest modifications.
Their fix: if there's no documentation, they can't complain about it...

I took over an application that consisted of 4 MSSQL (2005 at the time) databases, hundreds of tables, thousands of stored procedures, maybe a 1/4 of them actual still being used, external links to more than 20 other databases (MSSQL, Oracle and DB2) which all ran from a single "master" stored proc that was kicked off nightly by scheduled job.

The existing documentation consisted of a single word document, about three pages long, describing how to set up the application... on the Sql Server 6 server it had been originally created on two generations ago.

TeamSpeak 3 Plugin Documentation. There is likely none.