When I was first promoted to management, back at Mindcraft Software, I thought to myself, "Finally! Now we can start doing this project right."
« July 2009 | Main | October 2009 »
When I was first promoted to management, back at Mindcraft Software, I thought to myself, "Finally! Now we can start doing this project right."
Posted at 10:27 AM in Manager In A Strange Land | Permalink | Comments (0)
| |
|
When Wizards of the Coast had moved onto D&D 3rd edition, my friends were still playing second, still talking "THAC0", still 'open-source, why should I care?'
Posted at 02:47 PM | Permalink | Comments (2)
| |
|
That's what was missing.
Posted at 05:01 PM | Permalink | Comments (0)
| |
|
I think this is my least favorite kind of bug to track down. Even worse than a dangling pointer write - at least with that, you can use hardware debugging and catch it in the act.
Posted at 09:26 AM | Permalink | Comments (2)
| |
|
I only recently discovered the "override" keyword in Visual C++. It's clearly a Good Thing - too bad other compilers don't support it, but you can always #define it out for other platforms.
Posted at 05:28 PM | Permalink | Comments (0)
| |
|
Some time ago I believe I said I'd give certain parts of my anatomy for some decent C++ refactoring tools.
Posted at 04:41 PM | Permalink | Comments (5)
| |
|
I've been ranting about good code a lot lately, but something I've discovered is that a few of the most succesful companies out there have crappy codebases. This galls me a bit - it doesn't seem fair! But when I think about it, it makes sense.
Posted at 10:56 AM | Permalink | Comments (4)
| |
|
Posted at 11:30 PM | Permalink | Comments (2)
| |
|
How do you order your #includes at the top of a cpp file? You probably don't care, because it mostly doesn't matter. But, for whatever reason, I care. First the precompiled header header, of course. Then a linefeed. Then I like putting the matching .h file first, because if that .h file needs any other .h files, we'll immediately find out and can include them within that .h file.
Then another linefeed. Then the "" headers. Our headers. In alphabetical order. How anal is that? I guess I like structure. But it does have one little advantage, that you won't accidentally include the same file twice. Not that that matters, either, but it does look a little bad if someone sees it. Then the standard lib <> includes.
Just thought I'd share. This isn't something I ask coders on my projects to do, but when I'm working with their files, I sometimes go in and rearrange their headers to suit my whims.
Posted at 02:48 PM in Stupid Programming Tricks | Permalink | Comments (9)
| |
|
Posted at 10:54 AM in Stupid Programming Tricks | Permalink | Comments (3)
| |
|
Recent Comments