> Now would you rather have code that is having a bug but is readable or having code that is incomprehensible but afaik I don't know the answer myself, but the

> Now would you rather have code that is having a bug but is readable or having code that is incomprehensible but afaik I don't know the answer myself, but the "Practical C Programming" book argues that clear code that doesn't work is preferable to unclear code which works but is hard to understand (because of its messiness). This is because you understand what's wrong about the clear but non-working code and therefore you can fix it. I don't know if this maxim works for every situation, but as a general rule it seems ok.