Author: Tom (Page 13 of 427)

Visual Studio Code Insiders: Sharing Extensions, Settings, and Keybindings

June 16, 2023 / Tom

Since there are a few extensions I’ve wanted to try out that aren’t available for Visual Studio Code’s stable builds, I’ve been using Visual Studio Code Insiders for the last few weeks.

The main difference is that this version is a daily release versus the standard monthly release and certain plugins, like GitHub Copilot Chat, requires the daily builds for it to run.

Here’s the thing, though: If you have settings you want to preserve across installations and Settings Sync doesn’t do the trick (I had hit or miss success with it across the two editions of the IDE), then here’s a simple trick for symbolically linking extensions, settings, and keybindings across editions.

Don’t Let Your Devices Tell You What to Do

June 14, 2023 / Tom

From How to Stare at Your Phone Without Losing Your Soul:

There are better parameters to evaluate quality, not quantity, of the time spent staring at your screens:

Does this app do its job and then politely step aside?

Does it linger in your brain like an awkward party guest at 2:30 A.M. after everyone else already left?

Did I summon this app, or did it summon me via notifications?

Emphasis mine.

One of the best things I’ve done since my “digital detox” (see here and here) at the beginning of last year was to turn off only notifications that weren’t urgent. Of course, what’s considered urgent for me isn’t going to be what’s urgent for you.

Don’t Forget: Remember to Build Tools

June 13, 2023 / Tom

As programmers, we’re used to leveraging all kinds of tools that help us to do our jobs be it something such as a debugger to something that helps us standardize our code to something that helps us to deploy our code to whatever platform we’re releasing our product.

And there seems to be a pattern that emerges for many of us as we work through our career:

We often try to write everything we can for ourselves (we have the time, energy, and desire to do so).
We start leveraging tools that helps us to achieve our primary goal (we have the know-how to use pre-existing, high quality utilities that help us to write better code or work with a larger project).
We develop a work flow for working in our niche and outsourcing all of the things that can be automated to third-party tools (we know what we need to focus on and leave the rest to other tools).

But do these tools that are part of our workflow always help us get our work done on a small scale? In other words, why don’t we remember to build tools for ourselves to use?

Effortless Documentation with Modern Tools

June 12, 2023 / Tom

This is a long article on The Surprising Power of Documentation and I think it’s worth a read, but it’s also geared toward implementing a documentation-first mindset in an organization.

This isn’t something I’m concerned about focusing on in this post but there are a few points the articles are makes and it reminded of a few things that I’ve done over the few months – especially with the growth of tools such as GitHub Copilot Chat – to make the documentation process almost effortless.

Sodium Compat: PHP Sodium Functionality via Composer

June 8, 2023 / Tom

If you’ve worked with PHP with any length of time and needed to use some type of built-in encryption, you’ve likely seen something about the Sodium library in the manual.

Sodium is a modern, easy-to-use software library for encryption, decryption, signatures, password hashing and more. Its goal is to provide all of the core operations needed to build higher-level cryptographic tools.

Unfortunately, the module that contains this library isn’t always installed with the PHP binary. It then has to be either re-compiled or enabled by a package manager. If you don’t have the ability, time, or access to do any of those, then there’s a solid alternative for the native library that can be installed via Composer: Sodium Compat.