[mattpallissard]

More documentation was available at your fingertips because it wasn't assumed that you had an internet connection and search engine always at your disposal. Also heading into a datacenter to physically plug in a crash cart without a laptop was fairly normal.

I've been remote for years and tend to live in rural areas with spotty connections. I also travel frequently. I can usually stack up a week or two's worth of offline work just in case connections are terrible. Some of it's documentation and writing. But a lot of it is technical stuff or mock ups. Maybe I can't take a task all the way to completion without ci/cd or additional documentation, but I can keep making progress at least.

    * I download documentation sites for offline use with wget
    * I set up virtual environments, containers, and dependencies prior to going offline.
    * Abstract away any libraries that I might need to add or look up the semantics of.  Handwaving over the details.
    * If there's a dependency that I might have to patch, or upstream code I might have to read, I typically vendor things with submodules locally
    * run local instances of infrastructure for testing integrations or tools that expect you to be online all the time such as; config management tools, helm charts, docker repos, secrets management.
    * have testing plans that don't require online validation
        * for code, unit tests
        * for IaC stuff, templating it out and diffing or manually eye-balling
    * keep the logic of ci/cd pipelines in code or scripts instead of platform specific configuration files (within reason)

It doesn't have to be a technical solution. Explicitly planning out your work days to the minutia and accounting for all the tools you'll need will get you pretty far.

Now planning around times in-between access to power is an entirely different game.

edit: formatting