with me. Regarding branches, I meant I use the same git branches and of course git commits Used in development as a model.
Example. When adding a new feature, I start a new git branch, but in my memory palace, instead of adding my new feature right then and there, I usually place a " porthole " to another palace, and when I am finished adding the new feature, I place another porthole at the end of this journey that brings me back to my master branch or to a new branch of this branch, etc.
As you can imagine, I do the same on a smaller scale for simple commits throughout. Makes it easy because I’m already used to this development workflow using git.
Basically, anytime I diverge from the main project, I jump to another familiar place. I have hundreds in use and I got accustomed to finding new ones. Sometimes by going to the first place that comes to mind when creating a commit or diverging to a new branch. Example:
git commit -m “Added view component for skills, progress bar” ::::
first image that comes to mind : A skying candy bar.
First familiar place that comes to mind: corner store where I used to buy my candy when I was a kid.
I then firmly place my skying giant candy bar in snow where I am at the moment, in my hospital cafeteria already full of code, and it reminds me to go to my candy store where I am building my view component for skills with progress bar…
Mmmm hope it’s clearer. Don’t hesitate to ask for precision.
Don’t hesitate to try to start a journey and try this yourself. There’s a lot of trial and error at first just discovering and development of skills needed for memory techniques such as this.
And I wish someone wouldve repeated the following to me when starting out : start small
Also Important::: have fun without stress. Do mess up, make mistakes, learn to enjoy making mistakes, and next thing you know, you’ll be creating these left and right with ease . These are the skills that helped me more than I could’ve imagined.