It’s rare these days, but there were occasions in the past where I was completely offline: In a train, on a long trip, when the power went out and I still had a few hours of battery on my laptop.
And I wanted to program for some reason.
I realized that programming offline is a rather revealing experience. It showed me what I could, in fact, write using only my knowledge, intuition, <code>man</code> pages, and the sources in my laptop.
No programming or framework subreddits, no Stack Overflow, no programming forums, no Discord, no AI.
It became clear what problem domains I had mastered and in which ones I was lacking.
A web server in Go? Got it. The front-end? I was forced to admit I sucked at CSS and could barely make any page look good without Googling for CSS properties or going to <a href="https://developer.mozilla.org/en-US/" target="_blank" rel="noopener nofollow">MDN</a>.Thankfully, there were projects on my SSD with CSS I could look at.
One time, I was working on a TUI in Odin. It can interface with C. I had read about <code>termios</code> on a related blog post.
If you have <code>man-pages</code> installed on your Linux system, you have the C standard library docs like <code>sprintf</code>, <code>termios</code>, <code>exit</code>, anything that’s available on the OS.
(If you have to install <code>man-pages</code> or equivalent on your distro, run <code>sudo mandb</code> right after so its search index is updated. This helps searching with <code>man -k &lt;topic&gt;</code> or <code>apropos &lt;topic&gt;</code>).
So <code>man termios</code> got me started.
I also learned that <code>/usr/include</code> contains all the C header files used in the system. It’s a good read.
It was so interesting to search things on my own system. Programming felt more personal, I was working directly with my machine, it was self-contained.
Learning this way is so efficient.
Every line written became more genuinely mine.
Even though this can be impractical in many on-the-job scenarios. It’s still an amazing learning and skill-sharpening activity.

Isaac de Andrade

Programming without internet access reveals gaps in knowledge and forces reliance on local resources like man pages, system header files, and existing code. This constraint-based approach helps identify mastered domains versus weak areas, makes learning more efficient and personal, and strengthens fundamental skills by eliminating dependency on Stack Overflow, documentation sites, and AI assistants.

The Lost Art of Programming Offline

When you code offline, you suddenly see what you truly know and what you’ve been leaning on Google for. It’s humbling, but it also feels more hands on, like you’re actually working with your machine instead of just hunting for answers online. Doing this once in a while is a great reality check for any developer.

I mean in the end its important that you get to the correct solutions no matter which way you get there but i think doing something like that will greatly improve how fast you can get to solutions!

This way, you can hone your skills, but it’s difficult to understand.

Back in the day we had physical books. Outdated, of course, by the time they reached the bookstores. Nowadays you can keep PDFs and ePubs locally. Or you can use something like Zeal: <a href="https://zealdocs.org/" target="_blank" rel="noopener nofollow">https://zealdocs.org/</a>

Does using a local Ollama instance count?