mko

We can choose what we want to run at work. I work as with Solution Architecture and Platform Engineering mainly with Azure, PaaS and dotnet solutions. It’s atypical I suppose but surprisingly seamless.

Doing this in Linux is pretty straightforward and my choice of distro is Ubuntu since last year. I have modified Gnome getting it sorta close to Omakub (the precursor to Omarchy).

The stack, including Dotnet, C#, PowerShell, Bicep, Terraform and Azure CLI works well. I’m midway in my setup of Neovim and have it working with PowerShell and Bicep as well as an assortment of other LSP’s. Additional tools such as JetBrains Rider, Draw.io and Obsidian with Excalidraw are native and so is LibreOffice. For the few workloads I can’t run natively (basically Visual Studio and Office) I have a VM.

The major issue I have found in a lot of workplaces with Windows since forever, disregarding the increasing mess in Windows 11, has been group policy lockdowns. IT tend to look at everyone including devs as office workers (assuming Office is the most advanced tools needed), meaning no admin access and blocked apps.

The whole site is kinda suspect.

Yes, although MySQL/MariaDB or PostgreSQL are the more robust options.

For personal use. As someone who has all my non-trivial creations, including dot-files and scripts I replicate between machines, in repos since CVS has a thing it’s a habit. Version control. This stuff is mostly private but not secret, why should I have it public?

Edit after spell check.

For source code or any project - a folder Projects (on my personal setups) or Documents/Projects/PersonalRepo (more customer specific folders under the Projects sub-folder)

• Anything under ~/Projects that isn’t just a throwaway will be a git repo.
• Anything under ~/Documents/Project/*Repo will be a git repo.

Without knowing what ypu plan is in detail, here’s one example of a plan for a NAS…

• Flash your SAS card or get an LSI card you can flash to IT mode.
• Install TrueNAS Scale and set up your ZFS volume with your existing SAS drives
• If any drive fails, exchange it for a SATA with at least the same size and re-silver.

You wouldn’t need to exchange all of them at the same time as long as the one you are swapping in can hold all the blocks the old one did.

This is the way we did things back in the day in manufacturing. Zebra printers connected to serial connections or via dumb terminals via serial ports being sent ZPL from OpenVMS based applications.

Switzerland is contradictory in many ways. At the same time as they go for on-prem or sovereign cloud (laudable), they are passing laws that chase away privacy first companies such as Proton (less than optimal).

Yeah, your data is taken hostage. When cancelling the subscription it’s a good idea to delete everything manually before the account expires. Even if you can’t guarantee Dropbox haven’t just flagged the files as deleted, it signals intention. I did this when migrating to pCloud and haven’t received any reminders from Dropbox.

It’s a good idea to use what you know. I don’t have much experience with btrfs but if it does what it says on the tin then it should be safe to use.

Copying the contents at the target is a good strategy. If the drives are to be put into 27/7 use later I would probably consider wiping them and run an integrity test before putting them to use, as once they start being used it will be too late (and stay as a doubt in the back of my mind).

From a position of handling corporate data on a daily basis, I am pretty confident that data integrity is top of mind.

How do you ensure that is doesn’t happen? If this is corporate data that can be key.