DEV Community

Discussion on: Moving Past Tutorials: Receiving a Problem to Solve

Collapse
 
lkopacz profile image
Lindsey Kopacz

You'll have to remember the discussion and the specifications after the fact, and relying on your memory alone is not enough!

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.

Collapse
 
johnkazer profile image
John Kazer

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.

Collapse
 
andrewharpin profile image
Andrew Harpin

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.

Collapse
 
piotroxp profile image
Piotr Słupski

The more data on your own project the better