Director Engineering , Red Ventures
Corporate policy restrictions got you down? Me too! I've been struggling to find a good reliable solution for local Slack, Github, or cloud development when Ngrok, the most commonly used tool for exposing services locally, is restricted by either local execution policy or via OpenDNS (or similar).
In all companies, large and small, there is no One app to rule them all. The reality is that there are often dozens, sometimes hundreds, of apps/services/tools/etc that we use to help ourselves, or to provide services to our clients. So how do you get all of your services and tools working in concert to meet your goals, objectives, and strategies?
I had a great time getting my yearly injection of the future as Microsoft see's it. The Azure, The Windows, The AI, and The .NET all got The Love. Azure even received the coveted day 1 keynote slot that typically belonged to Windows and Microsoft partners building apps, so from my perspective, we got right to the good stuff. So put your "~~augmented~~ mixed reality" headsets on , scale your serverless compute, and lets intelligently (and responsibly) Dock(er) with the the BUILD container.
Testing! Every developers favorite topic :). This post discusses how to work with the Azure Storage REST API, free of the SDK, in a test environment like Runscope or Postman.
Managing large teams well is no small task. Meeting regularly and taking hand written notes is a great start, but how can we do it all without adding additional time?
In this example, I'm using an Azure API app with Easy API's enabled (formerly mobile services...but better) and the preview version of the Azure Function app.
There was a lot of information to ingest at BUILD this year. Whether you're working with Xbox, Azure, Windows, or even containers on Linux, I would find it surprising if there wasn't at least one announcement that touched your development universe.
I've been along for the ride since the beginning of Slack, and even with it's flaws, I can finally see a future without email. So I've put together this list of tips on how to make the transition from email a little easier.
If you use Git with GitHub, the Hub wrapper utility by GitHub is a better cli option for working with your personal and org repositories.
I have a love hate with the Azure portals. Some days it's fast and lets me do exactly what I want, other days like today, I just want more control over how my stuff runs.
To continue my quest of converting from CVCS's to git, I figured I would do a short write up on my recent experience with converting from Subversion in a Windows environment.
First things first, it all starts with the package manager. It's the best, and I feel the only, way to maintain software on any machine you deal with.
After sifting through posts, docs, and Stack Overflow I was finally able to set this up using the same MSBuild process that I'm using for CD today.
Online persistent chat is awesome! Ever since I joined my first IRC chat room, I was hooked. It's slash commands, people leaving/joining/collaborating, and its always running `/me likes persistance`.
Fortunately for Azure developers, there are a lot of great ways to set up continuous delivery (CD) to Websites.
I love beer! And because of the love affair, I've had a kegerator in my home for well over a decade now. I still love and enjoy bottles of my favorite brews, but there is nothing like pouring yourself a beer right from your own stainless tap.
As we all know, exception handling is critical to every applications success. It's not a matter of if something goes wrong, its how and when. However, it's one thing to trap an exception and another to get that information into an actionable format.
Kudu is all around great tool if your using Azure Websites. It will not only build and deploy your code from git, but it also provides a lesser known web interface available on every azure website.
I had a great time at BUILD this year. As far as major announcements go, this had to be one of the biggest in recent memory.
As a long time TFS user, and VSS user before that, what is most commonly referred to as centralized version control (CVCS) was all I knew.
