[ladyattis]

I agree with the comments in the video since often I find myself dealing with opaque code. Having code that's opaque makes it hard to make sense of what it does, when it does what it does, and what happens when it fails. Having code that's obviously less than optimal but still understandable is far better as the OP mentions in the video. At least with bad code that's understandable you can improve it sometimes if the underlying requirements and dependencies aren't too deep (otherwise, you're gonna break something and it's better to just leave it be bad or ugly code).