I think it was 5 to 6 that was a really tough one for me because we had an in-house state management library that broke with the major breaking changes to RxJS. After that was pretty much no issue all the way from 6 to 17.

Some of this is just because some of these frameworks and technologies have been around for a while and they iterate frequently. I see a ton of Azure content that is obsolete after only a few years.

In addition, the company doesn’t invest in growing and retaining the rest of the development team for 20 years until said developer is near retirement, then finds that they need to hire 10 developers because 2 need to replace said person and 8 need to redo everything they did.

It’s been nearly 10 years since you needed to develop with C# on Windows.

New versions of .NET have been cross platform with a free IDE since 2016.

I primarily use GitHub CLI to interact with the GitHub API, not Git. I don’t really see it as an extension of the Git CLI, which I use much more frequently. Everything you can do with it can also be done through their REST API.

I use it for things that aren’t really git features, like:

Syncing repository admin, pull request, and branch control settings across multiple repositories

Checking the status of self-hosted actions runners

Creating pull requests, auto-approving them