Welcome to MSDN Blogs Sign in | Join | Help

March 2005 - Posts

One of the internal software engineering traditions here at Microsoft is the "BUGBUG". Bugbug's are annotations that are added to the source code when the developer writing the code isn't sure if the code they're writing is "correct", or if there's some Read More...
The wired network in my building's being unusually flakey so I'm posting this from my laptop, sorry for the brevety.. Slashdot had a front page story today about an article be Adrian Wong posted in his Rojak Pot: " Virtual Memory Optimization Guide ". Read More...
I was surfing the web the other day and ran into someone linking to this article by Jack Lanier from Edmunds (the automotive newsletter people). The article's entitled "Friends Don't Let Friends Modify Cars". From the article: Today, it's difficult to Read More...
Somehow (and I'm not sure how I managed to do this), I missed the fact that last week was the one year anniversary of this blog! Since I'm usually pretty obsessive about dates, I can't really explain it, but it is. Last year on March 15th, this blog went Read More...
Work's heading up right now, so this one will be briefer than expected. Windows has its own idea of threading models. In general, each window on the system is owned by a thread, and that thread is responsible for ensuring that the thread is constantly Read More...
As I mentioned the other day , I can't quite let go of the concurrency bug, so the 2nd of my 3 add-on posts to the concurrency series. One thing I didn't talk about explicitly in the original concurrency series is the Win32 API set. I implicated the concurrency Read More...
For some reason, I can't seem to let this concurrency thing go, I keep on thinking of more and more relevant topics - there are a lot of issues surrounding concurrency. I realized today that my concurrency series didn't talk at all about libraries and Read More...
This is sort-of a follow-up for the article " Keeping kids safe on the internet " that I wrote a while ago. First off, I want to point to the excellent article " What you don't know can hurt kids ". Based on that article, my comments were hopelessly naive. Read More...
Yesterday's article was a bit of a trick question, but was a real world example. Our group encountered this in some code we were testing last week (in some pre-production code - it was not part of any product). Somewhat surprisingly, it turns out that Read More...
I've seen this twice so far this morning, and it'll get a lot more play RSN, but I'm going to violate my normal "don't repeat a meme" policy because this is just too darned cool... Several places have pointed out this site which gives detailed instructions Read More...
Ok, time for another "what's wrong with this code". This one's trivial from a code standpoint, but it's tricky... // ---------------------------------------------------------------------- // Function: // CThing1::OnSomethingHappening() // // Description: Read More...
I'm listening to NPR right now (getting ready for work/school) and I realized they had an article on Knuth. Very cool, and worth listening. And he's just about done with Volume 4! Read More...
Busy weekend, I'm about to go out-of-town to a seminar with Daniel, and Sharron's got another riding competition (the first one I won't be able to see :(). So a quick note instead of an article I just noticed (via Rick Schaut's blog ) that Jason Matusow Read More...
Today I want to wrap up my concurrency series (finally). There are some more topics I'll be covering in the future (like the debugging concurrency issues I talked about yesterday :)), but I think I've said a reasonable amount about the issue (and frankly, Read More...
Ok, the light's at the end of the tunnel. I couldn't figure out where to slot this in, so it got stuck at the end... Someone (I'm forgetting who) asked about what happens when someone's producing data to be handed to a pool of threads. The simplest example Read More...
I think I've got two more articles in this series left, I didn't really intend for this to overwhelm my blog for an entire month, but it sort-of got out of hand - I'd originally planned for a total of 6 topics and here I am on the lucky 13th. Anyway, Read More...
Last time, I mentioned that even when you get everything right, you can STILL have scalability issues... To explain what's going on, a digression. One of the major features of Exchange 2000 was the ability for the store to access multiple databases (before, Read More...
So you're writing a server. You've done your research, and you've designed your system to be as scalable as you possibly can. All your linked lists are interlocked lists, you're app uses only one thread per CPU core, you're using fibers to manage your Read More...
Well, the concurrency series is finally running down (phew, it's a lot longer than I expected it to be)... Today's article is about determining how you know if you've got a scalability problem. First, a general principle: All non trivial, long lived applications Read More...
Sorry, I just noticed that this didn't get posted yesterday - I don't know what happened, but... As I mentioned the other day , Win32 provides a number of tools for writing scalable applications. Today I want to catalog some of them. Remember, that the Read More...
 
Page view tracker