Dangerous - debugging statements can sometimes make it into final builds, and can be read with tools like SysInternal's DebugView. Not the sort of thing you want certain customers to see (or your boss would want any customer to see). People have been fired for less from less well humoured employers.
In comments, however, I feel to vent as much spleen as I like. I've been known to write multi-screen essays on exactly why certain Microsoft APIs suck great steaming goats' cocks. (But they do also explain the problem and solutions in detail, hopefully preventing someone from later going "That's an odd piece of code, I'll just refactor that" and creating a regression nightmare.)
I've the joy that the projects we do are internal and I'm the only person writing it (from the very start all the way through to final release and updates afterward) so comments etc. can be whatever I want thm to be :)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-05-10 02:09 pm (UTC)no subject
Date: 2004-05-10 07:15 pm (UTC)In comments, however, I feel to vent as much spleen as I like. I've been known to write multi-screen essays on exactly why certain Microsoft APIs suck great steaming goats' cocks. (But they do also explain the problem and solutions in detail, hopefully preventing someone from later going "That's an odd piece of code, I'll just refactor that" and creating a regression nightmare.)
no subject
Date: 2004-05-11 08:25 am (UTC)