• 0 Posts
  • 38 Comments
Joined 1 month ago
cake
Cake day: June 30th, 2025

help-circle



  • I work in the education space and my biggest worry is the next generation losing the ability to critically think.

    Just like how Gen X is much better at mental math than Millennials because the invention of pocket calculators / calculators on phones made math trivial; I think AI is going to trivialize critical thinking. We (as a Millennial) still had to hunt for a correct answer to our problems, which forced us to question possible answers we found and used our critical thinking skills to determine if it was a valid answer or not. With AI though, you type in your question and it’ll spit out an answer. For easy questions - it’s great. But for anything a little more nuanced, it struggles still. So if we don’t develop our critical thinking skills on easy questions, I wonder how we’ll do on the harder questions









  • I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

    • Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
    • Backup everything. I’d recommend doing this on a regular basis anyway.
    • (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
    • (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup








  • I usually only keep documents and media. Programs can be redownloaded and reinstalled (and it might be better to reinstall them in case you move to a new OS anyway to ensure compatibility).

    For docker specifically, only keep stuff that’s specific for your instance; which you normally setup as an external volume anyway. Docker is designed such that you should be able to nuke the container, and all persistent data is restored via an external volume on the host. If you’re not doing that, you should immediately go and set that up now (to get the data out safely, setup a volume connection such that the container path is new - that way you don’t accidentally destroy what’s there, copy the stuff you need out, then readjust the path so it’s correct)