See you at Build 2018 next week


I'll be at the Build conference next week. Here's my schedule so far:

  • Monday
    • Attending Dona Sarkar (and some other guy)'s talk with the great title slide at 4:00pm.
    • After that, I'll be at the Sets booth at the Expo until closing.
  • Tuesday
  • Wednesday
    • Co-presenting a talk on Sets at 10:15am.
    • After grabbing some lunch, I'll be down at the Sets booth at the Expo.
    • And then joining the panel of co-presenters for the Amplify Your Awesome talk at 4:30pm.

For times not listed above, I'll be wandering around, or maybe hiding in the Speaker Prep room panicking. If you want to find me, you can head to the Sets booth, and if I'm not there, they can call me.

Comments (14)
  1. Microsoft should really have a //Patch/ conference instead. Or //Bug Fix/ one. I mean what’s the point of building something that I’d uninstall in frustration?

    You know, before Windows 10, it never occurred to me that Windows can have bugs too.

    1. Ray Koopa says:

      Well wasn’t that a rather //naive/ thought.

      1. No. Because it was not a thought in the first place.

        1. xcomcmdr says:

          Yes, you don’t think. We can attest that. Thank you.

          No, if you could do it in the future, that would be splendid.

          For example, you can start by thinking before commenting about the following :
          – Is my comment relevant to the topic at hand ?
          – Does it bring any sort of value to the discussion ?

          Thank you in advance, and take care !

    2. Antonio Rodríguez says:

      Windows has had bugs before Windows 10 (the music metadata destroying bug of Windows 7 beta 1 comes to mind), and will continue to have bugs after Windows 10. As every piece of code more than 10 lines long. But, what is your point here? Your rant is not on topic with this post, not with the blog’s usual topics.

      1. When you put “beta 1” in there, you’re kinda defeating your own argument. I am saying //Build/ (which is the topic here) is getting irrelevant, when incentives for building is getting hurt. “Rant” is a very unfriendly replacement for “I respectfully disagree because …”.

        1. xcomcmdr says:

          Every installation of Windows 7 SP1 has the “Windows Update does not work and takes all the memory” bug.

          Yes, MS products, as they are software, have bugs. Just like all software. Your comment is off-topic and childish.

    3. Erik F says:

      Obviously Microsoft made sure to have as one of their goals “Make sure that Fleet Command is frustrated with Windows 10,” just like one of the goals of Windows 95 was “Make sure Norman Diamond’s SCSI hard drive doesn’t work.” Are there bugs in Windows? Absolutely, just like every other complex piece of software. I’m not sure why you’re amazed that this is news, however.

    4. Cesar says:

      The name “//Build/” looks like a server name, probably the build server. The same build server would also be used for patches and bug fixes (they have to be built somewhere). Also, AFAIK server names can’t contain spaces.

      1. Ray Koopa says:

        I was always thinking about the server name thing. But then it should’ve been \\build\. But that was too obvious probably. Or not stylish enough. Now the slashes are gone and will be forgotten soon anyway.

  2. skSdnW says:

    Will we be reading about win32 Sets bugs in 3rd-party apps here in about 10 years? Is there anything 3rd-party apps can/should [not] be doing? I’m just a normal insider and not on skip ahead so I have not played around with them yet.

  3. Phil says:

    On an unrelated note: An old, old blog entry of yours speculated on why the close button was in the right hand corner (https://blogs.msdn.microsoft.com/oldnewthing/20120522-00/?p=7563). I found a more authoritative answer at https://medium.com/re-form/x-to-close-417936dfc0dc, which quotes Windows 95 team member Daniel Oran as saying that the idea was borrowed from NeXTSTEP (!)

    PS: I also serve as an unofficial historian for my company, drop me a note by email if you’d like to compare notes.

    1. Alex Cohn says:

      To be fair, the Next theory was discussed in the comments of the ’12 post.

    2. Gee Law says:

      The two don’t conflict. It could be that NeXT reasoned their decision by Fitt’s law, and Microsoft chose that because of Fitt’s law.

Comments are closed.

Skip to main content