Office Move 2006, Part 2

I finally got around to setting up and re-arranging my office after the completion of the Office Move. Like Wade, I spend the extra time and effort to disassemble all wires of my computers prior to moving and reassemble them myself after the move. My main reasons for doing this?

  1. I want to be responsible for how my machines are wired. One of the worst feelings is to have a kernel debugger misconfigured following a move and waste time figuring out what happened in the middle of a debugging session
  2. I re-optimize my wiring depending on the location of the power/networking jacks as well as machine placement. Usually, I decide on a machine layout after seeing them in the new office, so I will likely undo any existing wiring efforts done by the movers... might as well do it myself

In other words, I am just picky when it comes to my machines and how they are arranged. 🙂

Well, this time I remembered to take pictures of my new office after I finished wiring everything up.

As you can see, I do not like clutter and highly value clean, contiguous space, so I basically stashed all my computers into one corner of the office so that I can have an entire wall of just whiteboards.

And another nice thing with this particular office's layout is that I can stash my old move boxes (which accumulate every time I move offices) into a recessed area so that I do not need to unpack them. Out of sight, out of mind. 🙂

Yes, there is a little stuffed radioactive-green frog lounging across the top of my LCDs.



Comments (13)

  1. Thanks for the pic 😉 How big is your office, btw? I’m still relegated to a cubicle, so anything beats what I’ve got.

    Incidentally…what do you have running on your system in that pic?

    – Mark

  2. David.Wang says:

    Mark – Hmm, I have never measured directly. I just counted the number of ceiling tiles and I see 4.5 x 6.25 tiles, which probably is in the neighborhood of 9’x12.5′.

    I’m running on pretty dated hardware – P4 2.6Ghz, 512MB, dual Dell 2001FP DVI on FX5200. But, it still gives me enough performance and screen real estate to Remote Desktop to test machines and do my tasks. I’m pretty “low maintenance” when it comes to HW requirements at the office…

    I’ll play around with the pictures and figure out how to get them integrated into the blog entry text stream and not as file attachments…


  3. Funny…I actually meant to ask, what apps are running as shown in the pic? 🙂

    Don’t feel bad – my hardware is more dated than yours – Athlon 1.0GHz, 1024MB, etc…no Vista for me I guess.

    – Mark

  4. David.Wang says:

    Mark – Oh, all the usual apps that I had listed here:

    Community Server, NT Command Shell, Remote Desktop, Textpad, Outlook, Outlook Express.


  5. What, no Visual Studio?! 😉

  6. David.Wang says:

    Mark – hehe… Visual Studio is merely what we think *you* need to develop on Windows. "Real" development/debugging still happens with notepad and ntsd/windbg. 😉

    Actually, most of the IIS team does not use Visual Studio at all… developers code with a variety of editors including Emacs, vi, gvim, VC6, and while Windows builds with compilers from C++, the build system remains customized.


  7. no kidding…well, at the risk of sounding overly judgmental…doesn’t this continue to feed the negative criticism that microsofties don’t "dogfood" their own products? i think it’s important for those of you on the iis team to experience developing against iis the way folks like myself do (using visual studio) to help improve not only our development experience, but to explore the potential for improving the platform as a whole. just stop me when this thread becomes tiresome…lol 😉

  8. David.Wang says:

    Mark – Hmm… I do no not agree with your assessment that Microsoft does not dogfood their own products. I think Microsoft does it more than most.

    The difference here is that we are NOT developing against IIS – we are developing IIS itself. Visual Studio is great to develop against IIS/Windows, but it is not necessarily great to develop IIS/Windows itself…

    When it makes sense, dogfooding is heavily utilized. For example, ASP.Net team is pretty much Visual Studio bound and use it to develop against IIS all the time.

    And IIS7 managed modules will continue to leverage the ASP.Net development experience.

    I agree that for ASP and ISAPI, this level of attention was never paid. As a "platform" team, we tend to make changes that make technological sense and not constrain ourselves to "But what would the Visual Studio user experience be like". For example, application pools would never have come about if we worried about the Visual Studio user experience, but would you rather have application pools or a good Visual Studio user experience?


  9. LoL ! notepad is good. it is slim and less complicated 🙂  too bad now! I don’t have any cubicle, ‘they’ took mine away due to all the traveling, now I’m working from home… kekekeee..

    I only have beers on my desk, you so nice! was that wine or champagne ?

  10. David.Wang says:

    Bernard – hehe… not having to drive away to "work" is a nice thing… at times, I just work in front of the TV in my living room. It is not unlike university days. 😉

    It’s a bottle of wine – Chateau St Michelle 2004 Muscat Canelli. I like whites on the slightly sweeter and fruitier side of things.


  11. David Wang says:

    Back in this blog entry, I mused about how nice it would be to have more bloggers from the IIS product…

  12. Curious says:

    Just wondering if you have any textpad tips or customizations you could share.

  13. David.Wang says:

    Curious – Well, Textpad is pretty darn customizable, so I suggest making good use of it. Things that I am picky about include:
    – Editor window size and position
    – Open documents (Textpad Workspace)
    – Syntax classification files for languages I use
    – Syntax coloring scheme
    – Hotkey bindings

    What is important to you, as well as your needs, can definitely vary from me, so feel free to experiment! 🙂

    Besides, all Textpad settings can be captured and restored via a Registry key, so I can easily invest in settings and know I can move it from machine to machine.


Skip to main content