Repeat after me, “Avoid
async void!” (Now say that ten times fast!) Ha ha ha. You sound funny.
For most of my life, I was a man without a drink.Read More
I love to communicate through the written word because it offers me a chance to really consider what I say, and then rewrite it, and then rewrite it again. And in the end, I still don’t communicate as clearly and eloquently as I would like.Read More
If you run a company, stop increasing pay based on performance reviews. No, I’m not taking advantage of all that newly legal weed in my state (Washington). I know this challenges a belief as old as business itself. It challenges something that seems so totally obvious that you’re still not convinced I’m not smoking something. But hear me out.Read More
Recently I wrote what many consider to be the most important Visual Studio Extension ever shipped - Encourage for Visual Studio. It was my humble attempt to make a small corner of the world brighter with little encouragements as folks work in Visual Studio. You can get it via the Visual Studio Extension Manager.Read More
When Ballmer famously said, “Linux is a cancer that attaches itself in an intellectual property sense to everything it touches,” it was fair to characterize Microsoft’s approach to open source as hostile. But over time, forces within Microsoft pushed to change this attitude. Many groups inside of Microsoft continue to see the customer and business value in fostering, rather than fighting, OSS.Read More
Software collaboration goes beyond just working on the code. In addition to writing a lot of code, software involves writing a lot of words. Prose shows up in documentation, tutorials, blog posts, and so on.Read More
The screaming was unexpected.Read More
Some endpoints in the GitHub API require authorization to access private details. For example, if you want to get all of a user’s repositories, you’ll need to authenticate to see private repositories.Read More
In a recent version of GitHub for Windows, we made a quiet change that had a subtle effect you might have noticed. We changed the default merge strategy for
*.csproj and similar files. If you make changes to a
.csproj file in a branch and then merge it to another branch, you’ll probably run into more merge conflicts now than before.