Attribute-based Programmers
Just for fun... Here's a couple of nice quotes from e-conversations and comments.
- The more I use attributes, the more I like attributes. I'm really becoming a "programmer with attributes"
- There is more, about you and your professionalism, that can not be "decompiled"
The first quote is adapted from Italian and in the original form it enjoys the double sense we assign to the word "attributes" (the plural form). You americans and mother tongues, do "attributes" mean to you what it (sometimes) means to us?
Reading Flyboys, a James Bradley's book about the story of some US pilots during WW2, I've learned a lot about the so-called Spirit of Warrior that animated all Japanese troups during the war. They (were led to) believe that thanks to their spirit they could only win any war. In the book, James reports the comment of an unknown American pilot:
We had the same spirit, but we called it balls.
Well, we (also) call it attributes. (When we want to be polite and be "sort of" elegant in our conversation...)
In light of this, I officially propose to rename "real programmers" to "attribute-based programmers." It reflects better the new spirit of .NET programmers, isn't it? Attribute-based programmers are seasoned and professional developers and consultant, completely obfuscated and, as such, impossible to decompile for fellows and wives <g>