Re: Changing var names

2010-01-20 Thread Victor Subervi
On Mon, Jan 18, 2010 at 10:10 AM, Jean-Michel Pichavant < jeanmic...@sequans.com> wrote: > Victor Subervi wrote: > >> On Fri, Jan 15, 2010 at 3:15 PM, Adam Tauno Williams < >> awill...@opengroupware.us > wrote: >> >>On Fri, 2010-01-15 at 13:27 -0400, Victor Su

Re: Changing var names

2010-01-18 Thread Jean-Michel Pichavant
Victor Subervi wrote: On Fri, Jan 15, 2010 at 3:15 PM, Adam Tauno Williams mailto:awill...@opengroupware.us>> wrote: On Fri, 2010-01-15 at 13:27 -0400, Victor Subervi wrote: > Hi; > Well it took me *less than a day* to fix the following problems: > -- bare excepts (accidentally

Re: Changing var names

2010-01-16 Thread Victor Subervi
On Fri, Jan 15, 2010 at 3:47 PM, Phlip wrote: > Victor Subervi wrote: > > > Should I re-write it in classes before testing units? Right now it's > > very monolithic. > > The "Unit" in unit tests is a misnomer. It refers to an old QA concept, for > high-end projects, that the failure of any test s

Re: Changing var names

2010-01-15 Thread Phlip
Victor Subervi wrote: > Should I re-write it in classes before testing units? Right now it's > very monolithic. The "Unit" in unit tests is a misnomer. It refers to an old QA concept, for high-end projects, that the failure of any test should implicate only one unit. We only need "developer t

Re: Changing var names

2010-01-15 Thread Victor Subervi
On Fri, Jan 15, 2010 at 3:45 PM, Phlip wrote: > Adam Tauno Williams wrote: > > This process is called 'refactoring' [a good term to Google], and every >> decent IDE provides some support [if it doesn't, it isn't a "decent" >> IDE] >> > > Way more important than IDE support is developers writing

Re: Changing var names

2010-01-15 Thread Victor Subervi
On Fri, Jan 15, 2010 at 3:15 PM, Adam Tauno Williams < awill...@opengroupware.us> wrote: > On Fri, 2010-01-15 at 13:27 -0400, Victor Subervi wrote: > > Hi; > > Well it took me *less than a day* to fix the following problems: > > -- bare excepts (accidentally left a couple I think) > > -- sql injec

Re: Changing var names

2010-01-15 Thread Phlip
Adam Tauno Williams wrote: This process is called 'refactoring' [a good term to Google], and every decent IDE provides some support [if it doesn't, it isn't a "decent" IDE] Way more important than IDE support is developers writing wall-to-wall unit tests as they write their features, _before_

Re: Changing var names

2010-01-15 Thread Adam Tauno Williams
On Fri, 2010-01-15 at 13:27 -0400, Victor Subervi wrote: > Hi; > Well it took me *less than a day* to fix the following problems: > -- bare excepts (accidentally left a couple I think) > -- sql injection attacks > -- recreating tables to make them more reasonable > Now, I believe someone once menti

Re: Changing var names

2010-01-15 Thread Victor Subervi
On Fri, Jan 15, 2010 at 2:26 PM, Jean-Michel Pichavant < jeanmic...@sequans.com> wrote: > Victor Subervi wrote: > >> Hi; >> Well it took me *less than a day* to fix the following problems: >> -- bare excepts (accidentally left a couple I think) >> -- sql injection attacks >> -- recreating tables t

Re: Changing var names

2010-01-15 Thread Jean-Michel Pichavant
Victor Subervi wrote: Hi; Well it took me *less than a day* to fix the following problems: -- bare excepts (accidentally left a couple I think) -- sql injection attacks -- recreating tables to make them more reasonable ** "Programming is an ITERATIVE proce

Changing var names

2010-01-15 Thread Victor Subervi
Hi; Well it took me *less than a day* to fix the following problems: -- bare excepts (accidentally left a couple I think) -- sql injection attacks -- recreating tables to make them more reasonable ** "Programming is an ITERATIVE process." ***