The first - and one of best - Mark Harding (UK).
I remember a ling time ago.. Mark would ping me with some Elggy question
or another and I'd ping back a little and then demand that he email me
with the details.. Slowly the pings and emails would die put and
the next day he would email me back to say 'it was working..'
There was that 'Versioning' or the Files PlugIn he had
kept bugging me about and sure enough some days later..
It 'was working..' ;-)
Briliiant for his age - I think he was about 13 then,
barely starting high school, but almost a PhD in the Elgg API lolz ;-)
Hope he's doing well with his stuff these days...

The last and also.. one of the best.. SpeedySnail only about 11 yrs going onto 12 very soon, born under the same perfectionist zodiac sign as the 'master' ;) Speedy comes from a long and respected 'family' tradiiton of Elgg-sites - FKKids.Com the largest Elgg-based website on the world (built by hand, scratch by scratch); Speedy used hang out there since a few years back, used to bug the heck out of the admins with his programming smartz. One day Speedy figured out that the platform behind FBFK was Elgg! and soo.. downloaded, instaled,  tested - not very long ago. Today - Speedy spins out themes like a theme-magician, also codes in Python !;-X, asks difficult questions that most Elggsters will not or can not answer.. while Speedy speeds on - onwards in his quest to own the Internet one day ;P Don't frett so hardd Speedy ! you'll get yr OpenSIM @Enbrache's Server. one day soon ;-)

lolz ;-) krazi koding kid from kolkata got a new avatar ! ;-P

@Dhrup

My brother and I are already doing something like this. It is still in development. http://jrcoders.x10.mx. We will buy domain when we are done. Could we move this to your servers when were done?

We will be posting our site on github. Let me know if you want to get involved.

The Ten Commandments of Egoless Programming (from childhood days;)

1. Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry. We can, and should, learn, laugh, and move on.
2. You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don’t take it personally when one is uncovered.
3. No matter how much “karate” you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.
4. Don’t rewrite code without consultation. There’s a fine line between “fixing code” and “rewriting code.” Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.
5. Treat people who know less than you with respect, deference, and patience. Non-technical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don’t reinforce this stereotype with anger and impatience.
6. The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, rather than some serious inconvenience to be fought.
7. The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect – so if you want respect in an egoless environment, cultivate knowledge.
8. Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you are right, don’t take revenge or say “I told you so.” Never make your dearly departed idea a martyr or rallying cry.
9. Don’t be “the coder in the corner.” Don’t be the person in the dark office emerging only for soda. The coder in the corner is out of sight, out of touch, and out of control. This person has no voice in an open, collaborative environment. Get involved in conversations, and be a participant in your office community.
10. Critique code instead of people – be kind to the coder, not to the code. As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.

;-)

The Ten Commandments of Egoless Programming #3

No matter how much php “kungpowfoobar” you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it’s not needed.  --- ScoopDeWuTangWarriorMonk

@DhrupDeScoop what a marvelous speech.