Squash-merge PRs. You can configure this in GitLab, GitHub, and Azure DevOps. Your private commits can be whatever you want and they get rolled up to a single PR commit when your working branch is merged to trunk.
Native interop in .NET has always been via what they call "P/Invoke". On .NET Core, P/Invoke is cross-platform and you can also call .so/.dylib functions on Linux/MacOS just like you could always call .dll functions on Windows on .NET Framework before we had .NET Core.
I'm curious to know what you needed to do with native libraries. I've been programming with .NET around 20 yrs and find it fairly rare that I need to use P/Invoke... But I'm sure it depends on what you're building.
From what I've seen, the biggest issue here is that you cannot transfer purchased Google Play Store purchases. Even without the G Suite thing, this is a problem.
For example, I have a fairly unprofessional primary Google account that I created when I was young and dumb(er). I would like to transfer the hundreds of dollars in purchases I've made under that account to another, more appropriately named, account but it does not seem possible.
They could solve this part of the problem for the affected G Suite deprecated users as well as people in positions like me by having a way to do this.
In my mind, "consulting" is knowledge work. Your role is to lend knowledge and expertise, help with strategy, architecture, tool/platform selection, etc.
"Contracting" is high-skill grunt work. Your role is to code your fingers off, deliver-deliver-deliver, typically according to someone else's (possibly ill-conceived) plan.
From what I've read, the Koch method combined with Farnsworth timing is the best way to learn to hear Morse code.
Koch method is about using full-speed dits/dahs from the beginning and gradually adding a couple to the set of characters being trained as you learn to identify them by their sound.
Farnsworth timing is about controlling the overall speed by putting pauses between the characters while training instead of slowing down the dits/dahs of the actual characters.
I don't know the science behind it, but I've spent a few hours training this way. Each set of tones that makes up a character starts to sound like its own word, or phoneme at least. It feels like it's stimulating the subconscious language bits of the brain rather than the logical/conscious ones as if you tried listening and counting the dits/dahs.
It's better than nothing, but one of the values of UUIDs for identifiers is that you can create new ones client-side while offline. These "sequential" UUIDs will fail standard UUID validation because of the byte swapping and, in my experience, when used offline-capable apps, will result in sparse clusters of sequential UUIDs that yield an unpredictable improvement over truly random UUIDs.
Docker runs an arm64 Linux VM on an M1 Mac. My experience is that it works well for anything that has arm64 images available. It can also run x64 containers via QEMU emulation.
I found this to be hit-or-miss. I need the full version of MS SQL Server for one of the projects I work on. MS only supports x64 and the image won't start because of what looks like some kind of memory mapping/translation problem with the QEMU emulation.
Full version of MS SQL Server doesn't work. The X86-64 Docker image won't start under QEMU emulation and the installer won't install it in the ARM64 insider builds of Windows 10/11 running in Parallels. You can use the ARM64 build of Azure SQL Edge, but it lacks many features that may or may not be important depending on your use.
I run and develop on the x64 versions of dotnet core 3.1 and dotnet 5 on my M1 Macbook Air every day and don't have problems. It runs via Rosetta 2 translation, and probably isn't as fast or memory efficient as it could be, but I don't have major issues and it runs a lot faster and keeps my mac cooler than if I try to run in Windows on ARM in Parallels.
I use VS for Mac 2019 (x64) and VS Code (arm64) for development work on a near daily basis.
That said, I tried installing the arm64 dotnet 6 preview and it broke the x64 versions I had installed and although I could debug/attach in VS Code, I could not get it to debug in VS for Mac 2019.
From what I understand, the issue is that the dotnet binary for x64 got replaced with the arm64 one. There is only one on the system at a time and the arm64 version doesn't know how to work with the x64 architecture sdks/runtime. There is some discussion and links to related issues in this GH issue: https://github.com/dotnet/sdk/issues/16896
Regarding SQL, I use the Docker Azure SQL Edge arm64 image and it works okay for most thing but doesn't support some of the more advanced features like full text search or spatial types.
For Database Projects (dacpac), Azure Data Studio with the Database Projects extension works okay for basic editing and deployment. However, it's not nearly as complete or refined as the database project edit/deploy experience in the Windows version of VS 2019. As far as I can tell it doesn't create new refactorlog entries for renamed objects and I can't figure out how to create a new deployment profile so I have to select the database connection every time I deploy.
I have been running the x64 build of dotnet 6 preview 4 and now preview 5 for a while and have not many issues. One thing that happened is that it broke the dacpac deploy in Azure Data Studio but there was a relatively simple workaround -- added a configuration setting in Azure Data Studio to override the dotnet SDK path to point to a folder where I had put dotnet 5.
This was my first exposure to 2-step command combos (some call "chords") starting with Ctrl+K and then a second key.
I'm unsure if WordStar created this feature.
However, by way of Turbo Pascal, Delphi, Visual Studio and even VS Code, somehow this feature followed me into the present day for ~40 years!