[DUG] Naming your code

[Todd Martin]

I assume you're joking. That's not my idea of 'superb programming'.

> The extreme example was one package where the variables had different
names
> and declarations from one program to another, the programmer concerned
wrote
> not one single comment in his code, and liked naming variables with names
> like B320 B330 B340 etc.  He was a superb programmer who believed code
> should be read to find what it does, and also liked reading object files
> directly.....if you are lucky you wouldn't be maintaining his code, it was
> hard to improve in all senses.
>
> John
>
>
> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On
> Behalf Of Richard Vowles
> Sent: Friday, 5 May 2006 12:53 p.m.
> To: NZ Borland Developers Group - Delphi List
> Subject: RE: [DUG] Naming your code
>
>
> It should be in the version control check-in anyway so you know who to
> blame. The only reason it isn't in my code is I can't be bothered putting
it
> there. It is there on templated code.
>
> (a dedicated subversion user).
>
> How about people change subject lines to match what we are talking about.
> ---
> Richard Vowles, Solutions Architect, Borland New Zealand
> email: richard.vowles at borland.com
> phone: +64-9-9184573
> cell: +64-21-467747
> other: MSN richard.vowles at borland.com, skype: rvowles
> blog: http://www.usergroup.org.nz/blogs/selectBlog.html?id=39769
>
> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
> On Behalf Of Kyley Harris
> Sent: Thursday, 4 May 2006 11:42 p.m.
> To: NZ Borland Developers Group - Delphi List
> Subject: RE: [DUG] In case you're interested (or buy stuff)
>
> Correct. Many companies that rely on contractors to fulfill work do not
want
> temp employess, etc to see a name, and go tell the competition who they
> should contact for good design work. So in that case it is valid to
request
> unsigned work. If you really want to assert that you wrote something. Get
a
> reference in writing on letterhead that cannot be disputed by future
> managers, employees etc. Get the letter to state unequivocally what input
> you had such as design, implementation, delployment. NEVER rely on an
> interviewer calling someone. I make a point of providing no verbal
> references unless that person giving the ref would die for me, or close :D
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
> __________ NOD32 1.1461 (20060329) Information __________
>
> This message was checked by NOD32 antivirus system. http://www.eset.com
>
>
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.5.1/327 - Release Date: 28/04/2006
>



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.5.1/327 - Release Date: 28/04/2006