It's actually fine for that. I have 24 hour access to my uni building so I just go in when no-one else is around to write my code.
I print off research papers to read them at home/coffee shops. I prefer reading from paper anyway.
Got my phone if I really need to read something. But limited data allowance, so have to ration it...
Of course, nothing beats Google, but if the docs are good (big if) you tend get a deeper understanding of your tools.
I gained a ton of productivity when I started creating a set of helper functions, examples, and gotchas for each language / domain I work in. I used to use a network call helper in JS for ages to remember all the different ways errors can bubble out of fetch. I also have a file with a bunch of ML algorithms, cause there's no way I can keep it all in my head, but I don't want to forget the right tool for a job.
I'm still self depricating, but my 'babys_first_elixir.exs' has been invaluable resource for me to dump interesting funtional patterns into while reading other folks code, then referencing when it's time for me to write.
What I do:
- Take lots of notes with code examples and thorough basic explanations to self.
- Reduce inputs (news, social media, knowledge that doesn't matter)
- Exercise (moving meditation. walk, run, whatever. time to self. no listening to podcasts/music/etc.)