I don't have time to properly respond, but I'm pretty sure no one on this
team is using single letter variables to save keystrokes.
Is is a good point that abbreviations may be more common in one area than
another. I find both ctx and txn to be completely self explanatory even
with zero context (h
On 27/08/13 09:26, Andrew Wilkins wrote:
> Traditionally I've also avoided abbreviated names (preferring context
> over ctx, transaction over tx/txn). I'm not 100% convinced that this is
> necessary, though, in these cases where there's a *conventional* and
> obvious abbreviation. I mean, ctx is pr
Still waiting for the book to arrive. I'll admit to using single-letter
names in my personal projects, and I'd say that has been largely influenced
by the other Go code that I have worked with.
Traditionally I've also avoided abbreviated names (preferring context over
ctx, transaction over tx/txn)
Hi all,
If you haven't yet, please get a copy of Clean Code [1] as we will be
starting reviews of it soon.
I have found a reference in that book that pretty clearly describes my
dislike for single character variable names. I type that section here.
Avoid Mental Mapping [2]
Readers shouldn't h
