Quality from Outercurve
Directly from the weekly podcast of the Orchard Steering Group.
I do a lot of shit that could use a similar comment while working around buggy frameworks. Although at this point I generally assume there is no way to do it right.
I do a lot of shit that could use a similar comment while working around buggy frameworks. Although at this point I generally assume there is no way to do it right.That reminds me of some XML processing I was doing recently (in Java, alas) which would mysteriously lose the content of some attributes. The workaround was to use some XPath to read the content of every attribute in the document.
That's actually quite helpful, it's refreshing to see such honesty in comments. It means it's going to get more scrutiny in a code review, that's for sure.
I see no WTF here. He got it working, he's not confident in the solution, he can't really explain it, either because he doesn't really know, or the framework has bugs internal to it, but he has it working now, with the idea that if he is wrong, unexpected results could come in later testing and this will have to be looked at again. Yes a code review will also scrutinize this more, but if no one has a better way or other input on why this works or doesn't, you pass it with a note.