Luke Rogers

If you are at a point in your career where you want to make a change (new role/team/company/etc.), you need to take some steps to prepare your team and your replacement for success. Side note: I am assuming you don't want to burn any bridges. If that is your goal, this post isn't for you. If you move within the company and neglect to make the transition easy, you will likely be asked to cover your old role and will have a hard time succeeding in your new role.

I’ve been working from home for around 7 years now and I vacillate between thinking I could never do it any other way and wanting to work in an office again. I don’t think anyone will argue that you can accomplish tasks more effectively when you can focus. Working from home allows you to avoid a lot of the “noise” of an office; especially in an open floor plan or cube farm.

If you want to jump straight to the repo, go to https://github.com/lukerogers/swashbuckle-nginx. After cloning the repo you can just run docker-compose up then open http://localhost:5100/api and you should see the swagger UI. If you're still reading this, thanks for sticking around. Back to the task at hand! Assumptions: If you got here looking for running Swashbuckle behind NGINX, I'm going to assume you are familiar with my setup. ASP.NET Core WebAPI service running with Swashbuckle to document the API and test it.

As I get started on my Docker journey I wanted to start with a simple application to get my feet wet. I chose the classic Example Voting App as it covered a few services, showed Docker Compose and had Kubernetes deployments already in place. When I tried to spin it up I received the following error: Error starting userland proxy: mkdir /port/tcp:0.0.0.0:32787:tcp:172.22.0.2:6379: input/output error Searching this specific issue leads in various directions, but then I saw a comment about having issues while on the corporate VPN, namely Cisco AnyConnect.

In my effort to make my application as fast as possible, I needed to compress the JSON being returned by my application to speed up the download time. It is quite easy to turn on compression for IIS. You 100% should do it for static content (HTML, CSS, JavaScript) and generally should for dynamic content as well. Those two are simple changes in the UI or via Desired State Configuration (DSC).

Recently I was working on an application that utilizes Azure Service Fabric and I was doing load testing before going live and I wasn't getting the performance I was expecting. Since this application can only run under the service fabric runtime, profiling is a big challenge. Tools like ANTS Performance Profiler or dotTrace can't plug in since service fabric is hiding the application so I needed to turn to a regular C# StopWatch to track down the problem.