(Apr-13-2017, 07:13 PM)Larz60+ Wrote:oh, the days of Pearly Spencer, sorry - waterfallQuote:So you should always set out at least a list of goalsI think you missed the point of the overall thread.
This thread advocates having a very good and complete overall plan.
Didn't it work well
. But of course it's a folly to write "quick and dirty" - and then redoing it. I try to start writing proper code from the start - including some rudiment comments. Occasionally it turns right
But you make - and fix - mistakes. As you go, you realize that things don't work exactly as you planned. Then someone tells you that you misunderstood the requirements - or they were wrong. Then someone changes requirements.
But the cleaner the initial code was - the easier refactoring will be (about a year ago - commit of 400 changed lines
in 2 days).It is important to keep in mind have to understand that occasionally even project developer - when visiting his/her own old code - will have to spend some time to figure out what the hell were the intentions.
So, again - the cleaner is the code from the start, the easier life will be in the long run
PS Several times in my career as QA Automation Developer I was preached by my managers that they don't care about performance, code quality - I must quickly supply solutions to the problems that the management piles on me. And they did not understand that those solutions eventually turn into problems
Test everything in a Python shell (iPython, Azure Notebook, etc.)
- Someone gave you an advice you liked? Test it - maybe the advice was actually bad.
- Someone gave you an advice you think is bad? Test it before arguing - maybe it was good.
- You posted a claim that something you did not test works? Be prepared to eat your hat.