Dale (dalestan) wrote,
Dale
dalestan

On "That can't be done because ..."

"... because it can be done."

At least that's what seems to be happening lately when I try to explain why I can't implement something in NFORenum. I tried to explain why a pretty-printer was impossible, and ended up writing one.
I tried to explain why a variational-accessibility check couldn't be done. And ended up writing one.
I should either quit trying to explain why I can't do something, or try to explain more often; depending on whether it's a feature I want to implement or one I'd prefer not to implement.

I guess this is a good thing, and it even makes sense when I think about it, but it's just strange to answer "Why can't you do $FOO?" with "I can."

So, should I explain why I can't do class DC00 TextID checks and random 2 bit-usage checks next?
Subscribe
  • Post a new comment

    Error

    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 0 comments