Remote Work
I'm a huge fan of reverse proxy tunnels. Accessing private networks, like your home network or homelab, in this way is generally considered more secure than using a VPN or exposing ports to the public internet on your router. This will get you up and running in 5 minutes; anyone can do it.
Gaming
I'm a little older, and my reaction time is a little slower, but I can claw some of that back with a bit of button mapping and retraining. Casual doesn't have to mean settling for the stock option.
Homelab
I'm continuing to discover new and exciting ways to access my Homelab and home network when I'm away or using a device I don't personally manage...in this case, securely, without a VPN or WARP client
Homelab
Zero Trust is a platform for small businesses and enterprises to offer secure access to their networks and applications...which sounds perfect for my five-user household 🙂; oh, and it's Free!
Cloudflare
It's to set up your secure tunnels directly to Cloudflare on bare metal or within virtual machines. Why stop there? Let’s make them easier to manage and highly available by containerizing multiple tunnels across several physical devices
Homelab
This guide will walk you through securely exposing Plex, your NAS, and other services while away from home. All while avoiding UPnP and traditional port forwarding, which is typically less secure and more complex with only one dynamic IP address.
Homelab
Forget the Adblock browser extension. It's time to level up your home network to block unwanted ads and trackers across all of your devices. Pi-hole is an open-source project that has been around for a while and makes this dead simple.
Remote Work
In my opinion, Remote is here to stay. Companies that have embraced this will likely lead the pack to the most desirable places to work and are already innovating and transforming shared workspaces, embracing frequent travel, and offering home office perks.
Docker
Corporate policy restrictions got you down? Me too! I've struggled to find a reliable solution for local Slack, Github, or cloud development when Ngrok, the most commonly used tool for exposing services locally, is restricted by either a local execution policy or via OpenDNS (or similar)
Engineer, Technologist, and Gamer.
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.
I had a great time getting my yearly injection of the future as Microsoft sees it. The Azure, The Windows, The AI, and The .NET all got The Love. Azure even received the coveted day one keynote slot, so from my perspective, we got right to the good stuff.
Testing! Every developer's favorite topic :). For me, if I can save time through automation, then I'm interested. Automated testing for a developer typically starts with unit tests, which, even if you don't subscribe to TDD, you've written at least one of them to see what all the fuss was about.
Managing large teams well is no small task. Meeting regularly and taking handwritten 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 APIs enabled (formerly mobile services...but better) and the preview version of the Azure Function app.
I've been along for the ride since the beginning of Slack, and even with its flaws, I can finally see a future without email.  So I've put together this list of tips on making the transition away from email a little easier.
There was a lot of information to ingest at BUILD this year. Whether you're working with Xbox, Azure, Windows, or even Linux containers, I would find it surprising that there wasn't at least one announcement that touched your development universe.
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 relationship with the Azure portals. Some days it's fast and lets me do exactly what I want; other days, like today, I want more control over how my stuff runs.
To continue my quest of converting from CVCS 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 finally set this up using the same MSBuild process I'm using for Continuous Deployment today.
