Software engineer & creator of internet things. Node.js aficionado since 2011, React lover since 2014.
Head of solarwallet.io at SatoshiPay (satoshipay.io).
After having had that problem for years, I started... writing stuff down :D
I create issues in GitHub, not only for what doesn't work yet, but also for features I want to add in the future
I create pull requests when introducing code changes, even if there is no one to review them
Oftentimes before I start working on it, I collect my thoughts on what I want to achieve and what pain I have that I want to solve
Not too detailed, a few bullet points per idea usually do the trick.
Doesn't take much time, but when I come back after pausing for months, I can just read up on my initial motivation and plans, as well as getting an overview of what I was doing before I left.
Plus: Not having to worry about forgetting good lines of thought is a very comforting feeling 🙂
I do the same! Issues and pull requests on Github is a very handy tool to improve productivity and stay aware of the project, even not working in a time on that repo.
I'm trying something in a few weeks that works a ton for me, I usually do like this:
Create a branch signing with is a feature/bugfix/hotfix an then the folder following by the current change
feature/cartModule/cartList
Do what is necessary on project, and go for a commit. Here is a awesome stage that I recommend the most
All set up, then I merge to master, always set this branch up to date
I find super useful in this merge process: code review! in each final merge, I review what is done and anything that comes in my mind, I comment on the lines or review the entire merge
I think that is a good way and you have all the information within the repo, not having writhing elsewhere that you can easily forget
A 'driven' software engineer with a passion for cars and tabletop games. Get it, driven? Because cars and... Okay, I'll stick to writing code instead of puns. 🏁
That's similar to what I do. I have a workspace in Notion.so (great tool for organizing btw) that has everything for a major project, from ideas to tasks and rudimentary user stories. If I leave a project and come back to it, ideally I can grab whatever task was next on the pile or review what I had planned next.
Same here. I write tickets and high level overview documentation as if I would on-board a ton of other developers in the future. In the end that stuff is super helpful getting back on track months later. So practically I'm doing myself a favor, not other people. It's also important to write as if you were explaining to someone who doesn't share the same knowledge at the time you're writing it. Makes it much easier to jump right back when memory faded quite a bit.
Also prioritizing tickets at a time where knowledge about the project is fresh, helps getting back on track quicker.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
After having had that problem for years, I started... writing stuff down :D
Not too detailed, a few bullet points per idea usually do the trick.
Doesn't take much time, but when I come back after pausing for months, I can just read up on my initial motivation and plans, as well as getting an overview of what I was doing before I left.
Plus: Not having to worry about forgetting good lines of thought is a very comforting feeling 🙂
A little addendum:
I do the same! Issues and pull requests on Github is a very handy tool to improve productivity and stay aware of the project, even not working in a time on that repo.
I'm trying something in a few weeks that works a ton for me, I usually do like this:
feature/bugfix/hotfixan then the folder following by the current changefeature/cartModule/cartListDo what is necessary on project, and go for a commit. Here is a awesome stage that I recommend the most
All set up, then I merge to master, always set this branch up to date
I find super useful in this merge process: code review! in each final merge, I review what is done and anything that comes in my mind, I comment on the lines or
reviewthe entire mergeI think that is a good way and you have all the information within the repo, not having writhing elsewhere that you can easily forget
Any ideas to improve is very welcome!
That's similar to what I do. I have a workspace in Notion.so (great tool for organizing btw) that has everything for a major project, from ideas to tasks and rudimentary user stories. If I leave a project and come back to it, ideally I can grab whatever task was next on the pile or review what I had planned next.
Yeah, great tool you note over there notion.so is impressive for this kind of tasks.😉
Hey, thanks for mentioning Notion.so! Going to have to check it out. I wonder how i've never heard of it.
Hey notion looks awesome ...I use boostnote to keep track of everything, but it's not as full featured yet.
Might be interesting to try out!
Same here. I write tickets and high level overview documentation as if I would on-board a ton of other developers in the future. In the end that stuff is super helpful getting back on track months later. So practically I'm doing myself a favor, not other people. It's also important to write as if you were explaining to someone who doesn't share the same knowledge at the time you're writing it. Makes it much easier to jump right back when memory faded quite a bit.
Also prioritizing tickets at a time where knowledge about the project is fresh, helps getting back on track quicker.