The cockamamie comment

DoctorJones

I just found this in the dark depths of one of our sites...

// this cockamamie code comes from http://www.codeproject.com/Articles/611175/Radio-Buttons-for-List-Items-in-MVC-4-Problem-with
{
    string rbSiteNameExistingId = ViewContext.ViewData.TemplateInfo.GetFullHtmlFieldId("rbExisting");  
    @Html.RadioButtonFor(m => m.rblSelectedSiteName, "existingSitename", new { id = rbSiteNameExistingId })
    @Html.LabelFor(m => m.rblSelectedSiteName, Model.SiteNameExisting, new { @for = rbSiteNameExistingId })                   
}

If the code is so cockamine, why the fuck did you decide to copy it into our codebase? Jackass.

ScholRLEA

Are you sure that Cockamamie isn't a framework? There are plenty of them out there which the word would describe, so it may just be someone decided to own it and used that as the name.

Yamikuronue

@DoctorJones In my private reality, someone put the code there, and someone else was debugging it, googled, found where it was copied from, and labelled it in disgust.

DoctorJones

: You own it girlfriend!

DoctorJones

@Yamikuronue said in The cockamamie comment:

@DoctorJones In my private reality, someone put the code there, and someone else was debugging it, googled, found where it was copied from, and labelled it in disgust.

Knowing which developer was responsible, that was certainly not the case. Luckily he's no longer with us

groo

@DoctorJones I had to google this word to understand it, then I googled thedailywtf for this word and found a good quote in an article from @Remy:

“Oh, check-ins, sure. Him and that cockamamie source-control stuff. It’s a great way to look busy when you aren’t actually doing any work. We’re running ourselves ragged, working right on the production boxes.”