Re: Too early implementation

2009-04-18 Thread Tim Wintle
On Sat, 2009-04-18 at 13:48 +0200, Filip Gruszczyński wrote: > > So, do you know some good methods to prevent myself from just starting > coding (which I like very much) and do some thinking about the problem > (which I like a little less ;-))? The "Method" (If you can call it that) that I use is

Re: Too early implementation

2009-04-18 Thread Aaron Watters
On Apr 18, 7:48 am, Filip Gruszczyński wrote: > So, do you know some good methods to prevent myself from just starting > coding (which I like very much) and do some thinking about the problem > (which I like a little less ;-))? There are a lot of ideas, some you've seen earlier in this thread. B

Re: Too early implementation

2009-04-18 Thread Kay Schluehr
Start to like blogging about your ideas, results and findings. Writing is a process of clarification of the mind. It doesn't matter much whether you design upfront, or mix coding and writing in an incremental process. If I could I'd just write specs, draft my ideas in Python in order to verify that

Re: Too early implementation

2009-04-18 Thread Patrick Mullen
2009/4/18 Filip Gruszczyński : > Yep, I have heard a lot about test driven development. I am now > programming a lot using DJango and I would like to use its test > framework to try it. However, I have little experience with this (as > most people I know). I also have no idea, how to apply this, wh

Re: Too early implementation

2009-04-18 Thread stephane . bisinger
On Apr 18, 5:54 pm, Filip Gruszczyński wrote: > Yep, I have heard a lot about test driven development. I am now > programming a lot using DJango and I would like to use its test > framework to try it. However, I have little experience with this (as > most people I know). I also have no idea, how t

Re: Too early implementation

2009-04-18 Thread Filip Gruszczyński
Yep, I have heard a lot about test driven development. I am now programming a lot using DJango and I would like to use its test framework to try it. However, I have little experience with this (as most people I know). I also have no idea, how to apply this, when I write code heavily focused on user

Re: Too early implementation

2009-04-18 Thread stephane . bisinger
On Apr 18, 4:44 pm, a...@pythoncraft.com (Aahz) wrote: > This observation was originally made in _The Mythical Man-Month_ by Fred > Brooks, which ought to be required reading for all programmers. I miss that one, yet :( Nice to know, though -- http://mail.python.org/mailman/listinfo/python-list

Re: Too early implementation

2009-04-18 Thread Aahz
In article , wrote: > >Well you know, the thing is that according to Pike & Kernighan in "The >Practice of Programming", your first implementation of a program >should be scrapped and rewritten from scratch, so your approach might >not be that wrong after all. This observation was originally mad

Re: Too early implementation

2009-04-18 Thread stephane . bisinger
On Apr 18, 12:48 pm, Filip Gruszczyński wrote: > So, do you know some good methods to prevent myself from just starting > coding (which I like very much) and do some thinking about the problem > (which I like a little less ;-))? Well you know, the thing is that according to Pike & Kernighan in "T

Re: Too early implementation

2009-04-18 Thread alex23
On Apr 18, 9:48 pm, Filip Gruszczyński wrote: > With Python you rarely are sorry, because you can do everything so > quickly. And yet, at some point you see, that flaws in design get so > annoying, that you need to do something about them. Usually at that > point it's a bit problematic ;-) > > So,

Re: Too early implementation

2009-04-18 Thread Tim Chase
Filip Gruszczyński wrote: I am not a very disciplined person. Usually I rush to my next assignment and code furiously, hoping that my initial understanding of the stated problem will be just fine. And Python does very little to stop me ;-) If I had to do something in C++, I know I would have to w