ICloneable:

A nice read on on deep , shallow copy and the interface implementation

IEquatable

IEquatable.Equals vs. System.Object.Equals

The IEquatable.Equals method is very similar to Object.Equals. However, IEquatable.Equals is type-safe and generic—requiring no boxing and unboxing.

IEquatable vs. IComparable

At first glance, the IEquatable interface appears very similar to the IComparable interface. But, whereas IEquatable returns a bool representing only whether the instances are equal or not, IComparable returns an inthow the instances differ—whether smaller, equal or larger. indicating

3/20/2008 7:29:40 PM (GMT Standard Time, UTC+00:00)    Comments [0] 

SQL joins with Venn Diagrams

Basic SQL Xml techniques

SQL tips

A Little something about SQL Null

Row Number function in SQL

3/12/2008 7:33:45 PM (GMT Standard Time, UTC+00:00)    Comments [0] 

Interesting piece on SQL server Myths- Jason Haley

talk abt SQL server myths on truncate commands, where a sql table variable is stored, etc

SQL server error handling, and a must read

7/2/2007 1:57:02 AM (GMT Daylight Time, UTC+01:00)    Comments [0] 

Beware using IsStringNullOrEmpty in .Net 2.0. This bug could easily slip out of the developers hands, as we use IDEs almost always.

7/2/2007 1:10:52 AM (GMT Daylight Time, UTC+01:00)    Comments [0] 

Here is a cool function to parse delimited string input to SQL stored proc.[thru Jason Haley]

7/2/2007 12:53:48 AM (GMT Daylight Time, UTC+01:00)    Comments [0] 

One of the things I learnt from my first job is, if you differ from your colleague(s) on anything, check if you are differing or your ego is. The "incident" that lead to this was an eye opener, it showed us(team) how different people could be and how pre-conceived false personal notions could be affecting communication. Also the things that lead after that "incident" proved that you don't lose anything by apologizing or offering a sorry for a mutual mistake. I know I am still not best at this. Also over the course of years I learned that an intern would have a better(uncorrupted) grasp of concepts than a guy who has worked on some technology for years.

Guys like Jeff Atwood, make me not blog. At any moment there are atleast 50 feeds that are waiting for me to read and If I am not working on something cool, the passion to blog is zero.

Having said this Jeff Atwood has compiled an awesome list of pointers that are worth a read for any programmer.  Let me try to give the links that I liked from his compilation, with my words and a couple of my rants. I know I am not perfect, but....

• Understand and accept that you will make mistakes. Never take things personal.
• Being Humble teaches you a lot than being head strong.
• Ask Questions.
• You are not your code. If someone judges you by your code, then GOD help him.
• Treat people who know less than you with respect, deference, and patience, even if they are juniors to you.
• The only true authority stems from knowledge, not from position or years of experience.
• Don't try to dump your knowledge into someone who doesn't care. This is just an utter waste of time.
• Fight for what you believe, but gracefully accept defeat. There is no harm in saying "I was wrong" or "I am sorry"
• Share your knowledge whereever possible
• Don't be the guy in the room.
• Don't restrain yourself from raising red flags, you can never be a leader if you cannot speak your mind (this could be scope creep, staffing or lack of leadership/direction)
• Make hard problems look easy(I know this is tough, at times, but still)
• Dont over-analyze things, get your hands on.
• Your colleagues are your best teachers
• Some people are -------(add the adjective of your choice here).
• NEVER fake being nice, friendly, honest.
• NEVER EVER under estimate yourself. Everyone gets a chance to shine or to walk out of the door
• SMILE  - It can do wonders to people you work with.

Credits : Dare Obasanjo, Omar Shahine, Michael McDonough, Andres Taylor

3/25/2007 6:24:19 AM (GMT Daylight Time, UTC+01:00)    Comments [0]