3 ms·
Related, the advice I've heard is never to completely finish what you're writing when you stop for the day. Having some obvious things to dive right into when y
by version_five 5y ago
Related, the advice I've heard is never to completely finish what you're writing when you stop for the day. Having some obvious things to dive right into when you come back to it makes it much easier to get warmed up again then e.g. finishing a chapter or section and having to start on a new one.
Same is true for coding I believe, it's nice to have some quick wins to get started with before trying to tackle something brand new.
- poopypoopington 5y agoyes!
- smackeyacky 5y agoWhen I was in the middle of creating the software stack for my company, I would inevitably get stuck with big issues or trapped trying to architect something decent that would scale. I was working out of my house at the time. I had an old car in the shed that needed a fair bit of mechanical work. Every time I got stuck or needed inspiration, I'd get up from my desk, put on some gloves and get working on the car. Or go for a bike ride. It really, genuinely worked for me. I just needed to park some of those issues for a while and do something completely unrelated.