11
\$\begingroup\$

As developers we sometimes come across bug in third part code / tools / stuff we can't change and so we write a hack/workaround or some other dirty piece of code.

Is the "hack" reviewable? It matches everything in the FAQ (as I understand it) but its about working around broken code and often how "pretty" it makes my code look is irrelevant.

Specifically I asked a question about an issue I was having with an IDE + framework working together and posted how I worked around it. Even though I'm hoping for a non-hacky answer I think it could still be written better.

\$\endgroup\$

1 Answer 1

Reset to default
10
\$\begingroup\$

I think the main criterion here should be "Do you want it to be good code?" If so, it should be on-topic for review.

You should, of course, mention the rationale for the ugly code in the question, and state what is and isn't within your control. It should be fair game for reviewers to answer with a completely different (and hopefully better) workaround.

\$\endgroup\$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .