Well, my style of coding was always to make it work regardless of how inefficient looking it was.
Some people like to have everything perfect, every step of the way. I'd rather just make it work regardless of the method - then much later look at tidying it up.
For me, part of the learning is the 'redoing' at a later date of what I have already done. I learn from re-writing something - it takes longer, but I find it works.
I like the brute-force approach - just code like hell - doesn't matter how good-looking or efficient the code is - as long as it does what you wanted. Then a month or so (even a year) later, program the thing from scratch and see how different it is the next time you brute-force it. Basically, you end up teaching yourself rather than trying to apply what other people are advising you.
I'm not the planning and analysing type. However, it is best to concentrate on one thing at a time.
Some people like to have everything perfect, every step of the way. I'd rather just make it work regardless of the method - then much later look at tidying it up.
For me, part of the learning is the 'redoing' at a later date of what I have already done. I learn from re-writing something - it takes longer, but I find it works.
I like the brute-force approach - just code like hell - doesn't matter how good-looking or efficient the code is - as long as it does what you wanted. Then a month or so (even a year) later, program the thing from scratch and see how different it is the next time you brute-force it. Basically, you end up teaching yourself rather than trying to apply what other people are advising you.
I'm not the planning and analysing type. However, it is best to concentrate on one thing at a time.