SayCyberOnceMore

  • 0 Posts
  • 4 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle
  • You’re gonna need some top-down support there.

    Get some coding(& documentation?) guidelines agreed with a manager (I’d hope there were some already) and then it’s not 1:1 opinions, it’s now “Best” Practice.

    But, keep it high level… rather than just going in anti-AI and having more resistance, have the structure there that enforces what you want; local variables (& no emojis for variable names), comments are / not required, etc. and then they could still use Claude, but their output would have to match what you’re after.

    Good Luck


  • The NAS is on site, yes. It’s backed up to Hetzner - inc. it’s own /etc, /home, etc. so the NAS itself is kinda a 2-1 (2 backups, 1 offsite), but it would be a lot of rework to restore and that’s the device I’d need to recover everything else in case of a total disaster (like a house fire).

    (🤔 better check the Hetzner encryption is noted in my keypass file)

    I do need to get it’s config setup in Ansible though so it can be rebuilt automatically, but Ansible for single devices can be a little overkill and difficult to maintain.

    Similar for my hypervisor box… damn… there goes some more evenings…


  • Nice philosophy.

    I’m kinda in the middle ground here.

    I backup “everything” from my raspberries, and just \home for laptops but for an actual disaster recovery I’d just do a clean install, get an IP address and then reinstall everything via Ansible, then drag my home data back off the NAS

    But… I like that statement. I’ll use that at work.