private field
public property
method parameter
class name

On top of that VB.NET is case insensitive, I always end up with a syntax like

private _field # carried over from Python! i did’t knew of the m_ convention when I started in VB.NET
public Property # looks matter in API design
method(pParameter) # So method parameters don’t shadow properties, f*ck implicit self!
uClassName # *u*ser class, maybe it is too ugly

VB.NET allows using “Me” (like C++‘s “this”) when there is ambiguity, so I can say Me.Property,. That could let me drop the u from the class name and use the same convention for fileds and parameters, that way i can say:

Me._field
Me.Property
method(_parameter)
ClassName

But in practice is easy to forget the “Me.” because the compiler doesn’t enforce it and I haven’t found a way to make it complain when there is shadowing or ambiguity in local names. I wish VB.NET enforced “Me.”

On the other hand while I like explicit self and I like “self” better than “Me” or “this”, i wish self was a keyword, with similar semantics than javascrip’s “this”, that is, to refer to the outter namespace, wouldn’t that be sweet?

Today, you’d have to pry explicit self from my cold dead hands :)

This guy only need to time to embrace python and stop trying to emulate his old language behavior in python.