Ken Muse

With programming, things aren’t always what they seem. In fact, sometimes more is less. More specifically, sometimes we get better performance by doing the opposite of what we’ve learned is right. Let’s explore an example and how it applies to cloud-scale systems and big data.

Continuing with last week’s post, we’re going to explore how to take interactive staging (line staging) one step further in Git. Sometimes you need complete control over the process of selecting which lines to commit. Perhaps you need fine control over what code is being committed. Perhaps you just want to organize what’s in the commit. Today, we continue the exploration of this feature by learning how to edit what we’re staging.

The latest preview of Visual Studio 2022 has introduced interactive staging and the ability to stage and commit a subset of a file. Today we’ll examine how you can use the Git command line to choose to commit parts of files.

Several of the more powerful features of Git are only exposed from the command-line interface. However, some of these features rely on being able to invoke a text editor. In today’s post, we walk through how to associate a text editor with Git.

In last weeks post, I mentioned that there are ways to modernize Function apps. In truth, most App Services support an improved model for deploying your code — the deployment package. Learn to use ‘Run From Package’ to improve your Azure App Service deployments.

Sometimes continuous deployment of the code is just not enough to update your Azure Function. The symptoms are simple enough — triggers stop working or the Function stops scaling. In these cases, you need to make Azure aware of the changes. You may need to synchronize.

Did you know that you can have your favorite environment configurations follow you wherever you go, including into Development Containers and Codespaces? All of your environments can reflect your personal preferences through the power of a dotfiles Git repository.

Bicep continues to make it easier to create ARM templates … until you have a bad service schema. Here’s how to resolve a Template Not Found error with Bicep and APIM templates.

Creating Tags for APIM using infrastructure-as-code with Bicep should be simple. So why do we get a “Name should not be empty” error? More importantly, let’s discuss how to fix it.

If you’re using Visual Studio Code and Dev Containers without working in the right filesystem, you’re missing out on a lot of performance! Learn the right place to keep your files!