Building a custom VS Code extension can open the door for innovation. Extensions can become even more powerful when you use them to create a better interface. Today we explore how to incorporate custom UIs into your extension using Webviews.

Combining Visual Studio Code with Hugo has given me a great workflow for my blog. To make it even better, I need to modify part of the editor’s behavior. I need a custom VS Code extension.

I’ve mentioned a few times that I use Visual Studio Code and Hugo for my blogging. I’ve also discussed some of the the ways I make it faster and easier to create my posts. Learn how I make my VS Code experience faster and easier by using tasks.

Did you know that dev containers can have their own private Visual Studio Code extensions? By understanding some of the life cycle of the container, it’s possible to create and use extensions that are designed to support a specific dev container or Codespaces environment.

Continuing the topics from my last post, this week I want to offer a deep dive into the lifecycle of a Jest TestEnvironment by exposing the events that are raised when tests are run. I’ll also explore some of the details that are included with each event.

I needed a way to implement integration tests that would allow me to ensure that I could clean up the emulators I was using after each test cycle. Jest Test Environments provided a powerful way to do this, and TypeScript makes it easy to do (aside from a few quirks).

GitHub Advanced Security (GHAS) helps teams to shift left and secure their development practices. But what do you do when its process its processes and practices doesn’t quite fit your team’s approach? In this post, we’ll look at how to use GitHub Probot to implement your own process in a GitHub-native way.

Developers usually want to be able to directly connect to a system, start the debugger, and step their way through the code. Being able to log into a machine and debug is the way most of us learn to troubleshoot and fix issues. But what if you can’t do that? And what if I told you there’s a better way to debug?

In the last post, we started to explore how to create a Decoder and its containers in Swift. Now, we need to have a good way to read the data and provide it back to the decoder so that it can create the type instances. Today’s post will introduce pattern for reading binary data and converting it to Swift types. We’ll then discuss how to integrate it with the Decoder.

If we’re going to build a Bluetooth application, we need to be able to decode the data we receive. Swift has a native way to convert encoded data into types – the Decoder protocol. In today’s post, we’ll explore the basics of implementing a custom binary data decoder in Swift. We’ll also look at the different types of “containers” and how they work.