3 ms·

I was a high schooler when I was learning to code. I had a laptop but only the breaks between classes to do it. So what I'd usually do was get up in the morning

I was a high schooler when I was learning to code. I had a laptop but only the breaks between classes to do it. So what I'd usually do was get up in the morning and learn something, then sporadically practice and experiment with it for small chunks of time. I'd usually start by adding comments for what I want to do so I don't lose track. I don't know if this is applicable to actual computer science but worked for me for the programming part. Apps like Enki also have helped me but not in a really transformative way.

HenryBemis 3y ago
Similar to that, when I want to get something (not work related) progress, I think about it on my breaks etc and then I text myself on Signal ("Note to shelf"). Then on Friday night (if not sooner) I go through all these self-messages, I clean them up, and there I have a well rounded next steps on whichever project I work on (coding, building a feeding station for birds, etc)(for drawings I either use A4 and black ink, or the Jotr app)
wucaworld 3y ago
I’m an old person now but I miss coding. With lil kids and stressful management work, I just don’t get blocks of time as I used to as a younger person. Can you share how you were able to code in breaks? As it takes time to get into a state of flow, I don’t even bother with short intervals under 2 hours. That is likely my mistake. Open to tips to wake up the code monk inside.
- VPenkov 3y ago
  No, you're right, and I should have set the expectation that you can't really get into deep thinking mode that more demanding tasks require. But a lot of it can be discrete or boilerplate. While it's not muscle memory yet, leaving comments for myself and implementing them later, especially when it's about implementing $routine in $language. This is useful when learning. Doing integration work will take focus or great planning + notes though. But I think it can be done to a large extent. I find it easy to pick up old abandoned projects where I've left enough comments to my future self. And I'm in my 30s now so not the youngest in software either.

HenryBemis 3y ago

Similar to that, when I want to get something (not work related) progress, I think about it on my breaks etc and then I text myself on Signal ("Note to shelf"). Then on Friday night (if not sooner) I go through all these self-messages, I clean them up, and there I have a well rounded next steps on whichever project I work on (coding, building a feeding station for birds, etc)(for drawings I either use A4 and black ink, or the Jotr app)

wucaworld 3y ago

I’m an old person now but I miss coding. With lil kids and stressful management work, I just don’t get blocks of time as I used to as a younger person. Can you share how you were able to code in breaks? As it takes time to get into a state of flow, I don’t even bother with short intervals under 2 hours. That is likely my mistake. Open to tips to wake up the code monk inside.

VPenkov 3y ago
No, you're right, and I should have set the expectation that you can't really get into deep thinking mode that more demanding tasks require. But a lot of it can be discrete or boilerplate. While it's not muscle memory yet, leaving comments for myself and implementing them later, especially when it's about implementing $routine in $language. This is useful when learning. Doing integration work will take focus or great planning + notes though. But I think it can be done to a large extent. I find it easy to pick up old abandoned projects where I've left enough comments to my future self. And I'm in my 30s now so not the youngest in software either.