A Kickstarter for features: It’s a Better kind of User Voice

For decades, I’ve watched users and developers long for capabilities in Windows and .NET that never happen. Sites like Connect and User Voice collect our ideas and votes yet backlogs rarely react.

I believe product teams often chase the next big feature, forcing themselves to ignore small, love-creating improvements or tweaks that would build tireless loyalty from their user base.

For this reason, I would like to propose a new idea. A way to solicit, not feedback, but ideas from a user or developer community in a way that gets results and creates wonder. 

Developer Evangelism’s Obvious Secret

Hi. So, here’s another entry from my notes as an Evangelist. So many snippets I wrote to myself, translated here to blog articles helping, I hope, anyone finding themselves where I was. This one is the role of empathy. Perhaps it is not as obvious as you assume?
For the sake of argument, and I think that’s a fine reason, let’s consider Developer Evangelist, Technical Evangelist, Developer Advocate, and any other variation of a Developer Relations title to be the same. For the most part, they are. For me, here, I will use Developer Evangelist because that’s the title I employed for just under a decade at Microsoft. And, I like it.

Three Reasons for Developer Evangelists to Engage

I would like to talk about the reasons for a Developer Evangelist to engage an audience. We already understand the three ways we can engage: online, personal and onstage.

As a reminder, online engagement has the greatest reach but the least impact, personal engagement has the greatest impact but the least reach, and onstage engagement is a combination of the two with varying results depending on skill, style, and approach.

But when as you prepare your talk, ask yourself why: why are you engaging in the first place. As you are driving to a conference or meetup ask yourself why: why are you engaging in the first place? I would assert there are three reasons for Developer Evangelism engagement.

Some goals for 2019

Hi. Today is the first day of 2019; I have a few goals for the coming year I will codify here so I can look back and see how I did. This is not a list for you, it’s for me. That said, I am satisfied for my list to influence your list, should it.

I have some big things afoot in my life and should waters stay smooth, these goals are both attainable and what I want. I should also point out this year’s goals resemble last year’s goals. I am certainly a creature of habit. Some of last year’s goals were reached. Some are carrying over. Some, however, always make my list in one form or another.

The three pillars of Technical Evangelism

Terms like evangelism are funny. Etymogically, evangelism is about converting and teaching. Where most of us are used to hearing it in the context of theology, technical evangelism is about teaching and converting in the context of technology, most usually software development.

I am a Microsoft Evangelist. It’s my real title, and I sometimes must show people my card before they believe me. As a Microsoft Evangelist I am converting developers to Microsoft Technologies. I also teach, of course, but it is a fundamental part of evangelism that teaching, though important, is secondary.

Custom UWP-XAML attached properties

Look, this article is for me. I keep forgetting the basics of XAML attached properties & some advanced syntax. If this helps you, too, great. 

As the author of Template 10 (the best UWP framework) I keep on my UWP toes with XAML & WinRT. I may not be a XAML Jedi, but I’m on the path. You’d think after writing about this in my Navigation View article in MSDN Magazine article last month I would have it all locked in. But, I’m the type of guy who forgets things. Even stuff I mastered just last month. So, here goes.

Containing class

The only requirement for an attached property is that its containing class derive from DependecyObject. The class cannot be static.

A personal review of some Star Trek swag I have lying around.

I have a few Star Trek things sitting on my desk, in drawers, or around the house. This isn’t really a review as much as it is an excuse for me to talk about them. This is important since the first episode of Star Trek: Discovery is only 3 days away and I am getting anxious about the whole thing. Don’t think of this as a buyer’s guide as much as me, dreaming up an excuse to talk about Star Trek in anticipation of the new show.

Cardinal XAML: a reflection

In 2014, at the VS Live in Chicago, Ben Dewey, a Microsoft MVP for Windows Client at the time, presented the session: XAML Anti-patterns. Not to be confused with Markus Egger’s excellent series with the same name in Code Magazine (also in 2014); Ben’s session had the playful subtext: The Seven Deadly Sins of XAML Development.

Between the two authors, they saw a regular set of common developer practices that harmed the efficiency and maintainability of XAML applications. In this article, I wanted to iterate those insights, consider the actuality of them, and review if they remain relevant to modern developers using newer, evolved XAML technologies and tooling.

What is a developer evangelist?

Much like asking what is the right way to develop software there are as many answers to that questions as there are people. But, developer evangelism or product evangelism has become a staple of companies wanting to reach a specific demographic in a particularly noisy marketplace. They speak, they listen, they code, they help, they advocate: but, what are they, really?

Login to your UWP with your MSA

Here’s the idea, you want your UWP user to login with their MSA so you can get their information, access OneDrive, Outlook, Office, Rome devices or just their profile photo and name. Whatever the reason, it’s more simple than you think.

Please note: the Live SDK we used to use for this has been deprecated and now we use Microsoft Graph for just about everything around authentication & access.

Here are your four easy steps to follow:

1. Register your app @ http://apps.dev.microsoft.com
2. Add your ClientID & ReturnURL to app.xaml Resources
3. Copy AuthenticationHelper.cs
4. Nuget packages
1. PM> Install-Package Microsoft.Graph
2. PM> Install-Package Microsoft.Identity.Client –pre