As a developer, it is always important to keep in mind one thing – never trust the client. Ever. The client is neither a completely secure entrypoint nor the source of truth moving upstream to the service.
NOTE: This issue has already been addressed and the fix is live. Shoutout to Kyle Rankin for being on top of things and responding to my email.
As a Program Manager, part of my job is to write technical specification documents. Our team recently switched to using our very own system (yes, we use the docs.microsoft.com infrastructure internally too) to write technical specs – content is on GitHub and Markdown-based. As part of that came the question – how do we aggregate comments when people review them?
If you are following the news around our new technical documentation experience, you probably know that last week we revamped our managed reference experience and launched the .NET API Browser. In today’s post, I thought I would go into the nitty-gritty of the process and talk about how exactly we generate reference documentation for .NET Framework and related managed SDKs.
With the release of Windows 10, all photos are now opened by default with the help of the Photos app. I like the Photos app, but I also enjoy the UI of the traditional Windows Photo Viewer.