I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
It's a very good practice to get into writing it all down.
If you take up software development professionally, as you advance you are juggling more and more information.
If something is not supplied in written form, ensure that it is.
Another piece of advice is to email them back with your understanding and get confirmation. This can occasionally jog their memory for anything that has been missed and gives you a written trace in case of any disagreement.
Inventor, Technology Consultant, Developer. Working on the fuller stack (from hard technology development to software). Software Engineer at FileCloud.
Say it again for the people in the back! So many times I've told myself I'll remember it, and news flash....I never do.
I try to write the why of a piece of code, what was the thought process that made it like it is. As well as what it is supposed to do.
It's a very good practice to get into writing it all down.
If you take up software development professionally, as you advance you are juggling more and more information.
If something is not supplied in written form, ensure that it is.
Another piece of advice is to email them back with your understanding and get confirmation. This can occasionally jog their memory for anything that has been missed and gives you a written trace in case of any disagreement.
The more data on your own project the better