Low Level Considerations for VS of the Future (an old memo)

I wrote this a long time ago.  It’s very interesting to me how applicable this is today.  And how it is not very specific to Visual Studio at all… Low Level Considerations for VS of the FutureRico Mariani, Sept 12/2007 Introduction I’ve been giving much thought to what enabling steps we have to take to…

2

A systematic approach to finding performance regressions using overweight analysis

I have been using this approach to do systematic analysis of performance regressions for several years now. I came up with it while looking at some tricky problems in Internet Explorer about three years ago and it’s served me well since then. The idea is pretty a simple one but it gives surprisingly good results…

7

A Personal History of Microcomputing (Part 3)

[All the parts in this history] Recap I’m only up to 1980, that’s pretty amazing considering what’s happened in the story so far.  The Altair 8800 made its big splash in the January edition of Popular Electronics (which naturally came out in December).  Now it’s 1980, only a half-decade later, and we’ve gone from that…

2

Use Symbol Filtering to get symbols you care about from your server instead of getting the kitchen sink

One of the most annoying things about working with performance traces is that they include information about everything in the system.  That’s also one of the great things. However, most of the time, for most problems, there are very few things you are specifically looking for.  Like in my case I’m looking at IE problems and…

9

Anybody want a peanut?

I wrote a message much like the below yesterday and I kept cracking up once I had started.  And nobody around me had the relevant context to understand why I thought it was so funny.  I’ve removed all the specifics and left the core.  I know some of you will get it 🙂 We have…

12

Example of a transform for unit testing something tricky

There were some requests for an example of my unit testing strategy so made up this fragment and included some things that would make your testing annoying. This is the initial fragment.  Note that it uses annoying global methods that complicate testing as well as global state and system calls that have challenging failure conditions. HANDLE hMutex…

2

How to make ANY code in ANY system unit-test-friendly

[I added this example in a later post] There are lots of pieces of code that are embedded in places that make it very hard to test.  Sometimes these bits are essential to the correct operation of your program and could have complex state machines, timeout conditions, error modes, and who knows what else.  However,…

13

A Personal History of Microcomputing (Part 2)

[All the parts in this history] I could spend a long time writing about programming the PET and its various entry points, and I’m likely going to spend disproportionate time on the CBM family of computers because that’s what I know, but I think it’s important to look at other aspects of microcomputers as well and…

0

A Personal History of Microcomputing (Part 1)

[All the parts in this history] I started writing this several years ago, never finished it…  stumbled across it just now and I thought maybe if I post this I’d be motivated to write more. This is of course just my perspective and it’s probably wrong in places, but it is my perspective.  So there…

4

My Universal Performance Problem Advice

I get asked for recommendations a lot.  Most of the time I have little to no data when asked to perform this sort of divination.  But as it turns out I have this ready-to-go universal advice that works for me, so I’m able to give the same recommendation all the time even with no data! …

2