Snarky Comments Found in Code

dalecosp

Especially if they're someone else's, but "you in the past" authorship is also valid.

Everyone is HIGHLY encouraged to participate 😃

// Hey, you guys, it's not 1998 anymore....
$doh = "<td height='1' width='7' align='center'><img src='./images/spacer.gif' width='7' height='1'></td>";

preg_match($doh, $html, $matches);

Derokorian

I don't have access to it now, but at a previous job we were required to have destructors that unset all object properties. I wrote a transcoder and had 17 properties that needed unsetting (for no reason what so ever IMO), so I put a block comment above with an all the things ASCII art that said "UNSET ALL THE THINGS".

NogDog

Just added this succinct comment today, while cobbling junk together to see if I could get something to do something it wasn't originally designed for:

        $thisSlope = isset($question['metadata']['slope'])
                   ? $question['metadata']['slope']
                   : $questionsById[$questionsByTitle[$question['name']]['number']]['slope']; // egad!

sneakyimp

A rather crude comment from years ago. The Russian contractors used numeric keys instead of associative as instructed. NOTE: the code is still running after 12 years:

// modified because some moron didn't use associative keys

    //      get uber categories
    $sql = "SELECT mu.name AS mu_n, mu.id AS mu_i, 
            mc.name AS mc_n, mc.id, mc.seo_name
            from " . UBER_TABLE . " mu, " . CATEGORY_TABLE . " mc
            where mu.id = mc.uber_id and
                    mu.type = 'gen'
            order by mc_n";

dalecosp

This is in vBulletin 4.x:

// We don't want no stinkin' sessionhash

Also these, but not sure that 'snarky' is the right adjective:

//this is not a mistake.

// not quite a bug, but a deliberate feature!

//This is too much work to fix functionality that already doesn't work.

Weedpacket

// Here I am in 2013 dealing with a CSS bug that affects only IE6. Hey, I didn't make this layout!

Bonesnap

I wrote this comment in a project a few years ago when dealing with Authorize.Net's CIM. Instead of simply just updating a value, you had to pull down the customer's profile and recreate the whole thing (with the updated value) and then update that. I hope things have changed since then.

/**
 * According to Authorize.Net's documentation, in order to update a customer's payment information
 * you must get their payment profile and create a new payment profile object, and use the
 * corresponding fields to fill in the new object, changing whatever fields need to be
 * changed while the rest remain the same. You then update using this new payment profile
 * object.
 *
 * Seriously.
 */

sneakyimp

Bonesnap;11061133 wrote:
I wrote this comment in a project a few years ago when dealing with Authorize.Net's CIM. Instead of simply just updating a value, you had to pull down the customer's profile and recreate the whole thing (with the updated value) and then update that. I hope things have changed since then.

Paypal & Authorize.net's SDKs have been just ghastly in the past. You should sling them some snark via twitter or something.