I hate messy code.
-
Code that isn't lined up and is all over the place make my teeth itch. Just thought I'd share that with you all. cheers, Chris Maunder
-
Code that isn't lined up and is all over the place make my teeth itch. Just thought I'd share that with you all. cheers, Chris Maunder
Chris Maunder wrote: Just thought I'd share that with you all. "Hi everybody, my name is David and I have a coding problem." ;) That's why god invented ALT+F8... or was that CTRL+F8... dammit now I've gotta fire up MSVC++ before I go insane... ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
-
Code that isn't lined up and is all over the place make my teeth itch. Just thought I'd share that with you all. cheers, Chris Maunder
I hate code like that too. (And one day I'll stop writing it) Michael :-)
-
Chris Maunder wrote: Just thought I'd share that with you all. "Hi everybody, my name is David and I have a coding problem." ;) That's why god invented ALT+F8... or was that CTRL+F8... dammit now I've gotta fire up MSVC++ before I go insane... ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
it's ctrl-shift-f over here in the US. but it messes up block /*..*/ comments -c
Smaller Animals Software, Inc. You're the icing - on the cake - on the table - at my wake. Modest Mouse
-
it's ctrl-shift-f over here in the US. but it messes up block /*..*/ comments -c
Smaller Animals Software, Inc. You're the icing - on the cake - on the table - at my wake. Modest Mouse
Chris Losinger wrote: it's ctrl-shift-f over here in the US It would be. ;) Chris Losinger wrote: but it messes up block /*..*/ comments I know, but I tend to use // for multiline comment blocks, or else use a seperate /* ... */ on each line. It is especially useful if you have multi-printed-page comments which contain code, as you don't get confused. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
-
Chris Losinger wrote: it's ctrl-shift-f over here in the US It would be. ;) Chris Losinger wrote: but it messes up block /*..*/ comments I know, but I tend to use // for multiline comment blocks, or else use a seperate /* ... */ on each line. It is especially useful if you have multi-printed-page comments which contain code, as you don't get confused. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
-
Yeah, I was expecting that sort of reply! I personally don't print my own code, but most of the companies I have worked for over the past years have asked for bound copies of all source code and project documentation for archival and maintenance purposes. Quite why the hell they can't archive a CDR is beyond me, but is it for me to say? I charge them for the resouces and the hours (as much as a day) it takes to print, sort and bind the various documents. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
-
Yeah, I was expecting that sort of reply! I personally don't print my own code, but most of the companies I have worked for over the past years have asked for bound copies of all source code and project documentation for archival and maintenance purposes. Quite why the hell they can't archive a CDR is beyond me, but is it for me to say? I charge them for the resouces and the hours (as much as a day) it takes to print, sort and bind the various documents. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
I was just kiddin. Really. I can understand printed and bound copies of documentation but I think printed copies of code is a bit useless. Personally, I haven't printed code or read printed code in quite some time. I can't exactly remember the last time actually. Anyway, I am glad to hear that you bill for the effort. On the subject of CDR, a colleague told me that he recently ran across some older CDRs he had made (at 1X speed) that are now unreadable and he tried them on several different drives. I always thought their lifetime was longer than mine but now I am not so sure. I would expect it to be longer than any magnetic media though.
-
I was just kiddin. Really. I can understand printed and bound copies of documentation but I think printed copies of code is a bit useless. Personally, I haven't printed code or read printed code in quite some time. I can't exactly remember the last time actually. Anyway, I am glad to hear that you bill for the effort. On the subject of CDR, a colleague told me that he recently ran across some older CDRs he had made (at 1X speed) that are now unreadable and he tried them on several different drives. I always thought their lifetime was longer than mine but now I am not so sure. I would expect it to be longer than any magnetic media though.
I thought CDR's only lasted 10yrs max cheers, Chris Maunder
-
I was just kiddin. Really. I can understand printed and bound copies of documentation but I think printed copies of code is a bit useless. Personally, I haven't printed code or read printed code in quite some time. I can't exactly remember the last time actually. Anyway, I am glad to hear that you bill for the effort. On the subject of CDR, a colleague told me that he recently ran across some older CDRs he had made (at 1X speed) that are now unreadable and he tried them on several different drives. I always thought their lifetime was longer than mine but now I am not so sure. I would expect it to be longer than any magnetic media though.
I still find that reading through printed code is a better way of reviewing code for obvious mistakes and tracking down elusive bugs. Michael :-)
-
Code that isn't lined up and is all over the place make my teeth itch. Just thought I'd share that with you all. cheers, Chris Maunder
Chris Maunder wrote: Code that isn't lined up and is all over the place make my teeth itch. Well, that certainly explains my current dental afflictions. Bought an ASP based shopping cart system for a baseline set of code that I then beat into submission (we're talking severe beatings here) for my record store site. Their stuff was generated / written with FrontPage, which completely trashes any semblance of formatting. After grinding my teeth for enough hours, I finally realized that the most productive thing to do was to reformat an entire file before I started modifications so I could read the !@#^&^$@#!! thing... Chistopher Duncan Author - The Career Programmer: Guerilla Tactics for an Imperfect World (Apress)
-
I still find that reading through printed code is a better way of reviewing code for obvious mistakes and tracking down elusive bugs. Michael :-)
True - I always keep my pack of highliters handy! ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …