size of actions
i've been having a hard time continueing development of my project and the solution i think is pretty simple. usually, when i first start coding I've just dived right into the code. this is probably the most horrendous choice you do. but, as i get more involved in the problem space and know what exactly my app will do, i think i should have plans or actions that much that intent.
that's a little vague, what i mean is that of course when you first start you don't really know the structure, the issue, requirements, and ideas you want to bring to life. as you code more, it slowly reveals itself to you. at this point, when you starting feeling a plateau it usually means I've gotten to the point where i can refactor or need more specific plans so i know how my early coding/component will interact with the future plans.
it's also important because how am i supposed to code anything without proper diagram, documents, and layouts. how ridiculous of me to not notice this issue. there is a reason why professionals have detailed diagrams, kambam boards, and what not, they work! the next steps for me is to make more concrete plan and diagrams that will hopefully alleviate my plateau with development.