On 22/10/13 13:42, Sydney Shall wrote:
trying to get him to adopt a workflow where he writes on paper
an informal "use case" description of the solution and if
necessary a pseudo code design.
Could you please explain exactly what you mean by 'an informal "use
case" description of the solution
I am glad we are having this discussion. It helps me understand the
plight of some of our posters.
I had the benefit of a good school system, plus attending a technical
high school and a college of engineering.
In the early 90's I was an adjunct professor at the University of
Denver's "Unive
On 22/10/2013 00:42, Alan Gauld wrote:
On 22/10/13 00:07, Steven D'Aprano wrote:
I'd like to upgrade that process :D ...
1) think about your problem
2) if there are some heplful libraries that can make it way easier,
use them
3) write some code
4) fix the bugs until it'll run
5) write unitte
The interesting thing however is that the schools have not taught
>>any kind of approach to problem solving, they just give a homework assignment
>>and expect them to produce code.
>
>
>I feel like we've had this conversation a long, long time ago. :P
>
>
>This is the sort of thing that we should
>
>
> I agree. I've recently started coaching the son of a friend in computing
> for his new school (he is effectively a year behind
> his new classmates). They use VB6 but at a level I can cope with! :-)
>
> The interesting thing however is that the schools have not taught
> any kind of approach t
On 22/10/13 00:07, Steven D'Aprano wrote:
I'd like to upgrade that process :D ...
1) think about your problem
2) if there are some heplful libraries that can make it way easier, use them
3) write some code
4) fix the bugs until it'll run
5) write unittests
6) test if it works correctly and if u
