5 ms·
I agree with this. I travel a lot and read a lot of ebooks. I also get a fair amount of work done without internet connectivity. * plan out exactly what yo
by mattpallissard 3y ago
I agree with this. I travel a lot and read a lot of ebooks. I also get a fair amount of work done without internet connectivity.
* plan out exactly what you'll be working on, to the minutia
* save source and upstream dependencies locally
* have a local environment where you can build and run the code locally
* download specific sites and documentation with `wget -r` and the like
* have multiple things stacked up for if you hit a blocker on one project.
If it's a solo big project you can work without internet in perpetuity. You just have to RYO on any libraries you don't have downloaded before hand.
- maerF0x0 3y agoFun true story. I had a professor in university who only had 1 finger on 1 hand. He would plan out whole programs in his head, debug them mentally (step the code afaik), and then when he knew exactly what he wanted to write, he'd sit down and pluck away at his keyboard, one effortful keypress at a time. He was productive and smart enough to do it, and I think it's a great exercise for engineers to at least try a few times. Try to think about what you're going to write before you even open your editor. Try to break down the strategy into a recipe of things that can be done in about hundred lines each or so. Then sit down and type it out.
- tamiral 3y agosomething similar to my process when I was in university doing my internship and was doing half requirements gathering as a business analyst and half developer working on different small projects. It's really helpful to organize yourself , visualize the code, the problems, plan it out on paper and then code... less coding more design upfront.
- qup 3y agoI hope he's having a heyday with chatGPT translating his voice into code.