Comment Anybody can write code. Employable people can DOC (Score 1) 309
I read your list of achievements. Very nice.
In the next few projects focus on
- planning the programming before you do it, so you can explain your design decisions
and the inevitable tradeoffs to prevent people who come after you from trying to "fix"
what isn't broken.
- documenting what you did do so anyone can support your code
If you are fond of saying any of these:
- "Anyone who can read code can see what it does"
- "the obvious doesn't need documenting"
- "there were no tradeoffs"
- one day I will rewrite this to be better
University education is a good first step to something something complete.
Being a freshman is not a bonus nor a hindrance. Experience with github,
software RCS etc are all good. The keys are making choices before coding,
knowing and being able to explain those choices, and documenting them for
others to take the burdens of support off your inventive shoulders.
E