The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
printf (and all its variants) is still the debugger in case where there is no debugger (I had a case with micro-controllers, when the only way I found was to write debug info to the second serial port and listen to it with an other application - kind of printf)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Debug.WriteLine is handy, because it's permanent - it's automatically conditional on the DEBUG flag, so it doesn't add overhead in production. Console.WriteLine always tries to output.
Plus, Debug writes to the Listeners collection, so you can add a more permanent trace to a file or similar as well as the Output pane.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Yeah but no, WriteLine() does the same thing but is harder to type! I have even used to some one else 'oh just use a printf() to a label' and got a blank look... printf was for printing every one knew what it did! WriteLine() sense changes as opposed to what it's being pointed to printf() just sent stuff. I'm being grumpy to day, I got to have my picture taken for the web site...
One of the lesser joys of switching jobs is that you get a new OS version. What I have is English Win10 with English as well as Swedish keyboards. What I wanted was to have Swedish keyboard as default. In Win7 this was a bit tricky, I think it took me 10 maybe 15 minutes to find. Annoying but not bad.
Win10 greets me with an abundance of really pretty high-res landscape photos on the lock screen. "Nice but... er... hello? I would like to switch the default keyboard, where did you gents hide that setting this time?" "Ask Windows help. Ask Google you dummy!"