Yeah, I said the same thing before I started this. But that's when I'm waste deep in code and I hit the inevitable stumbling block of a weird library bug, missi

Yeah, I said the same thing before I started this. But that's when I'm waste deep in code and I hit the inevitable stumbling block of a weird library bug, missing config option, strange behavior, etc. That addictive, power-through flow state is hard to maintain without instant SO/Google access, and for many years that was the only way I coded. But I've begun to relish the other mode of programming: the deep thought and careful mental construction of the optimal program, piece by piece, module by module. Sure, I can't bang out as many lines at night, but when I go into the city in the morning I have a mental view of underlying structure – laid out in clear, bold strokes – that makes my SO-enabled coding so much more effective, and directed.* (*I've noticed that letting SO answer a question prevents any pause which would make you step back from your work and ask "Am I even taking the right approach here?" Low latency, REPLs, and quick access answers make it very easy to go down a rabbit hole – the dark side of exploratory coding.) And yes, as others have mentioned, I do cache and wget all the docs for whatever tools I'm currently using. With all that, it's hard to get truly stuck, even without the internet.